Automation builder

The Automation builder is the visual editor where you set an automation's trigger and lay out the emails, delays, conditions, actions and integrations that follow it.

The builder at a glance

To create an automation, click New automation on the Automations list, give it a Name, pick What starts it? and click Create and open builder. You can fine-tune or change the trigger later in the builder.

The builder has two halves:

  • The canvas on the left shows the automation as a flowchart, one card per step, starting with the trigger. Each card shows the kind of step (Start, Email, Delay, Condition, Action, Webhook, Get data or Automation) and what it does. A card marked Needs setup still has something to finish. Drag cards to move them, and use the buttons at the bottom left to Zoom in, Zoom out or Fit the whole automation.
  • The panel on the right holds the settings of whichever step you click. With no step selected it shows an Overview with Runs so far (Completed, In progress, Failed) and a View full report button. On a narrow screen only one half shows at a time: switch with Show panel and Show canvas.

The title bar carries the automation itself: a back arrow to the Automations list, the automation's name (click it to Rename it) and a status badge — Live, Off or Needs setup. On the right are Generate with AI, Tidy up, the On / Off switch and Done.

Adding, moving and deleting steps is saved right away. A step's own settings are saved with the Save button at the bottom of its panel; Cancel closes the panel without saving.

Getting Started with Triggers

Every automation begins with a trigger — the event that starts the sequence. The trigger defines when the automation runs and for whom. Until you set one, the first card on the canvas reads Choose what starts it. Click it to open the Trigger panel, pick an option under What starts this automation?, fill in what it asks for and click Save.

Available Trigger Types

You start it by hand

Add contacts to the automation yourself, whenever you choose. Good for one-off sends and for testing.

A date arrives

Runs before, on or after a date saved on the contact, like a birthday or a trial end. Good for renewals, anniversaries and trial follow-ups.

Someone unsubscribes

Runs the moment a contact leaves your list. Good for tidying up or saying goodbye.

Someone subscribes

Runs when a new subscriber joins — once they confirm their email address. Marked Most used: a welcome series is what most people build first.

Your app calls our API

Start the automation from your own website or app with a single API call.

Manual Triggers

You start it by hand needs nothing else — the panel just says it starts only for contacts you add yourself. To start it for someone, open the contact on the Subscribers page, open the Actions menu, choose Trigger automation, pick the automation and click Start.

Date-Based Triggers

A date arrives schedules the automation against a date saved on each contact. Configure it with:

  • Which contacts are included?: choose Groups or Segments (two tabs — you pick one or the other) and select one or more. Only these contacts are checked for the date
  • Date: which date to watch — Added At under Built-in, or any custom date or date-and-time field under Your custom fields. Contacts with this date empty are skipped
  • Start: Before, On the date or After the date
  • How long before or after: for Before and After, a whole number and a unit
  • Time of day: for plain date fields, the hour and minute to start at, in UTC

Choose the Contacts

Select the groups or the segments the automation should apply to. Save stays disabled until you have picked at least one

Choose the Date

Pick the date field that decides when the automation runs

Set the Start

Choose Before, On the date or After the target date

Set How Long (if needed)

For Before and After, enter how far away. A date-and-time field offers minutes, hours, days, weeks, months and years; a plain date field offers days, weeks, months and years only

Set the Time of Day (for plain date fields)

For a plain date field, pick the hour and minute (UTC) to start at

How a plain date field matches. At the time of day you set, the automation starts for every subscriber whose date falls on the target day — today, or today moved by your Before/After distance. The whole date counts, year included, so it runs once per subscriber and does not repeat every year: a birthday saved as 1990-05-12 never comes round again. For a one-time anniversary, use After with 1 year. If you switch the automation on after today's time has passed, today's subscribers start right away. A run that fails for a subscriber is not started again.

Event-Based Triggers

Neither of these needs anything else set up:

  • Someone unsubscribes: starts for each contact who unsubscribes, immediately
  • Someone subscribes: starts for each new subscriber once they confirm their email address through the confirmation email

API Triggers

Your app calls our API lets an outside system start the automation. When you select it, the trigger panel shows Start it from your app: a ready-made code example with your own automation's ID already filled in. Copy it into your website or app and replace your_api_key, the email address and the example data with your own.

