Set when the stage automation runs
In the Action & Delay automation, the Wait field decides how long Clickmax waits before running the action. The countdown always starts the moment the opportunity enters the stage — not the moment you created the automation.
Before you start
- Workspace role: owner, admin or editor. Without one of these you cannot create or edit stage automations. See what each role covers in the permissions table.
- You need a pipeline with at least one stage. If you do not have one yet, start with Build your first pipeline.
Steps
- Open the pipeline and, on the stage you want to automate, click Create automation.
- On the Type step, choose Action & Delay and click Continue.
- On the Item step, choose the action that will run — for example Send WhatsApp, Apply tag or Create task — and click Continue.
- On the Configure step, use the Wait field to choose the time. Hover over each shortcut to read what it means.
- Fill in the fields for the chosen action and click Save.
What each wait time means
H is hour and D is day. In every case the countdown starts when the opportunity enters the stage — that is what the Time counts from the moment the card enters this stage text right below the field means.
D+1 means 24 hours later, not "the next morning". An opportunity that enters the stage at 10 PM with D+1 gets the action at 10 PM the following day.
Use a time that is not on the list
Click Custom to open the free time choice. Two fields appear: a number and the unit — minutes, hours or days.
- The value is always a whole number. To wait half an hour, choose
30minutes, not0.5hours. - Changing the unit rewrites the scale, it does not convert the duration: switching
2hours to minutes becomes2minutes, not 120. - When you reopen the automation, the saved time comes back in the largest unit that fits without a fraction — 48 hours reopen as
2days.
If the opportunity leaves the stage first
The action is cancelled. While the wait time runs, the automation stays pending; if someone moves the opportunity to another stage before the deadline, nothing runs.
That run is recorded as Canceled, not as completed. On the automation card, under Automations on the pipeline board, it counts in Executions but not as completed in the Rate.
This prevents, for example, a D+3 reminder from reaching an opportunity that was already closed the next day.
Related
If it did not work
- Create automation does not appear on the stage → your role does not allow configuring the pipeline. Check No permission and the permissions table.
- The action did not run when expected → check that the opportunity actually entered the stage after the automation was saved. Opportunities that were already in the stage do not start the countdown.
- You see a
Save errorwarning → the automation was not created. Check that every field for the chosen action is filled in and try again; if it persists, see the error codes.