You do not need dozens of workflows. Five well-built automations cover most of the follow-up work a small sales and marketing team forgets to do.
- Each workflow is a trigger, conditions and actions
- Start with one, test it on yourself, then add more
- Always stop automation when a human replies
Most small teams do not need a library of workflows. They need a few that run reliably and cover the moments people forget: the first hello, the follow-up after an event, the deal that quietly stopped moving.
Below are five automations you can build in Salesformics in an afternoon. Each one is described the same way: the trigger that starts it, the conditions that decide who it applies to, and the actions it takes. You can build them in the drag-and-drop workflow editor, or type a sentence into the GX Box and refine the draft it produces.
1. Welcome sequence for new sign-ups
The first message after someone signs up gets more attention than almost anything you send later. Use it to set expectations and point people at one useful next step.
- Trigger: contact is created from a sign-up or newsletter form.
- Conditions: lifecycle stage is subscriber or lead; contact is not already a customer; email is valid.
- Actions: send welcome email immediately; wait 3 days; send a short guide related to the form they used; wait 5 days; if no click, send one final message with a direct reply prompt; tag contact
welcomed.
Keep the first email short. Say who you are, what they will receive and how often. Ask one question they can answer by replying, such as what brought them here. Replies tell you more than any form field.
2. Job-change alert
When a champion moves to a new company, you lose a contact at the old account and gain a warm lead at a new one. Both deserve attention, and both are easy to miss.
- Trigger: the company or job title field on a contact changes, or an email bounces from a previously valid work address.
- Conditions: contact has been linked to at least one opportunity or is marked as a key contact.
- Actions: create a task for the account owner to confirm the change; flag the old account as needs new contact; if a new company is recorded, create or link the company and notify the owner with a suggested congratulations note.
The bounce trigger is the underrated part. A sudden hard bounce on a contact who used to open your emails is often the first sign that someone has moved on.
3. Event follow-up
Trade shows, webinars and meetups generate a burst of contacts that cool down fast. The team is tired, the spreadsheet of badge scans sits in someone's downloads folder, and a week later nobody remembers who asked what.
- Trigger: contacts are imported or added with the tag
event:<name>. - Conditions: split by attendance status, for example attended, registered but missed, spoke to us.
- Actions: within 24 hours send a thank-you email with the recording or slides; for spoke to us, create a follow-up task for the person who met them with notes attached; for registered but missed, send the recording with a short summary; after 7 days, move engaged contacts into the relevant nurture track.
Set this up before the event, not after. Create the tag and the workflow, then the import does the rest.
4. Re-engagement for quiet contacts
Every list has contacts who stopped engaging months ago. Sending them more of the same harms deliverability and teaches mailbox providers that your emails are unwanted. A short re-engagement workflow either wakes them up or lets them go.
- Trigger: scheduled daily check.
- Conditions: no clicks, replies or site visits for 120 days; not an active customer with an open deal; not already in re-engagement.
- Actions: send one plain email asking if they still want to hear from you, with two clear options; wait 10 days; if they click to stay, reset their status and tag
re-engaged; if no response, move to suppressed so they no longer receive marketing email.
Suppressing quiet contacts can feel like losing something. In practice, a smaller list of people who read your emails performs better than a large list of people who ignore them.
5. Deal stall alert
Deals rarely die in a dramatic moment. They drift. The last email goes unanswered, the next step is never booked, and a month later the opportunity is still sitting in the pipeline at the same stage.
- Trigger: scheduled daily check on open opportunities.
- Conditions: no logged activity for longer than the stage limit; deal value above a threshold you choose; no future task or meeting scheduled.
- Actions: notify the deal owner with the last activity and days since; create a task to define a next step; if still stalled after 7 more days, notify the team lead and add the deal to the weekly review dashboard.
Stage limits should vary. A deal can reasonably sit in proposal sent longer than in discovery call booked. Use your own history to set them.
| Stage | Example stall limit | Suggested next step |
|---|---|---|
| Qualified | 5 days | Book discovery call |
| Discovery done | 7 days | Send proposal or agree scope |
| Proposal sent | 10 days | Confirm decision date |
| Negotiation | 7 days | Resolve open questions |
The limits above are examples to start from, not benchmarks. Review them after a quarter against how long your won deals actually spent in each stage.
Using the GX Box to draft them
Each of these workflows can start as a single sentence. Type something like when a deal has no activity for 10 days, notify the owner and create a task and the GX Box turns it into a draft with the trigger, conditions and actions filled in. You then open it in the editor, check each step and adjust timings or wording.
The draft is a starting point, not a finished workflow. Always check three things before you save: which contacts the conditions actually match, what happens when someone replies, and whether any other workflow might send to the same people on the same day. A quick preview of the matching contacts usually reveals surprises, such as customers caught by a rule meant for leads.
How to roll these out
Do not switch on all five on the same day. If something misfires, you want to know which workflow caused it.
- Build one workflow and set it to test mode.
- Add yourself and a colleague as test contacts and run through every branch.
- Read every email on a phone. Cut anything that does not need to be there.
- Switch it on and watch the activity log for a few days.
- Move to the next workflow once the first has run cleanly for a week.
Rules that apply to all five
- Stop on human contact. A reply, a booked call or a manual email from the owner should end any sequence.
- One owner per workflow. Someone is responsible for checking it monthly.
- Plain language. Write emails as you would to a colleague. Short sentences, one ask.
- Respect consent. Marketing workflows only send to contacts with a valid lawful basis, and every message has an easy opt-out.
Measuring results
Give each workflow one number. Welcome: replies or first purchases. Job-change: new opportunities created from moved contacts. Event follow-up: meetings booked within 14 days. Re-engagement: share of contacts who choose to stay. Deal stall: stalled deals that moved to the next stage. Put all five on a single dashboard and look at it at the start of each month.
Five workflows will not run your business for you. They will make sure the predictable moments get handled, so your team can spend its attention on the conversations that need a person.
Questions
Do I need technical skills to build these workflows?
No. Each one is a trigger, a few conditions and a list of actions. In Salesformics you can drag the steps into place or describe the rule in the GX Box and edit the draft.
How do I stop a sequence when someone replies?
Add an exit condition for replies and booked meetings. In Salesformics this is a single setting on each workflow, and it is worth enabling on every marketing sequence.
Is it safe to suppress contacts who do not respond to re-engagement?
Yes. Suppressed contacts stay in the CRM with their history, they simply stop receiving marketing email. You can still reach them manually or restore them if they engage again.



