Skip to main content
Merchant
Automation

Automation rules

How to automate routine merchant workflows based on triggering events.

What this is

The Automation page lets you build rules that react to events like a submitted application, an inactive affiliate, an approved commission, an overdue payment, a reported payment problem, an unhealthy integration, tracking going silent, or a received conversion.

Why it matters

Automation reduces manual follow-up for routine situations, while sensitive actions still require your approval before they run.

How to do it

  1. Open Automation and review existing rules, or create a new one.
  2. Choose a triggering event from the list: application submitted, application pending, invitation unanswered, affiliate inactive, commission approved, payment overdue, payment problem reported, integration unhealthy, tracking stops receiving events, or conversion received.
  3. Choose an action: notify designated staff, notify affiliate, create a merchant reminder, flag for review, assign affiliate group, or request relationship termination.
  4. Save the rule and use Test rule to confirm it behaves as expected before turning it on.
  5. Toggle the rule active or inactive using the switch control.
  6. Review pending approvals and work items on the Automation page for any action that requires your sign-off before executing, particularly for sensitive actions like terminating a relationship or reversing a commission.

What happens next

Active rules run automatically when their trigger occurs. Sensitive actions wait in an approvals queue for you to decide; the platform also enforces a daily action limit per rule to prevent runaway automation.

Common mistakes

Do not assume every action executes immediately; actions like "request relationship termination" or reversing a commission require your explicit approval.

See Affiliate Segments for the "assign affiliate group" action's target audiences.

Last updated September 9, 2026.