Skip to content

Exclusive 50% off for 36 months for the first 100 Professional accounts, until 31 December 2026. See the programme →

Automation

What you know should happen, and nobody will do

Chase a quote at D+7, alert a manager if nobody answered within thirty minutes, ask for a review after delivery: simple, obvious gestures that never happen because they depend on a busy person's memory.

No credit card required

How it works

One trigger, one sequence, as long as it takes

A trigger from any hub

A submitted form, a missed call, a signed quote, an opened complaint, a date coming up: the trigger can come from anywhere in the suite. That is what separates a workflow from a mailing rule.

  • Events from every hub, custom objects included
  • Trigger on a date or a deadline
  • Inbound webhook for outside tools
  • Dry run before activation

Delays that hold for months

A workflow can wait three days, or six months, consuming nothing in between. That is what makes long sequences possible — chasing a hesitant applicant, re-engaging a dormant customer — which campaign tools cannot hold.

  • Durable waits, by the minute or by the month
  • Resumes exactly where it stopped
  • Conditions re-evaluated on waking
  • Stops automatically if the awaited event occurs

Use cases

What it looks like for someone like you

Detailed scenarios with figures, where this hub plays a central role: the starting situation, what gets put in place, what it shifts.

See all use cases

FAQ

Frequently asked questions

Do we need to code?

No. Workflows are assembled from blocks: trigger, condition, action. The API call exists for those who need it, and is never required.

What if a workflow loops?

A guard stops an execution that calls itself, and the log shows where. A workflow cannot spin forever without you seeing it.

Do AI actions consume credits?

Yes, as used: text, image and voice generation are metered like everywhere else, and the workflow stops cleanly if the balance is short.

Can a scenario be tested before going live?

Yes: run it on a control record and read the step-by-step trace before opening it to everyone.

What happens if an action fails?

The execution is traced with its error, and credit-consuming sends use an idempotency key: an action is never billed twice because of a retry.

Another question? Write to us — a human will answer.

Ready to bring all your tools together?

Create your free account in two minutes: CRM, telephony, marketing, appointments and customer service — all in one place, with AI built in.

No credit card required