await fetch("https://yaplet.com/api/newsletter/workflow/start", {
    method: "POST",
    headers: {
        "Content-Type": "application/json",
        "Y-API-Key": "your_api_key",
    },
    body: JSON.stringify({
        email: "[email protected]",
        workflow_id: "your-workflow-id",
        key1: "value1",
        key2: "value2",
    }),
});
The endpoint address and the workflow_id field keep the feature's old name, so that integrations written before it was renamed keep working. Use them exactly as shown.

Custom data fields are sent as top-level fields alongside email and workflow_id. They become available in later Send email and Send a webhook steps using {{key1}}, {{key2}} placeholders.

For complete API documentation including error codes, field reference, and integration best practices, see the Automation API documentation.

Sending Priority

Under Advanced at the bottom of the trigger panel (folded away; its closed row shows the current setting, for example Priority: Normal), Sending priority decides which emails wait when Gmail slows down mail from your domain. Pick Low, Normal (every automation starts here) or High, then click Save.

  • High — never held back. Use it for cart, order and welcome emails.
  • Normal — during a Gmail slowdown, Gmail emails to people who never open wait until the slowdown ends; everyone else gets them as usual.
  • Low — held back the same way as Normal, and sent after Normal when the domain is busy.
When a slowdown ends, held automation emails go out unless they are more than 7 days old — those are dropped. Duplicating an automation keeps its priority.

Building Your Automation

After setting up your trigger, build the sequence by adding steps. Click the round + button on the line under a card (Add a step here) to open Add a step, then pick what happens next. You set the new step up in the panel on the right. The steps come in four groups:

  • Send: Send email
  • Timing and paths: Wait, If / else and Start another automation
  • Contact: Update contact
  • Connect your systems: Send a webhook and Fetch data

A step you add between two others slots in between them, and the steps after it stay connected. To remove a step, click it and choose Delete step in the ⋯ menu at the top right of its panel. The steps after it move up and stay connected, and if it was an email step, the email written for it is deleted too. This can't be undone.

Send Email

Send email sends a message to each contact who reaches it, then moves them on to the next step. The step's panel walks you through it:

Who Is It From?

Set the Sender name and choose the Sender email. Only addresses on a verified domain are listed — if you have none yet, Set up a domain takes you to set one up first. Choose the sender email before you create the email, because the email is created with it

What Do They See in the Inbox?

Set the Subject and the optional Preview text. Both support {{variable}} merge tags with optional fallbacks ({{name|there}}), filled in per recipient at send time

What Does the Email Say?

Click Create the email. The How do you want to start this email? dialog offers three starting points, each with its gallery opening inline underneath:

  • From scratch — an empty editor; build the email yourself
  • From a template — start from a premade design or one of your saved templates, then change anything
  • From a previous email — copy an email you sent before

To have the AI write it, pick a starting point here and then use the Generate with AI button in the editor's toolbar.

If you open the AI dialog on a brand-new email step and close it without generating anything, the empty step is discarded rather than left behind half-configured.

Design and Test Your Email

Once the email exists, the panel shows a small preview with Edit email, which opens the drag-and-drop email builder (save your changes there — the step sends the new version from then on), and Send a test. Start over with a different starting point replaces the email's content with a new start; the subject and sender stay as they are

Automation emails go through the same safety check as campaign emails, right before each one goes out. One that fails, or whose sender is not on a verified domain, is not sent to that person (it counts as failed and is not retried) and the contact stays on the list. The workspace's owner gets a "Newsletter email not sent" notification with an Open automations button.

Available Email Creation Options

From scratch: Begin with a blank canvas and build your email design using the visual editor.

From a template: Start from a premade design or one of your saved templates.

From a previous email: Reuse successful email content from your previous campaigns to maintain consistency.

Email Editor Features

The email editor provides a full-featured design interface for creating compelling content. For detailed information about the email builder capabilities, see Email Design and Templates.

Wait

Wait adds a pause between steps, letting you space out your communications deliberately. Contacts wait here for the time you set, then move on to the next step.

