Before adding a trigger, state its event and intended result in one sentence. For example: after signing the preparation step, show a reminder to continue to measurement. Start with one action in a practice draft and test it before adding more actions.
A trigger performs an action when a step event occurs. It can set a variable, open a form, write to a table, or call a configured integration. Routing separately determines the next step.
Create a trigger
Select the step and open Triggers.
Add a trigger and give it a descriptive name.
Select the event.
Select the action and complete its settings.
Add a condition only if the action should run for a subset of cases.
Wait for Saved, inspect validation, and test.
Start in the step’s Triggers tab and choose Add Trigger in an editable draft. This read-only example has no triggers yet; the disabled button reflects read-only mode.
Choose the event
Step Is Signed: when the step is signed.
Step is Opened: when the step is opened. Do not assume this means once per session; revisiting a step can matter.
Step is Closed: when the step is closed.
Step Is Unsigned: when a signature is cancelled.
Choose an event based on the required business behavior, not just where the operator happens to be looking.
Common actions
Set Variable: assign a value to an existing variable.
Set Variable (Formula): calculate a value with a formula.
Open Form: choose a form to open.
Go to Workflow: choose the destination workflow.
Create Work Order: configure work-order creation.
NPT Operations: configure a table operation and its values/conditions.
Webhook: select a previously configured Webhook record.
Send Email, SMS, or WhatsApp: available according to the configured communication services.
The Webhook action does not contain an arbitrary HTTP method, header, and body editor. Device Action is not a general selectable action in this editor.
Event restrictions
Error Message can be used on signing or unsigning events. Open Form cannot be used on Step is Closed. The validator also checks required settings such as a chosen variable, form, table, or webhook.
Use the drag handle to reorder trigger cards where needed. Test actions with dependencies together, especially when one writes a variable used by another.
Example: record an inspection outcome
Create a Text variable named inspectionOutcome. On an Accept step, add a Step Is Signed trigger with action Set Variable and value PASS. On a Hold step, set the same variable to HOLD.
Display the value in the next instruction and test both paths.
Preview and release
Preview is useful for workflow logic, but some external actions are simulated or skipped. Verify table writes, messages, work-order creation, and integrations through controlled real test sessions.
Saving the draft does not release changed triggers to operators. Test and publish the intended workflow version separately.