Available on | ❌ Free | ✅ Start | ✅ Grow | ✅ Scale |
Automations help you build multi-step workflows that run automatically when someone completes a funnel or makes a payment. You can use them to create personalized journeys such as:
Welcome emails sent right after sign-up or quiz completion.
Follow-up messages sent after a delay with a special offer or next step.
Drip campaigns that nurture leads over time.
Branched journeys based on answers, scores, outcomes, or other participant data.
Automations vs. Follow-up Emails
involve.me gives you two ways to send emails after a submission: Follow-up Emails and Automations.
Both can be active on the same funnel at the same time, and they work alongside each other without conflict.
| Automations | |
Where to set up | Funnel Settings → Email Notifications | Main menu → Automations |
Emails per trigger | 1 email (or 1 per outcome) | Unlimited — build multi-step sequences |
Email editor | Basic editor — text, images, and attachments | Block editor — type "/" to add headings, images, buttons, tables, emoji, and more |
Timing | Sent immediately | Immediate, delayed, or scheduled with Wait steps |
Conditions | Per-outcome emails only | Branch on any field: answers, scores, outcomes, contact data, email engagement |
Non-email actions | No | Yes — Invite to Funnel, A/B Test, Exit |
Best for | Quick single-email confirmations, result delivery | Drip campaigns, nurturing sequences, complex journeys |
ℹ️ If you only need one immediate email after a submission, such as a quiz result or payment confirmation, Follow-up Emails are the simplest option.
Use Automations when you want to create a journey with multiple steps, delays, or branching logic.
Triggers: How a workflow starts
Every workflow begins with a trigger. The trigger is the event that starts the automation for a participant.
When creating a workflow, you choose the trigger and select the specific funnel connected to it.
Completed Submission | The workflow starts when a participant completes the funnel (not on partial submissions). This is the most common trigger. |
Payment Completed | The workflow starts after a successful payment. This trigger is useful for post-purchase sequences. |
Each time the trigger condition is met, a new workflow execution starts for that participant.
Available actions
After selecting the trigger, you can build your workflow by adding actions to the canvas.
Click the + button between steps to add a new action.
Send Email — Send a personalized email to the participant.
You can customize the subject, write the email body, and add attachments. Type “/” in the editor to insert blocks such as headings, images, buttons, tables, emoji, and more.
You can also personalize the email with variables by using “@”.
Invite to Funnel — Send an invitation to complete another funnel.
This is useful for connected experiences, such as sending a feedback survey after a purchase.
Wait Time — Pause the workflow for a set duration, either in hours or days, before the next step. This helps you space out emails in drip campaigns.
Conditional Logic — Split the workflow into different paths based on participant data, including answers, scores, outcomes, email engagement such as opened or clicked, or any other field.
A/B Test — Split participants randomly between two or more paths to test different email content or timing.
Exit — End the workflow at a specific point.
This is useful after conditional branches when participants no longer match your criteria.
How to create a workflow
Step 1: In the main navigation, click Automations.
Step 2: Click “+ Create workflow” in the top right.
Step 3: Choose a trigger, either Completed Submission or Payment Completed, and select the funnel.
Step 4: Click the + button to add actions and build your workflow.
Step 5: Configure each action. Write your email content, set wait durations, and define conditions.
Step 6: Save and activate the workflow.
Branching with Conditional Logic
The Conditional Logic action lets you split the workflow into different paths.
You can branch based on contact information, participant answers, scores, outcomes, email engagement such as opened or clicked, trigger data, and workflow variables.
You can also use conditions together with the Exit action to stop participants from continuing down a path once they no longer match your criteria.
Personalizing emails with variables
When adding a Send Email action, you can personalize both the subject line and the email body with data from the submission.
The recipient is always the contact collected in the funnel.
To insert a variable, type “@” or click the + icon to open the variable picker.
Available variables include contact form fields, question answers, outcome name, funnel name, hidden fields, and any custom fields from your funnel.
Email settings: SMTP, watermark, and attachments
Sent from | no-reply@involveme.com by default. You can connect your own SMTP sender to send from your own domain — this also improves deliverability. |
Watermark | The involve.me footer can be removed on Grow plan or higher. |
Opt-out link | The unsubscribe link at the bottom of the email cannot be removed, regardless of plan. Once someone opts out, they will not receive further emails from any of your workflows. |
Images | Images added to the email body support width sizing. You can choose 25%, 50%, 75%, 100%, or a custom pixel width. Images can also be made clickable with a URL, including variables such as #{{project.name}}. Click any image in the editor to adjust its size, alignment, and link. |
Attachments | Use the paperclip icon to attach files. Other files, such as PDFs, appear as a download link in the email. |
Tracking | Workflow emails automatically track opens and clicks. Follow-up emails also track opens and clicks when your own SMTP sender is configured. |
Preview | Click "Send Preview Email" to test how the email looks. Variables are not substituted in preview — complete a real test submission to see the full email. |
Monitoring workflow executions
The Automations dashboard shows all your workflows and their status, including Draft, Active, Completed, and Failed counts.
The workflow canvas displays open and click rates directly on each Send Email node, so you can review engagement at a glance.
Workflow emails also appear on the Contact Timeline. This lets you see when a workflow email was sent, opened, or clicked alongside follow-up emails and other contact activity.
To inspect a specific workflow, go to Automations, find your workflow, and click “View executions.”
Each execution shows one of three statuses:
Completed | All steps ran successfully |
Active | Currently in progress — waiting at a Wait step or condition |
Failed | Something needs attention. Check the error details to update your setup. |
Workflow examples
Here are some common workflows you can build:
Post-purchase follow-up
Payment Completed → Send confirmation email → Wait 3 days → Send review request
Quiz result drip
Completed Submission → Send result email → Wait 1 day → Conditional Logic (by outcome) → Send personalized follow-up
Welcome email series
Completed Submission → Send welcome email → Wait 2 days → Send tips → Wait 5 days → Send offer
Lead nurturing with A/B test
Completed Submission → Wait 1 day → A/B Test → Path A: promotional / Path B: educational → compare results
Cross-funnel journey
Completed Submission → Send thank-you → Wait 7 days → Invite to Funnel (feedback survey)
Best practices
Start simple. Begin with one or two steps before building more complex flows.
Use clear conditions. Branch on outcome names, scores, or funnel names instead of ambiguous free-text values.
Always test with real submissions. Do not rely only on preview. Complete a test submission and check View Executions.
Respect opt-outs. Once someone unsubscribes, they will not receive further emails from any workflow.
Space out your emails. Use Wait steps to give participants time between messages.
Troubleshooting
Workflow not starting | Make sure the workflow is set to Active and the trigger matches the correct funnel. |
Emails not arriving | Check spam/junk folders. Setting up your own SMTP sender significantly improves deliverability. |
Execution shows "Failed" | Open View Executions for error details. Common causes: missing email, bounced, or participant opted out. |
Conditions not working | Check field names and values — they are case-sensitive. Test with a known submission. |
⚠️ Accounts with high bounce or complaint rates may have their email capabilities temporarily and automatically limited or suspended. To support strong deliverability, keep your recipient lists clean and remove invalid email addresses.