Automations

Automations run your program while you sleep. There are two levels: flows you design yourself on a canvas, and one-toggle quick rules.

The flow builder

A flow starts from a trigger — a real Ecomyard event: delivery submitted or approved, revision requested, application received, affiliate joined, brief claimed, gift claimed, payout paid, or an affiliate going inactive.

From there you chain steps on the canvas:

• Time delay — wait minutes, hours or days.
• Conditional split — branch Yes/No on a live affiliate field (tier, country, revenue, referrals, posts, status), checked at the moment the event fires.
• Actions — send an email (via Klaviyo), an SMS, a Slack message to your team, an internal alert, or POST a webhook.

The canvas pans with the hand tool (drag anywhere) and zooms from the bottom-right controls. The top bar holds Show analytics (per-step stats with a date range), Flow history (every save, searchable) and the flow's details. Insert steps anywhere with the + points between cards (or click the palette), configure each step in the side panel, and personalise messages with {{first_name}}, {{name}}, {{tier}} and {{code}}. Flows switch between draft, live and paused.

Quick rules

Below the flows sit one-toggle rules for the common cases: inactivity reminders, payout thresholds, top-performer rewards and unclaimed gifts.

Email, SMS and Slack delivery run through their integrations (Klaviyo, Slack) once connected; until then flows save and validate so everything is ready to switch on.

Runs

Flows now actually execute. Every event in the product (a delivery submitted from the portal, an approval, a claimed gift, a payout, a new application) starts a run for each live flow on that trigger. Runs walk the canvas for real: time delays park the run and a scheduler resumes it when the wait elapses, conditional splits evaluate the affiliate's live data (tier, country, revenue, referrals, posts, activity score), and internal alerts land as notifications under the bell. Email, SMS, Slack and webhooks are recorded per run and start delivering with the integration rollout.

Time-based triggers (affiliate inactive, gift not claimed, enters the Top 3) are evaluated on a schedule, one run per affiliate per flow per 30 days.

Turn on Show analytics in the builder to see how many runs entered each step, and the flow list shows total runs per flow.