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.Send SMS to client
Send a text message to people in the 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.
Promote to client
Promote a prospect household to a client. This action has no configuration fields — it promotes the household directly.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:
- If you chose a specific user, the task is assigned to that user.
- If you chose a user-reference custom field, Slant reads that field off the household and assigns the task to whoever is set there.
- If the custom field is blank on the household, the task is created with no assignee.
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. It is available when the automation starts from a task trigger.
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.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 based on a prompt. Returns a subject line and HTML body that can be used in subsequent actions.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.
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
Can I use the result of one action in a later action?
Can I use the result of one action in a later action?
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.
What does 'requires subject' mean?
What does 'requires subject' mean?
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.
Why is an action grayed out in the picker?
Why is an action grayed out in the picker?
An action may be unavailable if its required record type is not in the automation’s context, or if a “one per branch” action (like Send email) has already been added to the current branch path. Hover over the action to see why it’s disabled.
Is there a limit on how many actions an automation can have?
Is there a limit on how many actions an automation can have?
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.