How is a journey run counted?

One run is one trigger firing and the journey executing to its end. Plans include from 100 to 50,000 runs per month.

Can I call my own API?

Yes, with the HTTP request step on Growth and higher plans.

When is automation available?

Journeys are planned for Phase 7; messaging and voice steps follow their channels.

Workflow automation

Automations that connect conversations to outcomes

Drag together triggers, conditions, AI steps and actions to follow up leads, recover carts and keep systems in sync — with versions, test mode, retries and full execution history.

Start free trial Book a demo

Journey — New lead follow-up (draft)

Trigger

New WhatsApp lead

AI agent

Qualify budget & timeline

Condition

Score ≥ 70

Delay

Wait 1 day

CRM

Create deal

Send brochure

Retries: 3 with backoffQuota: 2,500 runs / monthTest mode

Illustrative preview with sample data. Not connected to live systems.

Reliable by design

Journeys run on a durable execution engine: each step is recorded, failed steps retry with backoff, and runs that keep failing move to a dead-letter queue for review instead of disappearing.

You can pause, resume and test journeys, and every run counts against a clear monthly allowance so automation never surprises you on the bill.

What it does

Each capability shows when it is scheduled to ship and whether it depends on a provider's approval.

Triggers
Planned for Phase 7
Incoming messages, new leads, form submissions, schedules and webhooks.
Logic
Planned for Phase 7
Conditions, switches, delays and end steps.
AI and knowledge steps
Planned for Phase 7
Call an agent or look up knowledge mid-journey.
Actions
Planned for Phase 8
HTTP requests, CRM updates, notifications and email.
Messaging and voice actions
Phase 10, needs Meta (WhatsApp) approval
WhatsApp messages, SMS through approved providers and voice campaigns.
Human approval and error handling
Planned for Phase 7
Pause for approval; catch and retry errors.
Versions, test mode and history
Planned for Phase 7
Draft and publish versions, test safely and inspect every run.
Reliability and limits
Planned for Phase 7
Idempotency, retries, dead-letter queue, concurrency and quotas.

Where it helps

Lead follow-up

New lead → AI qualification → high score books a call, low score gets a nurture sequence.

Abandoned cart

Cart abandoned → wait an hour → WhatsApp reminder with the cart link → stop if they buy.

Refund request

Refund asked → AI checks eligibility → manager approves → payment refunded and customer told.

Build a journey

Step 1
Choose a trigger
Start from an event in your channels or systems.
Step 2
Add steps
Drag in conditions, AI steps and actions.
Step 3
Test
Run in test mode with sample data.
Step 4
Publish and watch
Go live and follow every run in the history.

Why teams choose it

No glue code: Connect tools without writing scripts.
Safe automation: Approvals and retries keep humans in control.
Predictable cost: Run allowances and quotas per plan.

Works with

n8n webhooks
Coming soon
Make webhooks
Coming soon
Zapier webhooks
Coming soon
Custom REST API
Coming soon
HubSpot
Coming soon
Google Sheets
Coming soon
Slack
Coming soon

See all integrations

Security considerations

Journeys cannot run arbitrary server-side code; expressions are sandboxed.
HTTP steps block internal network addresses.
Credentials used by steps are stored encrypted, never in the journey itself.

Questions, answered

Still unsure? Ask the team.

Plan your first agents with us

Book a walkthrough to see what is ready today, what each phase adds and how a pilot would work for your business.

Start free trial Book a demo

Reliable by design

Journeys run on a durable execution engine: each step is recorded, failed steps retry with backoff, and runs that keep failing move to a dead-letter queue for review instead of disappearing.

You can pause, resume and test journeys, and every run counts against a clear monthly allowance so automation never surprises you on the bill.

What it does

Each capability shows when it is scheduled to ship and whether it depends on a provider's approval.

Triggers

Planned for Phase 7

Incoming messages, new leads, form submissions, schedules and webhooks.

Logic

Planned for Phase 7

Conditions, switches, delays and end steps.

AI and knowledge steps

Planned for Phase 7

Call an agent or look up knowledge mid-journey.

Actions

Planned for Phase 8

HTTP requests, CRM updates, notifications and email.

Messaging and voice actions

Phase 10, needs Meta (WhatsApp) approval

WhatsApp messages, SMS through approved providers and voice campaigns.

Human approval and error handling

Planned for Phase 7

Pause for approval; catch and retry errors.

Versions, test mode and history

Planned for Phase 7

Draft and publish versions, test safely and inspect every run.

Reliability and limits

Planned for Phase 7

Idempotency, retries, dead-letter queue, concurrency and quotas.

Where it helps

Lead follow-up

New lead → AI qualification → high score books a call, low score gets a nurture sequence.

Abandoned cart

Cart abandoned → wait an hour → WhatsApp reminder with the cart link → stop if they buy.

Refund request

Refund asked → AI checks eligibility → manager approves → payment refunded and customer told.

Automations that connect conversations to outcomes

Reliable by design

What it does

Triggers

Logic

AI and knowledge steps

Actions

Messaging and voice actions

Human approval and error handling

Versions, test mode and history

Reliability and limits

Where it helps

Lead follow-up

Abandoned cart

Refund request

Build a journey

Choose a trigger

Add steps

Test

Publish and watch

Why teams choose it

Works with

Security considerations

Questions, answered

How is a journey run counted?

Can I call my own API?

When is automation available?

Related

Plan your first agents with us

Automations that connect conversations to outcomes

Reliable by design

What it does

Triggers

Logic

AI and knowledge steps

Actions

Messaging and voice actions

Human approval and error handling

Versions, test mode and history

Reliability and limits

Where it helps

Lead follow-up

Abandoned cart

Refund request

Build a journey

Choose a trigger

Add steps

Test

Publish and watch

Why teams choose it

Works with

Security considerations

Questions, answered

How is a journey run counted?

Can I call my own API?

When is automation available?

Related

Plan your first agents with us