AUTOMATIONS

The follow-up happens whether or not you remember

Rules go live by publishing a version. Test them on the records you pick with nothing written, open any run and read what each step did, and route every new lead to the right person the instant it arrives.

Free plan, not a trial · Test mode on every rule · Government tenders across six markets QatarBahrainSaudi ArabiaKuwaitOmanUnited Arab Emirates

Triggers

The moment something happens, the next step is done

A rule starts from any of eight moments in the CRM, on any object.

Record created
on any object, your own included
Record updated
or only when the attributes you name change, such as Stage or Owner
Record archived
when a record leaves the working set
Added to a list
any list, or one named list
Task created
on the record the task belongs to
Task completed
when someone ticks it off
A date arrives
on the day, or days before or after any stored date: three days before Closing date, for example
Manual
run for real on the records you pick

Conditions use the same and/or/not filters as your views. Publishing a version is the on switch, and a rule only ever acts from the moment it goes live.

Runs

Test it on three records before it touches three hundred

Every run is something you can open. Each step says what it did, or what it would have done, under the version it ran.

Test run

Pick the records and run the rule in test mode. Every step records what it would have done: "would have set Stage to Shortlisted", "would have created a task". Nothing is written.

Real run

The same steps write for real, and every value they write is tagged automation. Cancel stops a run and its queued mail; Replay runs a finished one again against the current version.

Waits and quiet hours

A step can wait minutes or weeks and pick up where it left off. Email waits for business hours, and a run stops itself the moment the contact replies.

A step that fails retries on its own. If it keeps failing, the run is kept with its state intact and the owner gets one notification.

Routing

Every new lead lands with the right person

Territory rules claim the records that match them; a round-robin pool shares the rest evenly. Assignment happens the instant a record arrives, so two leads landing together never end up with the same next person.

Territory rules
by country, sector, size or any attribute you choose
Round robin
a pool of people, each taking the next record in turn
Ownership
the assigned owner is written on the record, where every view and report already reads it

Webhooks and API

Doors in both directions, both signed

Outbound, every event can reach your own systems as a signed delivery that retries until it lands. Inbound, a write-scoped API key lets any tool create a deal, move a stage, add a contact or log an activity, with Zapier and Make guides in the app.

  1. Event
  2. One delivery per subscriber
  3. Signed and timestamped
  4. Delivered
  5. ReplayAny delivery, any time

API keys carry Read or Write and an expiry, and every request is logged. The docs sit beside the keys in the app and on the developers page; more connectors are on integrations.

Frequently asked questions

What starts a run?

One of eight triggers: record created, record updated (or only when chosen attributes change), record archived, added to a list, task created, task completed, a date arriving, or a manual run on picked records. Conditions use the same filters as views.

Can I test a rule before it does anything?

Yes. Test mode runs the rule on the records you pick and every step records what it would have done. Nothing is written, and the run is marked Test.

What happens when a step fails?

It retries on its own. If it keeps failing, the run is kept with its state intact so you can read which step failed and why, then Replay it. The rule's owner gets one notification per failing rule, not one per run.

Are webhooks signed?

Yes. Every outbound delivery carries a timestamp and a signature over the exact body, using a secret shown once at creation. Inbound actions are keyed to a write-scoped API key and logged to the same request log.

Publish one rule and watch it run.

Build a one-step rule, run it in test mode, and read the run end to end. Automations are on the Pro list; Free starts the CRM.

Free plan · 32,822 investors · six markets