Skip to content
Sekential

Automations

Recurring tasks get done without chasing.

Your team writes the rule once, in its Playbook's flow. When a journey starts or a portal page changes, the next steps run for each customer.

Join for free

7-day free trial.

ExampleApprovedSuccessFailure

The journey starts, the next steps follow.

A flow starts at the beginning of a journey or a Playbook. In a Playbook, it also starts when a portal page changes state. And when your tool calls Sekential, the flow resumes.

ExampleJourney startPlaybook startPortal pageCall from your tool

The flow handles repeated work.

The flow sends a pre-written email to the people in a role, or prepares it for your team to review. It also updates a variable's value, and the state of a step or a portal page.

ExampleOnboardingEmailTemplateYour access is readySend automaticallyToCustomer administratorCCProject manager

Your other tools follow the journey.

Your tool calls a Playbook's secret address, and the flow resumes. The other way round, the flow calls your tool's API, with a key kept in your workspace, and what comes next depends on the response.

ExampleYour tool calls SekentialRecent invocationsSekential calls your toolCall to your toolCreate the accountsSuccessFailure

What automations do

What starts the next steps

Journey or Playbook start

The flow starts with the journey, or with each Playbook in that journey.

Portal page

A Playbook's flow starts when a portal page moves to a new state.

Call from your tool

Your tool calls the secret address of the Playbook or the journey, and the flow resumes. The latest calls stay visible.

Milestone reached

Soon

The flow starts when a step marked as a milestone is completed.

What the flow does

Email

A pre-written email goes to the people in a role, with CC. Or the flow prepares it, and your team sends it.

Call to your tool

The flow calls a tool's API, with a key kept in your workspace. One output for success, one for failure.

Variables

The flow sets a variable's value, which the portal or an email then use.

States

The flow changes the state of a step or a portal page, which can also be hidden. In the journey's flow, it changes the state of the journey.

Retry a block

If a call fails, someone who can edit the flow retries it in one click.

Zapier and Make

Soon

Your journeys join the automations you already have.

See also

Adaptive Playbooks

The flow where your automations live, with its conditions and its decisions.

Custom Objects

The variables the flow reads and updates, on each customer's record.

Integrations

The tools your automations listen to or notify.

Frequently asked questions

Where automations are set up
In the flow of each Playbook, and in the journey's flow. The rule lives next to the steps it moves forward.
An email sent without review
It goes out from a template your team wrote, to the people in the chosen role. To review it before it is sent, choose the email drafted by your team.
A call that fails
The flow takes the path planned for failure, for example a task for your team. Someone who can edit the flow retries the call.
Your tools' keys
An admin of your workspace adds them. They are encrypted, and the flow uses them without showing them. A Playbook's secret address is shown once, when you create it.
What your customer sees
The result: an email received, a portal page that opens. Your rules stay with you.
Automations and AI Teammates
An automation follows the rule you wrote. An AI Teammate receives a bounded instruction in the same flow; the AI Teammates page tells you more.

Let the journey move forward.

Your team keeps its time for its customers.

Join for free

7-day free trial.

Playbook