Configuration Options:

  • Wait for: a whole number, plus a Unit — minutes, hours, days, weeks or months. Under Common waits, one click sets 1 hour, 1 day, 3 days or 1 week
  • Each unit has its own ceiling: 1–60 minutes, 1–24 hours, 1–31 days, 1–52 weeks, or 1–12 months. A single step cannot wait 90 minutes — minutes stop at 60. Chain two Wait steps instead: one of 1 hour, then one of 30 minutes

Use Cases:

  • Give subscribers time to engage before sending follow-ups
  • Space out educational content in nurture sequences
  • Respect deliverability best practices with appropriate timing

If / Else

If / else creates branching logic: it splits the automation in two, and each contact goes down the Yes path (contacts who match your rules) or the No path (everyone else). The card gets a Yes and a No button, each adding the next step on that path. If you add an If / else in front of steps that already exist, Which path keeps the steps below? asks whether they carry on down The Yes path or The No path; the other path starts empty.

Available Condition Types

Fields

Check contact field values like email, name, custom fields, and subscription status.

Group membership

Evaluate if contacts belong to specific groups.

Segment membership

Check against saved segments with their predefined filters.

Building Conditions

Under Who goes down the Yes path?, use the rule builder to decide which branch a contact takes. Save stays disabled until there is at least one finished rule:

Add a Rule

Click Add condition and choose the type: Fields, Group membership or Segment membership

Choose Criteria

Pick the specific field, group, or segment to evaluate

Set Comparison

Select how to compare the contact's data (Equals, Contains, More than, etc.)

Enter Values

Input comparison values or select from available options

Combine Logic

With several rules, choose whether a contact must match all of them (AND) or just one (OR). Add nested group adds a group of rules

Field Operators

Different field types support different comparisons:

Email, name, custom text fields (State and Email provider are dropdowns and offer only Equals / Does not equal):

  • Equals / Does not equal - Exact match
  • Contains / Does not contain - Partial text match
  • Starts with / Ends with (and their "Does not" versions) - Text position matching
  • Is set / Is not set - Check for value existence
Contacts matching your conditions follow the Yes path, while others take the No path. Use this to create personalized branches based on contact characteristics.

Update Contact

Update contact changes something about the contact when they reach this step, then moves on to the next step. Under What should happen to the contact?, choose one of:

Change a field: Modify a contact detail. Only your own custom fields can be changed here.

  • Text fields: set a New value that replaces whatever the field holds now
  • Number fields: Set to a value, Increase by or Decrease by
  • Date fields: Set to a value, Increase by or Decrease by a number of days, weeks and so on, Set to the moment this step runs, or The moment this step runs, plus… / minus…. The date is worked out separately for each contact, at the moment they reach this step

Group Management:

  • Add to groups: Put the contact into additional groups; they stay in the groups they're already in
  • Move between groups: Take the contact out of the groups under Take out of and put them into the groups under Put into. A group can't be on both sides
  • Remove from groups: Take the contact out of the groups you pick; groups they aren't in are skipped

Subscription Management:

  • Unsubscribe the contact: Immediately mark the contact as unsubscribed from your newsletters

Send a Webhook

Send a webhook sends data to an external service when a contact reaches it, enabling integrations with CRMs, analytics platforms, and custom applications. A webhook is an automatic message from Yaplet to another app, and a tool like Zapier or Make can receive it.

Configuration

Where Should It Go?

Enter the Web address (URL) the receiving app gave you (often called the "webhook URL"). You can put contact details in it too, like {{email}}

What Should It Send?

Each row becomes one item in the message. Type a Name on the left and, on the right, a fixed Value or a contact detail like {{email}}. Add a row adds another; Show the exact message previews what is sent

How Does the App Know It Came From You?

Enter a Secret key, or click Generate for a random one and copy it into the receiving app

Try It

Send a test sends one message right now, filled with made-up test contact details, so you can check the other app receives it. It needs the web address and the secret key first

Authentication

Webhooks include a Signature header containing an HMAC SHA-256 hash of your secret key. Verify requests on your server by hashing the same key and comparing signatures.

Available Field Tags

