This replaces and improves what was previously known as "creation assistants" or "instant automations".
From the window, click to create a new connection.
Select the you want to execute (only standalone automations are shown).
Define the (visible button text).
Configure the : where each value the automation needs comes from in that context.
Just like triggers, each automation parameter must receive a value. In the context of an action, values can come from:
- : the task or form where the button is displayed.
- : name, status, site, project, etc.
- : a fixed value.
If any parameter is left unassigned, the system shows a warning.
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.
A button in a task that creates a network element, two sites, and links them together — all in a single click.
A button in a form that creates a workflow by selecting project and template from configured options.
A button that creates a form pre-loaded with data from the current site.
Automatically on an event
Manually when the user clicks
No (runs in the background)
Yes (appears as a button)
Yes, the button text is defined
Object that triggered the event
Object where the button is displayed