Workflow Actions
Six things a CRM rule does once it fires, and not one of them is a placeholder. Mail goes out through your own server or it does not go out at all. An outbound call refuses a private address and gives up after five seconds.
Six actions, in the order you stored them
configuration only- 7A chat-channel kind the column permits
- Writes a real row
- Carries the title and the body you stored
- No placeholder anywhere in it
Product figures from the platform’s own defaults - not customer averages
How it works.
Six, and not one of them is a placeholder
Send a message, assign an owner, raise a task, set a field, move a deal along its pipeline, or call out to a system you name. Each one really writes to the record or really opens a connection. Not one of them is a placeholder.
A broken third does not undo the two before it
Actions hang off the rule with a sort position and run one after another. A failure is collected into a list and the next one still runs, so a broken third does not undo the two before it.
The narrow ones are narrow deliberately
Moving along a pipeline refuses anything that is not a deal. Assigning an owner covers leads and deals. Setting a field covers leads, deals and activities, and offers set, increase, decrease and append rather than assignment alone.
Two places it refuses to do the wrong thing
The mailer routes only through the workspace's own outgoing server, with no platform fallback to reach for, and where none is configured it fails with the sentence telling you where to add one. The outbound call resolves the address first, refuses anything on a private range, pins the connection to the address it checked, follows no redirects, and gives up after five seconds.
One moment in every run.
Every run passes through the same seven. Workflow Actions is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- Kinds
- Send message, assign owner, raise task, set field, move along the pipeline, call an external system
- Order
- Sequential by stored position. An error is collected and the remaining actions still run
- Record limits
- Pipeline moves are deals only. Assignment covers leads and deals. Field setting covers leads, deals and activities
- Outbound call
- Address checked against private ranges, no redirects followed, a five second ceiling, and a fixed identifying header
- Mailer
- The workspace's own outgoing server only, with no platform address to fall back on. Values merged into the HTML body are escaped; values merged into the subject line are not
- Guarded per action
- Each action carries its own finer test against the delivered payload, so one rule can act on part of what it matched and leave the rest
- When they run
- Inline on the rule's own run, in the order stored, with the run row closing on a verdict and the time it took
- Not the same as
- These are CRM rule actions. Steps inside a cadence belong to the Sequence Builder
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and outside triggers that act without being asked.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
The next step answers something the person actually did, not something your floor guessed. Opened, clicked, replied, or how the last call was dispositioned.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See workflow actions on your own floor.
Thirty minutes, your numbers and your data. We will set workflow actions up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included