Skip to main content

Automation rules

Where: Automation → Automation rules

Automation → Automation rules lists your custom rules — columns Name, “When this happens”, “Only if”, “Then”, Status — with Enable/Disable buttons per row.

Figure: Automation → Rules — visual trigger → condition → action builder

Automation → Rules — visual trigger → condition → action builder

  1. Press “New rule”. A visual canvas opens: a Trigger node flows into a Conditions node and then into one or more Action nodes.
  2. Name the rule (placeholder: “e.g. Email buyer when order ships”).
  3. Pick the trigger event: “An order’s status changes”, “An order is placed”, “A buyer requests a quote (RFQ)”, “A storefront visitor sends an enquiry”, “A vendor applies to sell”, “A buyer accepts a quote”, “A buyer declines a quote”, “A quote expires”, “Every hour”, or “Every day”.
  4. Add “only if” conditions using the operators = equals, ≠ not equals, > greater than, ≥ at least, < less than, ≤ at most (e.g. only if order total ≥ 100,000).
  5. Press “Add action” and pick what happens: Email the customer · Auto-price + send a quote for the RFQ · Open a pipeline opportunity for the RFQ · Alert the team (in-app) · Email the team · Expire stale quotes · Mark invoices overdue + dun · Follow up on expiring quotes · Recover abandoned carts. Each action has its own labelled parameters (e.g. “Quote valid for (days)”).
  6. Press Save — toast “Rule saved”.

Validation messages you might meet: “Name and trigger event are required.” · ‘Each “only if” line needs something to check.’ · “Add at least one thing to do, and pick what each one does.”

Branches, waits and trying a rule out​

  • Branch per action. Each action can carry its own if (same operators as “only if”), so one rule can do different things: alert the rep for a repeat customer, email a first-time buyer.
  • Wait for an event, or a timeout. Give an action a delay and wait_for (one or more events): it runs when the delay is up unless one of those events reached the same quote, request, order or customer first — then it steps aside and the run ledger shows skipped. “Alert me in 3 days unless the buyer accepted or declined” is one action.
  • Test on last 30 days. In the builder, this replays your trigger and conditions over the events the platform actually logged, and tells you how many times the rule would have fired before you save it.
  • Steps that follow a step. An action can carry then: steps that run after it, with whatever it produced merged into the data they see. A follow-up task hands over task_id and its subject; an AI sort (classify) reads one field, picks one of your labels and writes it back — so a later step can branch on label.
  • A human step with a deadline. Create a task, then a step that waits for A task is marked done with a delay: if nobody marks it done in time, the escalation runs; if someone does, it steps aside. The prebuilt Call every new request within 2 days — escalate if not is exactly this; marking the task done (Customers → timeline, or the API) is what the step listens for.
  • Versions. Every save keeps the previous version. In the builder, History lists them with a Restore button; restoring is itself a change, so the current version is kept too.
  • Starters. Automation → Prebuilt opens with bundles for a kind of business — distributor quote-to-cash, make-to-order manufacturer, services on retainer, dealer network. Install all switches every automation in the bundle on; each can still be turned off on its own.