Question 1

What is email automation and how is it different from broadcast campaigns?

Accepted Answer

Email automation is the practice of sending email in response to subscriber actions, time-based triggers, or attribute changes — rather than to a static list at a scheduled moment. **Where a broadcast campaign sends one message to one segment at one time, an automation runs continuously**, evaluating triggers against the live subscriber population and dispatching messages whenever the conditions match. Typical automations include welcome sequences fired by signup, abandoned-cart recovery fired by a cart-abandonment event from your application, win-back sequences fired by 60 days of inactivity, and post-purchase upsells fired by an order-fulfillment webhook. The Inbox OSS automation engine handles all of these patterns through one visual flow builder.

Question 2

What kind of triggers does the workflow builder support?

Accepted Answer

The builder supports six trigger types: **signup** (fires when a subscriber joins a list), **tag change** (a tag is added or removed), **custom event** (your application posts an event to our /api/v1/events endpoint — purchase, signup, plan upgrade, anything), **schedule** (cron-style: every Monday at 9am, the 1st of every month, etc.), **list join** (a subscriber is added to a specific list), and **attribute change** (a subscriber custom field crosses a threshold or matches a value). Multiple triggers can be combined into a single flow with AND/OR logic, so a flow can enter on signup OR custom-event-purchase, for instance.

Question 3

How does the visual flow builder compare to ActiveCampaign and Klaviyo?

Accepted Answer

The flow builder offers the same core node types as ActiveCampaign and Klaviyo — delay, branch (if/else), send, tag, webhook, exit — with the same drag-and-drop visual editor and live subscriber-count badges showing how many are currently at each step. **Where Inbox OSS differs is integration with the transactional layer**: an automation node can send via a template that is also used for transactional purposes, and the events generated by automation sends flow into the same webhook stream as transactional events. ActiveCampaign and Klaviyo are marketing-only platforms; integrating them with transactional email requires a separate ESP and custom event-stitching. Customer.io is the closest competitor architecturally, but its pricing model is per-monthly-active-profile rather than per-email-sent, which makes it costly for large lists with low send frequency.

Question 4

How do conditional branches work in an automation?

Accepted Answer

A branch node evaluates a condition and routes subscribers down one of two (or more) paths. Conditions can test **any subscriber property** (plan tier equals Pro, signup_source contains "google"), **recent behavior** (opened any email in the last 14 days, clicked link X in campaign Y), or **the response of an external API call** (a webhook node returns true/false to route the subscriber). Branches can be nested arbitrarily deep — a typical onboarding flow has 4-8 branch points evaluating engagement, plan upgrades, and feature usage. Branch evaluation happens at runtime, not when the subscriber enters the flow, so a property change after entry can route them down a different path at the next branch.

Question 5

What does the "Smart waits" feature do?

Accepted Answer

A wait node pauses a subscriber's progress through the flow until a condition is met. The four wait modes are: **wait N hours/days** (fixed duration), **wait until a specific date or time** (e.g., until next Tuesday at 9am subscriber-local), **wait within a window** (only continue if it is between 8am-6pm subscriber-local), and **wait until a subscriber does X** (e.g., until they click any email or complete a custom event, with a maximum wait of 7 days). Smart waits respect subscriber timezone — a 10am send is 10am wherever the subscriber lives — and pause cleanly during sender-configured quiet periods (no marketing emails on weekends, etc.).

Question 6

Can an automation hit my own backend mid-flow?

Accepted Answer

Yes — that is what the webhook step does. The webhook node POSTs to a URL you configure with the subscriber payload, then either proceeds immediately (fire-and-forget) or **pauses the subscriber at the node until your service responds** (request-response mode). Request-response is useful for runtime decisions: hit your billing service to check if the subscriber upgraded, hit your CRM to check lead score, hit a lookup service to enrich the subscriber profile. The response body is parsed as JSON and any key can be referenced in downstream branch conditions or template substitutions. Timeouts default to 10 seconds with up to 3 retries, configurable per node.

Question 7

How are re-entry and cooldown rules handled?

Accepted Answer

Every flow has configurable re-entry rules: **allow re-entry** (subscribers can enter the flow multiple times if they re-trigger), **block re-entry while in flow** (a subscriber cannot start the flow again until they finish or exit the previous run), **block re-entry permanently** (one-time-only — a subscriber who completes the flow once will never enter again), or **block re-entry within a cooldown window** (e.g., once every 30 days). Per-step cooldowns also exist — a send step can have a "do not send if this template was sent in the last N hours" guard to prevent message-storm bugs. These guardrails matter for behavioral triggers where the same action could fire repeatedly.

Question 8

How does this integrate with transactional email?

Accepted Answer

Transactional and marketing automations share the same template library, send infrastructure, suppression list, and event stream. A practical example: your application calls /api/v1/events with a purchase event; the automation engine triggers a post-purchase onboarding sequence (marketing) while the transactional API simultaneously fires the order-confirmation receipt (transactional). Both sends carry the same custom_args, route through the same DKIM-signed sender domain, and produce events on the same webhook firehose. **No other platform combines lifecycle marketing and transactional reliability at this depth** — Customer.io comes closest but pricing favors high-frequency low-volume use cases, where Inbox OSS pricing favors mixed workloads.

Question 9

Is there an audit history of changes to automations?

Accepted Answer

Yes. Every change to an automation — node added, removed, edited, branch condition changed, template swapped — is snapshotted with the editor identity, timestamp, and diff. The dashboard exposes the history for any flow with a one-click revert to any previous snapshot. This is essential for teams where multiple marketers and engineers collaborate on automations; you can see exactly when "the abandoned-cart open rate dropped" and which change caused it. The audit log is exportable as JSON for SOC 2 and ISO 27001 evidence requirements.

Question 10

Can I A/B test inside an automation?

Accepted Answer

Yes. The flow builder includes a split node that randomly routes subscribers to one of N variants with configurable weights (default 50/50 for two-variant, configurable for n-variant). Variant performance is reported in the same place as the rest of the flow — open rate, click rate, downstream conversion attribution — and winners can be auto-promoted by setting a confidence threshold and minimum sample size. Continuous A/B testing inside long-running flows is a particularly high-leverage use case: small subject-line lift compounds across millions of automation sends over time.

Set the journey once. Let the platform run it.

Visual flow builder

Trigger on anything

Smart waits

Conditional branches

Webhook steps

Re-entry rules

Frequently asked questions about email automation

Start sending email in under 5 minutes.