Trigger-based outreach workflows

A trigger workflow should decide what happens to a live prospect as well as launch a message. Its stop rule belongs alongside its send rule.

Build the workflow

Use the workflow as a chain of decisions. Each stage should answer one question before it permits the next action.

Stage	What you are trying to learn	Example question
Choose the trigger	What changed and why it gives you a reason to contact the account	What happened that makes this contact worth reaching now?
Define entry	Whether the event meets the conditions for entry	What exact condition opens the workflow?
Check state	Whether the contact and account can receive outreach, and what is already in progress	Is this contact eligible, and what sequence state are they in?
Choose the action	Whether to continue, adapt, pause, route, or suppress	What should happen next if the event is real?
Stop	What ends or pauses the workflow	What reply, meeting, opt-out, or owner action stops it?

Choose the trigger

Start with an event that gives the message a reason to exist. A narrow trigger makes the next decision easier because the workflow knows what changed.

Use unique signals as outreach triggers.¹ Real behavior such as ad clicks and page visits can indicate when to reach out.² Write the trigger as a condition tied to an action. An event trigger defines which action to perform based on a specified condition.³

Avoid broad entry rules that admit every contact showing weak activity. The trigger should tell you what the person or account did, when it happened, and why that event changes the next move.

Define entry and ownership

Write the entry contract before sending a message. It should specify who owns the workflow, which records stay out, and what ends the run.

Each outbound workflow needs a trigger, one owner, a suppression check, and a written stopping rule.⁴ For an event-triggered campaign, the maximum expiration time is capped at 15 minutes.⁵ An event-triggered campaign can initiate a voice call, email, or SMS.⁶

Keep the action narrow enough to test. If the event should create a task, queue a sequence, or send a message, define that action alongside the entry condition. This keeps a valid signal from becoming open-ended permission to contact someone.

Resolve eligibility and sequence state

An event can be valid while the contact is unsuitable for the next touch. Check the person, account, suppression state, and active sequence before the workflow acts.

Resolve the event, check contact and account eligibility, read the current sequence state, then choose whether to continue, change the next unsent step, pause for a rep, or suppress.⁷ Attendance by a known contact shows engagement with a declared topic, while purchase authority remains unconfirmed.⁸

Pause automated copy and give the owner a context-rich task when a known contact attends an event. Stop automation when a rep starts a live conversation.⁸ This handoff preserves the signal's context while giving the human a chance to test whether the topic matters.

Check re-entry behavior during setup. In HubSpot, a record enters a workflow only the first time it meets the triggers unless re-enrollment triggers are added. Sequences default to unenrolling a contact after a reply or booked meeting, and both behaviors can be switched off.⁹

Choose the action and message

The event should change what happens next. Keep the message tied to the event and choose the lightest action that fits the current state.

Queue a sequence from a marketing-intent signal when the workflow calls for structured follow-up.¹⁰ Act immediately when a timely event affects the prospect.¹¹ Contacting while the signal is fresh gives the message a clear connection to the action that caused it.

When prospects engage, the team can ask for meetings and place them in more sales-oriented sequences.¹² After engagement, a seller can also send a one-off message outside the traditional sequence.¹³ When the prospect engages with the trigger, run discovery on that topic.¹⁴

Use the event to open the conversation, then let the response determine the route. A positive reply can move the contact into a meeting path. A weak response can keep the person in a lighter path. A live conversation should end automated copy.

Stop the workflow

Send logic and stop logic belong in the same design. Outbound automation works when stop conditions receive the same care as send conditions.¹⁵

Write stopping rules for replies, booked meetings, live conversations, suppression events, and opt-outs. Make each rule visible to the person who owns the workflow, and test it with a contact already in sequence before enabling live sends.

What not to do

These failure points can turn a useful signal into unwanted outreach or a broken handoff.

• Do not treat an email opt-out as a later cleanup task. CAN-SPAM requires opt-outs to be honored within 10 business days, requires the opt-out mechanism to work for at least 30 days after the message, prohibits charging a fee or requiring more than a reply or a visit to one web page, and allows penalties of up to $53,088 for each violating email.¹⁶
• Do not force a single revocation channel. FCC telemarketing rules require a revocation made in any reasonable manner to be honored within a reasonable time of no more than 10 business days, and they prohibit designating an exclusive method for revocation.¹⁷
• Do not keep the internal do-not-call list in an informal note. It needs a written policy available on demand, trained staff, and a request recorded when it is made.¹⁸
• Do not automate social touches before checking the platform rules. LinkedIn's user agreement prohibits bots and unauthorized automated methods for adding or downloading contacts or sending messages, so automated social outreach needs a policy check before a deliverability check.¹⁹
• Do not let event attendance stand in for buying authority. Route the signal to a context-rich task and let the conversation establish fit.⁸