Automations

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

Start from a template

New flow opens on seven ready-made flows: a welcome follow-up, a first sale heads-up, a tier shout-out, a win-back for quiet affiliates, a gift reminder, a thank-you for content and a Top 3 celebration. Each card says what it does and which steps it runs. Open as draft creates it and opens the builder, so you can change anything first. Turn on creates it live straight away. A template with a Slack step always opens as a draft, because you pick the channel.

Where Ecomyard already mails the affiliate on the same moment, the card says so, and the template waits before it writes so the two never arrive together.

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, an affiliate's first sale, an affiliate reaching a new tier, 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, an SMS, a Slack message to your team, an internal alert, or POST a webhook.

Drag anywhere on the canvas to move around, on a card as well: a click still opens the card. Two fingers or the scroll wheel pan too, and a pinch, or Ctrl or Cmd with the scroll wheel, zooms around your cursor. The controls bottom right zoom in and out, go back to 100% when you click the percentage, and fit the whole flow on screen. The top bar holds Show analytics (per-step stats with a date range), Flow history (every save, searchable), the flow's details and Exit, which asks before it drops unsaved changes. The builder folds the sidebar away to give the canvas the room; the toggle top left brings it back. Insert steps anywhere with the + points between cards (or click the palette), and configure each step in the side panel that opens when you select it. Flows switch between draft, live and paused.

Slack and email steps

A new Slack or email step starts with a message written for the flow's trigger, so it is ready to send as is. Switch the trigger and any text you haven't touched follows along; your own words stay.

• Channel. A Slack step picks from the channels the Ecomyard app is in, so it can't point at one it can't post to. Missing a channel? Invite the app to it in Slack, then click refresh under the list.
• Merge fields. Click First name, Full name, Tier or Code under the message and the field lands where your cursor is. Alert steps have the same chips and fill them the same way. Application received has no affiliate yet, so it offers none.
• Going live. A flow can't go live while a step is unfinished: a Slack step without a channel or a message, an email without a subject or a body, a webhook without an https address, a split without a value. Saving it as Live opens that step instead. A Slack step in a channel the Ecomyard app isn't in is refused too, with the channel named.
• Second mails. Ecomyard already mails the affiliate when they join (Welcome), when a payout is paid, when a commission is earned and when they reach a new tier, and whenever your team writes to them about a delivery. An email step on those triggers says so, with a link to switch the automatic mail off under Notifications.
• When a step fails. A Slack, email or webhook step that can't deliver gets a red count on its card and on the flow in your list, with the reason in the step's panel. The bell tells you too, and through it your team's email and Slack alerts, at most once a day per step.

Quick rules

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

Email and Slack steps deliver today: email through Ecomyard's own sender, Slack through your connected workspace and channel. SMS waits on its integration; those steps save and validate so they are 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. Affiliate inactive waits until somebody has been in for 30 days, and counts both posts and orders: somebody who joined last week is new, not quiet.

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

The Monday recap

Every Monday morning, Ecomyard posts last week's numbers to your Slack alerts channel: new affiliates, creatives added, referral revenue on your store's real orders, and what you paid to creators (plus creative spend when there was any). It reads straight from your workspace data, and a completely quiet week posts nothing.

There is nothing to configure beyond connecting Slack and picking an alerts channel, which an owner or an admin does on the Slack page under Connections.