Run from buttons (Actions)

An action connects an automation to a visible button in the interface. When the user clicks the button, the automation runs.

This replaces and improves what was previously known as "creation assistants" or "instant automations".

How does it work?

1. From the Actions window, click + to create a new connection.
2. Select the automation you want to execute (only standalone automations are shown).
3. Define the label (visible button text).
4. Configure the parameter mapping: where each value the automation needs comes from in that context.

Parameter mapping

Just like triggers, each automation parameter must receive a value. In the context of an action, values can come from:

• Current object: the task or form where the button is displayed.
• Object fields: name, status, site, project, etc.
• Constant value: a fixed value.

If any parameter is left unassigned, the system shows a warning.

Reusability

A single automation can have multiple actions across different templates. For example, an automation that creates an associated workflow can have buttons in:

• The installation task template
• The inspection form template
• Any other template where it makes sense to offer that action

Each action has its own label and parameter mapping, adapted to the context where the button is displayed.

Usage examples

Create related elements: A button in a task that creates a network element, two sites, and links them together — all in a single click.

Start a workflow: A button in a form that creates a workflow by selecting project and template from configured options.

Generate documentation: A button that creates a form pre-loaded with data from the current site.

Difference from triggers