Skip to main content
Actions are the steps your automation performs after a trigger fires. You can chain multiple actions together, and each action runs in sequence. Some actions provide data to later actions — for example, Create opportunity makes the new opportunity available to subsequent steps. Actions are grouped into Household, Contact, Business, Task, Opportunity, Project, AI, Flow, and System. The available actions depend on the records supplied by your trigger and earlier steps.

Household actions

These actions operate on the household associated with the triggering record.

Add tag

Add a tag to the household.

Remove tag

Remove a tag from the household.

Add note

Add a note to the household record.

Add comment

Add a comment to the household.

Send email

Send an email to the household. Only one send email action is allowed per branch path. Type { in an email Subject to choose an available variable. Use Current date for the date when the automation runs; available record variables depend on the trigger and earlier actions.

Send SMS to client

Send a text message to people in the client household. Only one SMS action is allowed per branch path.

Create opportunity

Create a new opportunity for the household. The created opportunity becomes available to later actions.

Find opportunity

Find the most recently updated opportunity for the household. The found opportunity becomes available to later actions (such as Move to stage).

Add to sequence

Enroll the household in a sequence.

Remove from sequence

Remove the household from a sequence.

Start project

Start a project from a template. When the trigger provides a household, the project belongs to that household. A recurring automation configured to run Once per book creates a book-level project without a related household. If the selected project type’s first milestone has form fields, they appear below the action settings. Enter fixed values or insert data supplied by the trigger. When a chat-triggered run is still missing a required value, Slant provides a Complete project setup link instead of starting an incomplete project.

Find project

Find the most recently updated project for the household. The found project becomes available to later actions such as Move to milestone.

Promote to client

Promote a prospect household to a client. This action has no configuration fields — it promotes the household directly.

Update attribute

Set the household’s Tier, Next review date, or a supported custom field. Choose Attribute, then set Value. Date values support Specific date, Today, Tomorrow, In 1 week, In 1 month, In 1 year, and Clear date. Relative dates are calculated when the automation runs. Next review date updates apply to clients.

Delete open tasks

Delete the household’s open tasks and stop their recurring series. Completed tasks remain.
This action removes open tasks, including scheduled occurrences in their recurring series. Review the trigger and filters before enabling it.

Contact actions

Choose these actions when your automation runs for an other contact. Notes, tags, and sequence enrollment apply to that contact. Email and SMS use the contact’s own primary email address and phone number. Only one Send email and one Send SMS action are allowed per branch path. You can also use Create task to add a task for the contact.

Business actions

Use these actions when your trigger supplies a business:
  • Add note adds a note to the business.
  • Send email sends to the business’s primary email address.
  • Send SMS sends to the business’s primary phone number.
  • Start business project creates a project from a business Project template. Set an optional Project name and Assigned to.
You can also use Create task for the business. The available actions depend on the record context supplied by your trigger.

Task actions

Create task

Create a new task. The task is linked to the household or record associated with the trigger.
How user-reference custom field assignment resolves at run time. When the automation runs, Slant picks the assignee in this order:
  1. If you chose a specific user, the task is assigned to that user.
  2. If you chose a user-reference custom field, Slant reads that field off the household and assigns the task to whoever is set there.
  3. If the custom field is blank on the household, the task is created with no assignee.
This lets one automation assign tasks to the right team member per household — for example, always routing to each household’s servicing advisor.
When a project is available to the automation, Create task adds the task to its current milestone. Tasks linked to projects cannot repeat, so Repeats is disabled in that context.

Calculate task deadlines

With Relative date, enter an amount and unit, then choose the reference date. Available references depend on the trigger and record context. Household dates include Client since, Next review date, Next touchpoint date, and Next meeting date. With Next occurrence of, choose Day of the week, Day of the month, or Month and day. For monthly deadlines, you can select Last day of the month. The editor previews the resulting deadline under If run today. Calendar deadlines can fall on the current day. A numbered day such as the 31st skips months without that day; use Last day of the month for a deadline in each month.

Update tasks

Update matching tasks on the record supplied by the automation. Under Only update tasks if…, use Add filter to restrict tasks by Current status, Currently assigned to, or Current priority. Under Set on matching tasks, choose Status, Priority, Assign to, or Due in. Leave a setting unchanged to preserve its current value.

Update task

Update the task in the automation’s context (for example, the task from a task trigger). Every field is optional — only the fields you set are changed, and any field left blank or set to No change leaves the task unchanged.
This action requires a task in the automation’s context. A task trigger or an earlier Create task action can provide that task.

Add comment

Add a comment to the task in the automation’s context.

Opportunity actions

These actions require an opportunity in context — either from an opportunity trigger or from a previous Create opportunity or Find opportunity action.

Move to stage

Move the opportunity to a specific pipeline stage.

Add comment

Add a comment to the opportunity.

Project actions

These actions require a project in context from a project trigger, Start project, or Find project.

Move to milestone

Move the project to a milestone in its project type. Project types with Require milestones in order enabled cannot skip ahead past the next milestone.

AI actions

AI actions use artificial intelligence to process data, make decisions, and generate content. Input quality directly affects output quality — be specific in your prompts and descriptions.

Categorize

Use AI to sort a record into one of your defined categories. Returns the selected category, a confidence score (0–100), and the reasoning behind the choice.

Filter

Use AI to evaluate whether a record meets criteria you describe in plain language. Records that match continue through the automation; records that don’t are stopped.

Draft email

Use AI to generate an email draft from a Household or Meeting Magic button automation. The action returns a subject line and HTML body that you can use in subsequent actions.
Draft email is available only with a Magic button trigger under Household or Meeting. Meeting scheduled and other automatic triggers cannot create an AI email draft, even when they provide household or meeting data.With a Meeting Magic button, the meeting must be linked to a client or prospect before the action can create a draft. A linked other contact or business does not satisfy this requirement.

Research

Use AI to look up information and return a summary. The AI has access to web search and other research tools.

Parse and create contact

Extract contact information from an email or meeting and create a new record. Only one parse action is allowed per branch path. Requires an email or meeting in the automation context. When the record type is Client or Prospect, the AI also extracts a spouse or partner if one is mentioned and adds them to the same household. Words like “wife” or “husband” mark the second person as a spouse, and “partner”, “domestic partner”, or “fiancé” mark them as a partner.
This action stops its branch if no primary email is found or an existing record of the chosen type matches the primary or spouse email in that book. It does not reuse the existing record. When creation succeeds, later actions can use the new household or contact.

Flow actions

Flow actions control the execution path of your automation.

Branch

Split the automation into conditional paths. Each branch can have its own conditions, and records flow down the first branch whose conditions match. A default branch catches records that don’t match any other path. After adding a branch action, each branch path appears as a separate column on the canvas. Add actions to each branch independently.

Wait

Pause the automation for a specified duration before continuing to the next action.
The maximum wait time is 30 days.

System actions

Internal notification

Send a notification to team members via email or SMS. Use this to alert your team about important events.

Create task

Create a new task — see Task actions above. This action appears in both the Task and System categories.

Confetti

Trigger a confetti celebration on screen for selected team members.

FAQ

Yes. Some actions provide data to later steps — for example, Create opportunity makes the opportunity available, and AI actions provide their results as variables. You can reference these outputs using dynamic variables in text fields.
Some actions need a specific record type in context to work. For example, Move to stage requires an opportunity. If your trigger doesn’t provide one, add a Create opportunity or Find opportunity action earlier in the automation.
An action may be unavailable if the trigger or record context is incompatible, or if a “one per branch” action (like Send email) has already been added to the current branch path. For example, Draft email requires a Household or Meeting Magic button trigger. Hover over the action to see why it’s disabled.
There is no hard limit on the number of actions. However, longer automations are harder to debug — keep workflows focused on a single purpose when possible.