In the step's panel, Contact details you can use lists the tags; click one to copy it, then paste it into the address or a value. Use these placeholders in webhook URLs and body values:

Basic Fields:

  • {{email}} - Subscriber email address
  • {{name}} - Subscriber name
  • {{created_at}} - When subscriber was added
  • {{state}} - Subscriber status
  • {{engagement}}, {{isp}} (email provider), {{last_active_at}}, {{last_opened_at}}, {{last_clicked_at}}, {{click_count}}, {{emails_received}}, {{last_emailed_at}} - Engagement score and activity

Custom Fields: {{your_custom_field_tag}} for any custom fields you've created

Dynamic Data: Any custom data sent via API triggers or fetched via Fetch data steps

All placeholders accept an optional fallback after a pipe — {{name|there}} — used when the value is missing or empty.

Fetch Data

Fetch data asks another app — for example your shop or your own system — for extra details about the contact, so the next emails and webhooks can use them. The automation waits for the answer, then moves on.

Configuration

Where Should the Data Come From?

Enter the Web address (URL) of the other app (its "API endpoint"). Put a contact detail in it, like {{email}}, so the app knows who you're asking about. Yaplet only reads from this address (a GET request) and sends nothing else

How Does the App Know It's You?

Enter a Secret key, or click Generate for a random one and copy it into the other app

Try It

Try it now asks the other app once, with made-up test contact details, and shows What the other app answered

Using the Answer

Every item in the answer can be used in later steps as a tag with its name: an item called "points" becomes {{points}}

Response Format Requirements

The answer must be a JSON object with:

  • String keys only
  • String or number values
  • Maximum 20 fields per response

Example response format:

{
    "user_id": "12345",
    "account_type": "premium",
    "last_login": "2024-01-15"
}

Authentication

Like webhooks, fetch requests include a Signature header with HMAC SHA-256 authentication.

Start Another Automation

Start another automation hands the contact over to a second automation, which takes them from its first step, so you can keep shared logic in one place instead of copying it. A placed card reads Switch to automation: {name}.

Use Cases

  • Common Entry Sequences: Start with a universal welcome flow, then branch to specialized nurture tracks
  • Re-engagement Campaigns: Route inactive subscribers to different recovery automations
  • Segmentation Logic: Send different subscriber types through optimized sequences
Under Which automation should take over?, the picker lists every other automation of yours that is switched on — not the one you are editing. If none is switched on yet, switch one on and come back. Pick an automation that starts by hand (its trigger is You start it by hand), so it doesn't also start on its own.
This step ends the current automation's run for that contact — the second automation carries on from there. That is why the canvas offers no + under this card: anything placed below it would never run. Make it the last step on its branch.

Tidy Up

As an automation grows with multiple branches and conditions, cards can overlap or become hard to follow. The Tidy up button instantly reorganizes the whole flowchart into a clean, balanced structure.

Click Tidy up in the title bar to reorganize all cards. The canvas then zooms and pans to fit everything in view.

The cards are also tidied up automatically whenever you add or delete a step, and after the AI generates an automation, so the canvas stays organized as you build.

The layout engine:

  • Centers the trigger at the top and arranges all child cards below it
  • Balances branches — If / else steps (yes/no paths) get equal horizontal space
  • Spaces evenly — consistent vertical and horizontal gaps between all cards
  • Handles nesting — deeply branched automations are laid out without overlaps

Generate with AI

You can generate an entire automation from a plain-text description. Instead of adding steps one by one, describe what you want it to do and AI builds the whole flowchart for you.

How to Use It

Open the generate modal

Click Generate with AI at the top right of the title bar. The dialog is titled Generate automation with AI.

Choose a trigger type (optional)

Select a Trigger type (optional) from the dropdown to guide the AI, or leave it on Auto-detect and let the AI choose based on your description. Available trigger types:

  • Auto-detect — AI picks the best trigger for your use case
  • Manual — Start the automation on demand
  • On Subscribe — Trigger when someone joins
  • On Unsubscribe — Trigger when someone leaves
  • Date-based — Trigger relative to a date field
  • API — Trigger from an external system

Describe your automation

