How a lead status becomes a task Updated 2026-10-24
An automation is a published trigger and an action. When a lead moves to Contacted, the action can create a CRM task. The history then shows Success. A test run does not create the task.
Build the flow Choose the trigger lead status changed, and set the destination status to Contacted. Add an action that creates a CRM task. Do not insert a condition you cannot fill: an empty condition blocks the branch. Publish the workflow. Changing a lead to Contacted is the event that runs it.
The task title in the product can be the default sentence plus the lead's name. The task is saved on that lead, where the team can open it.
Open automations on the business plan. Set the trigger to a status change into Contacted. Add the action Create task. Skip an empty condition. Publish, then change a lead to Contacted. Open the run history and look for Success. The trigger is a lead moving to Contacted. The action creates a CRM task. Publish before you expect a run. What a test run will not prove The Test button is a dry run. It does not write history and it does not create the task. If the history says there are no runs, the workflow was not published, the lead status did not actually change, or the lead never actually moved to Contacted. Publish the workflow, change the status, and then look for Success in the history.
An automation can be the trigger for a WhatsApp template, but only on a paid number with a template Meta has approved. That send still needs the paid number and the approved template. The agents page is a person, not a bot.
The Test button is treated as a successful run. Publish, change the lead status, and read Success in the history.
A condition node is left empty. Use the trigger's destination status, and connect the action directly.
Publish, then change the status The Test button checks the draft. It does not write a run and it does not create the task. Publish the workflow, then move a lead to Contacted. The history should show Success, and the task should sit on that lead. If the history stays empty, the workflow was not published or the status did not actually change.
Leave out a condition you cannot fill. An empty condition blocks the branch, so the task never runs. The task title can be the default sentence plus the lead's name. WhatsApp is a different action: it needs the business plan, a paid number at $29 a month, and a template Meta has approved. The agents page is a person, not a bot.
FAQ Which plan includes this? The business plan, at $99 a month or $990 a year. CRM only does not run automations.
Does the workflow send WhatsApp? Only if you add that action on a paid number with an approved template. A status change can create a task. Sending WhatsApp is a separate action.
Why are there several Success rows? Older published workflows can match the same status change until you pause them. The history lists every matching run.
Is the agents page part of the automation? No. Agents are people. The automation creates a task a person can see.
