Auto-enrol deals into email sequences
Set up an automation rule so that whenever a deal moves into a chosen pipeline stage (Proposal, Negotiation, Won), its contacts are enrolled into a multi-step email sequence automatically. No manual list maintenance.
In this guide
CRM- Steps
- 5
- Prereqs
- 4
- Pitfalls
- 3 common ones
- Related
- 3 guides
Walkthrough only — no setup wizard. The flow is exactly what you do inside YionStack today.
Before you start
- CRM module enabled (Business plan and above).
- An email sequence already authored — Marketing → Sequences → New sequence — with at least one step.
- A connected mailbox (Gmail or Microsoft 365 OAuth) the sequence sends from.
- Owner or Admin role — automation rules are business-wide configuration.
Steps
- 1
Open the automation rules workspace
Go to CRM → Automations. Existing rules are listed with their trigger, conditions and actions. Choose New rule.
- 2
Pick the trigger
Set the trigger to Deal stage changed. The condition fields appear — pick the pipeline (if you have multiple, per LAG-B4 multi-pipeline help guide) and the stage that should fire the enrolment (commonly Proposal or Negotiation, occasionally Won for a post-sale onboarding cadence).
- 3
Add the enrol-sequence action
Add the action Enrol contact in sequence. Pick the sequence the deal’s contacts should be enrolled in, and the mailbox connection the sends go through. The action enrols every contact attached to the deal — primary and additional.
- 4
Save and activate
Save the rule and switch its status to Active. From the next deal-stage change, the action fires and the sequence-execution service picks up the enrolment on its next tick (typically within one minute).
- 5
Watch the enrolments land
Open Marketing → Sequences → [your sequence] → Enrolments. Every contact enrolled by the rule appears with the deal that triggered them, the enrol-date, and the current step they’re on. Open rate, click rate and reply rate aggregate per step as usual.
Common pitfalls
Stage re-entry triggers a second enrolment
If a deal moves out of and back into the trigger stage, the action fires again. The sequence-execution service deduplicates on (sequenceId, contactId) so the contact doesn’t end up double-enrolled — but the trigger event still counts toward the rule’s execution log. If this is undesirable, narrow the condition (e.g. only fire on first entry to the stage).
Unsubscribed contacts skip enrolment
If a contact has hard-suppressed marketing (an unsubscribe through any YionStack sequence ever, or imported from another tool with that status), the enrolment skips them. The deal still moves stage; only the email action is suppressed. The activity feed records the skip with the reason.
No mailbox connection
The action requires a valid connection. If the mailbox token has expired or the OAuth has been revoked, the action fails at execution time and the rule’s execution log surfaces the failure. The deal continues to move stage either way.
Need a hand with this one?
If a step is missing or unclear, tell us — every guide is a working document we improve as customers ask.