Use this file to discover all available pages before exploring further.
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.When you add an action, choose from six categories: Household, Task, Opportunity, AI, Flow, and System.
Send an email to the household. Only one send email action is allowed per branch path.
Field
Description
Email integration
Required. Select which connected email account to send from.
Recipients
Required. Choose who receives the email. For each person (head of household, spouse/partner), select To, CC, BCC, or None. Default: head of household as To.
Email content
Required. Optionally select an email template, then set the subject line and body. The body editor supports dynamic variables like {{person.preferred_name}}.
Create a new task. The task is linked to the household or record associated with the trigger.
Field
Description
Title
Required. The task name.
Description
Optional. A longer description. Supports markdown formatting.
Due in
Required. When the task is due: same day, 1–3 days, 5 days, 1 week, 2 weeks, or 1 month. Default: 1 day.
Priority
Optional. Set the priority: low, medium, high, or urgent.
Assigned to
Optional. Assign the task to a specific user, a team, or a user-reference custom field on the household (for example, a Servicing advisor field). The picker groups options under Users, Teams, and User reference fields.
Email draft
Optional. Pre-stage an email draft on the task. Choose AI prompt to write a free-text prompt that guides an AI-generated email, or Email template to pick from existing templates. Only one source can be set per task.
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.
This lets one automation assign tasks to the right team member per household — for example, always routing to each household’s servicing advisor.
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.
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.
Field
Description
Record type
Required. The type of record to categorize: household, contact, task, opportunity, meeting, or person.
Categorization mode
Required. Choose Custom categories (define your own list) or Object field options (use the existing options from a field on the record).
Field
Required if using object field options. Select which field’s options to use as categories.
Categories
Required if using custom categories. Define category names and optional descriptions.
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.
Field
Description
Record type
Required. The type of record to evaluate: household, task, opportunity, meeting, or person.
Criteria
Required. Describe the criteria for records to continue through the automation.
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.
Field
Description
Type of record to create
Required. Choose Client, Prospect, or Contact. Default: prospect.
Additional instructions
Optional. Additional instructions for the AI when parsing the contact information.
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.
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.
Field
Description
Branches
Required. Define branches with names and condition groups. Each branch can have its own sequence of actions.
After adding a branch action, each branch path appears as a separate column on the canvas. Add actions to each branch independently.
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?
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?
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?
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.
