Run Any Integration Action From a Workflow
Use the Business Action step in the Workflow builder to run any Velaro skill as a workflow step, such as looking up an order, creating a case or adding a record in a connected system. A step runs the same skill your bot uses, with the same access checks, so a workflow and a chat do the same thing in the same way.
Add a Skill Step
- Open the workflow and add a Business Action step from the palette.
- Pick the action from the list. Skills are grouped by integration and are searchable. Only the skills your account has turned on are offered.
- Fill in the form. It is built from the skill itself, so each field shows its type, allowed values and whether it is required.
- Insert earlier workflow values with double angle brackets, for example the order number saved by a previous step.
- Choose a Save result as name so later steps can use the output.
Steps that look something up can run in a test conversation. Steps that change data are skipped in a test conversation and show a message that they would have run, so testing never changes your records.
Steps That Change Data Need Admin Approval
A step that creates or updates a record in a connected system has to be approved by a site admin before it runs unattended. After you save the step, an admin approves it from the workflow. The approval is tied to the admin who gave it and to the exact step: the skill, the field values and the output name. If someone edits the step, the approval is replaced and an admin approves the new version. A copied, imported or template workflow starts without approvals, and an admin approves each change-making step in the new workflow.
If the approving admin leaves the team or loses admin access, the step waits for a new approval. Each run also checks that your account still includes that integration's write access.
Skills that move money, such as refunds and credits, use the Governed Action step, which has its own approval exits. See Governed Action Workflows.
Duplicate Protection
A workflow that is retried or restarted does not repeat a change it already made. If a step with the same values has already run, the repeat is not sent again. The step returns the earlier result marked as replayed, and a Duplicate exit lets you decide what happens next. If a loop needs to make several changes, include a value that differs on each pass, such as the item number. If a change could not be confirmed, the step takes the Error exit so you can check the record rather than create it twice.
Connect Every Exit
New skill steps have these exits: Success, Denied, Needs approval and Error. Connect each one so every outcome has a clear next step. If an exit that is needed is not connected, the workflow stops with a message that names the step and the reason. Existing Business Action steps keep working as they do today.
Existing NetSuite Connector Steps
Workflows that already use the NetSuite Connector step keep running as before, with the same field mapping. You do not need to rebuild them.
Tips
Test the workflow in a test conversation first, then ask an admin to approve change-making steps before turning the workflow on. Team members can add skill steps with the Velaro CLI and Moshky as well as the builder. Approval always comes from a person.
Was this article helpful?