Build a workflow you can follow from start to finish.
Begin with one visible outcome: a task created in your CRM. Follow that work through execution history before connecting a workflow to everyday business changes.
Updated October 2, 2026
Choose a small outcome you can check
Open Automate - Workflows and create a named draft, such as First follow-up task. The new canvas starts with a Manual trigger. Choose Add step, then Create record, and select Tasks in the Object field. In Field values, enter a JSON object such as {"name":"Example follow-up task","status":"To do"}.
Select Manual trigger from Select a workflow step and check that Next step points to Create record. You can also connect the canvas handles. Use fictional test information and an internal action for this first workflow. Record creation follows the same field and relation validation as creating a record by hand.
Save the draft and publish a version
Choose Save draft. Before Publish, check the task object, action data and connection between nodes. An owner or administrator publishes the workflow; publishing validates the settings and preserves a version for executions. A workflow needs exactly one trigger and all nodes connected to it.
A saved draft and a published workflow are different states. Later draft edits do not change the version used by a run. Save and publish again when the reviewed behavior needs to change. Managed outreach workflows remain controlled through Outreach, where audience review and launch checks apply.
Run it and inspect both sides
Choose Test run, leave Trigger input as {} for this example, and confirm Run published version. This performs real actions in your workspace. Open Execution history and inspect the state and step results. If it succeeds, open CRM - Tasks and confirm that Example follow-up task is present.
If the run fails, read the step error and check the action’s fields and context. Missing expression paths become empty strings, so inspect inputs rather than assuming a value exists. Correct the draft and publish its replacement. For external requests with an uncertain outcome, check the provider before another attempt.
Connect the next business event
After the manual path works, consider a business-event trigger such as a newly won deal. Event workflows can use record context, including {{record.data.name}} and {{record.id}}. Conditions select a path and waits preserve a delayed next step without holding a worker open.
A finance action creates a draft for review; it does not issue an invoice or move money. Pause controls future triggering, while cancelling an unfinished execution controls that run. An accepted external action cannot be undone by cancelling. Keep each workflow small enough that the next teammate can understand its trigger and outcome.
