Email Automation

Email automation sends messages when defined conditions are met. Those conditions can include a contact joining your audience, a property changing, an event from your application, or a timer completing.

In Loops, you build these sequences as workflows with triggers, emails, timers, audience filters and branches. Automation is useful when people need the same kind of help at different times, such as a setup reminder after their own signup.

An onboarding reminder, step by step

Consider this illustrative workflow for a SaaS trial. Your application sends an event named trialStarted and maintains a custom Boolean contact property named setupComplete. You define these names and connect the application data to Loops.

Start the workflow with the trialStarted event and send a welcome email linking to setup. Add a one-day timer. Then apply an audience filter requiring setupComplete to equal false before sending the reminder. The one-day delay is an example to test against your product’s setup process, not a universal schedule.

Set that filter to apply to “All following nodes” if later reminders should also depend on setup remaining incomplete. Loops rechecks this filter when the contact reaches each following node. A “Next node only” filter checks once and does not protect every later send. See the workflow documentation for these behaviors.

Decide when the messages stop

Keep setup status current so someone who finishes independently does not receive another setup prompt. Check whether repeated events could start duplicate journeys and whether another workflow sends a similar email. A workflow should have a clear end even when the person takes no action.

Subscription status also matters. Loops uses the contact’s subscribed status for campaigns and workflow emails. Routine data syncs should not reset a previous unsubscribe. Review the contact property rules before including that field in API updates.

Test the route as well as the email

Use test contacts to exercise incomplete setup, completed setup, missing data and repeated entry. Loops supports addresses at example.com and test.com for checking workflow movement without delivering mail to those addresses. Send a separate preview to inspect the actual email.

Once the workflow runs, compare completed setups with the number of eligible users. Delivery failures, complaints and unexpected repeat sends are reasons to inspect the workflow before adding more emails.

Related reading

Drip campaign · Autoresponder · Lead nurturing · Onboarding email examples