Action nodes
Action nodes either change the workflow payload or perform work in Magento or an external system. Simulation suppresses side effects, so a successful preview should be followed by a controlled live run for any action that changes data or sends a message.
Set Variable
Set Variable writes a named value into the current run payload. Use it to carry a decision, stage or calculated marker to later nodes. It does not update a Magento entity.
Update Entity and entity state
Entity-update actions write supported fields or state to the configured Magento entity. Verify the entity type, identifier source, target field and allowed value before publishing. Run the flow first against a disposable record and confirm the saved Magento entity afterward.
The built-in catalogue and required payload identifiers are listed under Supported entity updates.
Email actions use Magento's email infrastructure. The node takes a recipient address (payload placeholders such as {{ payload.customer.email }} are supported), a sender identity from Magento's store email contacts (general by default) and a Magento email template identifier. Sender and template are resolved in the store scope carried by the run payload.
The module ships a default workflow_action_email_template template. To customize the message, load that template under Marketing > Communications > Email Templates, save it as your own template and enter its template identifier on the node. A simulation records the step without sending the message. Live delivery still depends on Magento email transport and queue operation.
Webhook
Webhook actions call an allowed public host with a permitted HTTP method. The global request, response, retry and timeout limits apply. An empty allowed-host list blocks all destinations. Do not put credentials directly into a screenshot, workflow name or documentation example.
Comment
Comment actions write a rendered message to the workflow audit trail and the run's node log. They do not add a Magento sales-order status-history comment. Use a message that will still make sense when an operator reviews the workflow run later.
Wait
Wait pauses a live run for a configured duration and records when it may resume. Magento cron queues due runs in batches, so the actual continuation also depends on cron and the run-start consumer. In simulation, Wait is shown as the last executed step and no resume job is scheduled.
End
End finishes the current path. Give alternate End nodes clear names when the completion reason matters, such as Business follow-up queued and No business follow-up.