Automation

Workflows

A workflow is a series of steps that runs when something happens. Build workflows by dragging steps onto a canvas, start from a blueprint, or describe the workflow to Emma and review her draft.

Steps

Steps can call an action in another tool, ask Emma to investigate, wait for an approval, branch on a condition, loop over a list or run a small piece of code.

Triggers

A workflow can start from a signal, a case, a schedule, a webhook, an API call, a form answer or a change in a datastore. Workflows can also take input parameters when someone starts them by hand.

Approvals

Add an approval step before anything that changes a system. The approver gets a message in the console, Slack or Teams and clicks Approve or Reject. The workflow waits until they do.

Action catalog

The catalog holds ready-made actions for identity providers, chat, cloud, endpoint, threat intelligence and ticketing tools, such as suspending a user, revoking sessions or opening a ticket. Each action uses a connection you set up once.

In the consoleAutomation › Catalog.

Datastores

Datastores are small tables that workflows can read and update, such as an allow list, an on-call rota or the answers to a form. A change in a datastore can also start a workflow.

Forms

Forms collect answers from people inside or outside the company. Build a form in the editor, start from a blueprint, or let Emma draft it. Every answer is saved, and a form answer can start a workflow.

Forms can be shared with people outside the company through an external link. They confirm their email with a one-time code before they answer.

Emma automations

Give Emma a recurring job in plain words: what to do, which tools she may use and when to run. A common example is a short security update by email every weekday morning. See Emma automations.