Write a plain-English Automation description of what you want it to do. Be as specific as you like — mention timing, conditions, email topics, and actions.

Example descriptions:

  • "When someone subscribes, wait 1 day, send a welcome email, wait 3 days, send a tips email"
  • "After subscribing, send a welcome email. Wait 5 days, check if they opened it. If yes, send a thank-you. If no, send a reminder with a different subject line."
  • "Unsubscribe trigger: send a feedback survey email immediately, wait 7 days, if they haven't re-subscribed, remove them from the Active Users group"

Review and confirm

If the canvas already has steps, Replace current automation? asks you to confirm before the AI replaces them.

What Gets Generated

The AI creates the complete structure including:

  • Trigger configuration with the appropriate settings
  • Send email steps with subject lines and preview text (you design the email content separately using the email editor)
  • Wait steps with appropriate wait times
  • If / else steps with branching logic based on your description
  • Update contact steps for group management, field updates, or unsubscribes
  • Send a webhook and Fetch data steps when your description involves external integrations
The AI uses your organization's real data — your contact groups, custom fields, other automations that are switched on, and verified sender emails — so generated steps reference actual resources in your account.

After Generation

Once the AI has built the structure:

  1. Cards are tidied up — the layout engine positions everything cleanly
  2. Email content is not included — email steps have subjects and preview text, but you need to design the actual email content using the email editor on each step
  3. Review the structure — check that the logic matches your intent, and adjust any steps as needed
  4. Switch it on when ready — test your emails and switch the automation on
If the AI references contact groups or fields that don't exist in your account, those steps are marked Needs setup with a warning. A step pointing at an automation that is switched off or gone is removed outright, with a warning saying so. Fix the references before switching it on.

Automation Management

Validation and Activation

The On / Off switch in the title bar stays disabled until the automation is ready, and the status badge reads Needs setup (point at the switch to see why). With no step selected, the panel's Overview also shows a warning, Not ready to switch on yet: Set up the trigger and add at least one step, then finish every step marked "Needs setup". In practice that means:

  • The trigger is set
  • Every card on the canvas is fully configured — none is marked Needs setup
  • There is at least one step after the trigger

When the automation is ready, the badge reads Off. Flip the switch to On and confirm Turn on this automation? — from then on it starts for everyone its trigger brings in, and the badge reads Live.

If an automation that is already on later becomes unfinished, Yaplet switches it off for you rather than running something broken.

The Automations list shows the same Live, Off or Needs setup badge on each automation. Turning one on or off is in the ⋯ menu on its row (Turn on / Turn off), which asks first, so a stray click changes nothing. For an unfinished automation the badge tells you why it can't be turned on: Finish every step in the editor before turning it on.

Every email step needs a finished email

Switching an automation on is also refused when any Send email step has nothing to send. The automation stays off and a message explains which step is at fault:

  • An email step has no email yet — the step was added but its email was never created.
  • An email step has an empty body — the email exists but its content is blank.

Open the named step, build its email, save, and switch the automation on again.

Switching an automation off is never blocked, and it takes effect at once: everyone partway through the automation is dropped — their next emails are not sent, and switching it back on does not resume them. Yaplet asks first (Turn off this automation?) and tells you how many people are partway through.

Monitoring Performance

With no step selected, the panel's Overview shows Runs so far:

  • Completed: runs that finished
  • In progress: runs waiting to execute or partway through
  • Failed: runs that hit an error

View full report opens the automation's report.

Testing an Automation

  • Click Send a test on the Send email step to send a test email
  • Use Send a test on a Send a webhook step and Try it now on a Fetch data step to verify integrations
  • Start the automation by hand for a test contact from their page (Actions → Trigger automation)

Best Practices

Timing: Space out emails appropriately to avoid overwhelming subscribers and maintain deliverability.
Segmentation: Use If / else steps to create personalized paths based on subscriber behavior and preferences.
Testing: Always test with a small group of subscribers before switching an automation on for everyone.
Monitoring: Regularly review performance and adjust based on engagement metrics.
Reuse: Use Start another automation to build reusable pieces and keep each automation readable.

© 2026 Yaplet. All rights reserved.