Create and configure an automation

An automation is a reusable flow that executes a series of steps in sequence. It is created once and can be connected to multiple events, buttons, or API calls.

Create a new automation

From the Automations window, click + to create a new one. You will need to fill in:
  • Name: a descriptive name that identifies the flow.
  • Description: a short text explaining what the automation does.

Configure input parameters

Input parameters define what data the automation needs to run. For example, if your automation changes the status of a task, it needs to receive the task as a parameter.
There are two options:
  • No parameters: the automation is self-contained and does not need external data.
  • With parameters: one or more parameters are defined, each with a name and type.
Available parameter types:
Category
Types
Primitive
text, number, boolean, date, time, JSON, list
Entities
site, task, form, project, client, supplier, workflow, network element, user, among others
Files
file, answer file
Parameters are configured from the right panel of the automation editor, in the Input section.

Configure steps (actions)

Steps are the operations executed in sequence. Each step has an action and input fields filled with values from:
  • Constant value: a fixed value defined when configuring the step.
  • Input parameter: data received by the automation (e.g., Input → site → name).
  • Previous step result: data generated by a prior step (e.g., Step 1 | Create task → id).
  • Trigger context: when triggered by an event, data from the originating object (e.g., Trigger → task → status).
  • Executing user: data about the user who triggered the automation.
Available actions — Steps are grouped into three categories:
Find objects (for use in subsequent steps): client, workflow, task in workflow, project, reference document (file, form, engineering, workflow, site access request), custom field response (network element, workflow, task), site access request member, integration reference.
Update objects: task, form, site, network element, client, workflow (status), reference document, engineering form, custom field response (quote, network element, site, task, workflow).
Create objects: task, form, workflow, site, network element, client, project, integration reference, task form document.
Other actions: send email, execute another automation, HTTP response, among others.

Draft and publishing

Automations have a draft system. You can edit an automation without affecting the version running in production. When you are satisfied with the changes, publish the draft and the new version replaces the previous one.
This lets you test changes safely before applying them.

Activate and deactivate

Each automation can be active or inactive. An inactive automation does not run, but keeps its configuration intact for when you need it again.