> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slant.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Actions
> Reference for all automation action types — the steps an automation performs.
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.
## Household actions
These actions operate on the household associated with the triggering record.
### Add tag
Add a tag to the household.
| Field | Description |
| ------- | -------------------------------- |
| **Tag** | Required. Select the tag to add. |
### Remove tag
Remove a tag from the household.
| Field | Description |
| ------- | ----------------------------------- |
| **Tag** | Required. Select the tag to remove. |
### Add note
Add a note to the household record.
| Field | Description |
| ----------- | ------------------------------------------------------------------------------- |
| **Content** | Required. The note content. Supports markdown formatting and dynamic variables. |
### Add comment
Add a comment to the household.
| Field | Description |
| ----------- | --------------------------- |
| **Content** | Required. The comment text. |
### Send email
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}}`. If the selected template has attachments, they appear beneath the template and are automatically included with the sent email. |
### Send SMS to client
Send a text message to people in the household. Only one SMS action is allowed per branch path.
| Field | Description |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **SMS integration** | Required. Select which connected phone integration to send from. |
| **Recipients** | Required. Toggle which people receive the message: head of household and/or spouse/partner. Default: head of household only. |
| **Message** | Required. The message text. Supports dynamic variables like `{{person.preferred_name}}`. |
### Create opportunity
Create a new [opportunity](/activity/opportunities/overview) for the household. The created opportunity becomes available to later actions.
| Field | Description |
| --------------- | ------------------------------------------------------------------------------------------------ |
| **Name** | Required. The opportunity name. |
| **Pipeline** | Optional. Select a pipeline. If left empty, the default pipeline for the household type is used. |
| **Value** | Optional. The opportunity value in dollars. |
| **Probability** | Optional. Win probability from 0–100. |
### Find opportunity
Find the most recently updated opportunity for the household. The found opportunity becomes available to later actions (such as **Move to stage**).
| Field | Description |
| ------------ | --------------------------------------------------------------------------------------------- |
| **Pipeline** | Optional. Limit the search to a specific pipeline. If left empty, all pipelines are searched. |
### Add to sequence
Enroll the household in a [sequence](/platform/sequences/overview).
| Field | Description |
| ------------ | --------------------------------------------------------- |
| **Sequence** | Required. Select the sequence to enroll the household in. |
### Remove from sequence
Remove the household from a sequence.
| Field | Description |
| ------------ | ------------------------------------------------------------------- |
| **Sequence** | Required. Select a specific sequence, or remove from all sequences. |
### Start project
Start a [project](/activity/projects/overview) from a template for the household.
| Field | Description |
| ---------------- | -------------------------------------------- |
| **Project type** | Required. Select the project type to create. |
### 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](/activity/tasks/overview). 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](/account-settings/customization/custom-fields) 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:
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.
### 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.
| Field | Description |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Title** | Optional. The new task name. Leave blank to keep the current title. |
| **Description** | Optional. The new description. Supports markdown formatting and dynamic variables. |
| **Due in** | Optional. When the task is due: same day, 1–3 days, 5 days, 1 week, 2 weeks, or 1 month. Defaults to **No change**. |
| **Priority** | Optional. Set the priority: low, medium, high, or urgent. Defaults to **No change**. |
| **Status** | Optional. Set the status: to do, done, or rejected. Defaults to **No change**. |
| **Assigned to** | Optional. Reassign the task to a specific user, a team, or a user-reference [custom field](/account-settings/customization/custom-fields) on the household. The picker groups options under **Users**, **Teams**, and **User reference fields**. |
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.
| Field | Description |
| ----------- | ------------------------------------------------------- |
| **Comment** | Required. The comment text. Supports dynamic variables. |
## 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.
| Field | Description |
| ------------ | ---------------------------------- |
| **Pipeline** | Required. Select the pipeline. |
| **Stage** | Required. Select the target stage. |
### Add comment
Add a comment to the opportunity.
| Field | Description |
| ----------- | --------------------------- |
| **Content** | Required. The comment text. |
## 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.
| 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. |
### 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.
| 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. |
### 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.
| Field | Description |
| --------------- | ------------------------------------------------------------------------------------------------------------ |
| **Record type** | Required. The type of record to reference: household, task, opportunity, meeting, or person. |
| **Prompt** | Required. Describe the email you want. Data from the associated record is automatically included as context. |
### Research
Use AI to look up information and return a summary. The AI has access to web search and other research tools.
| Field | Description |
| ----------- | ------------------------------------------------------------------------------------------------------------- |
| **Subject** | Required. The type of record to research: household, task, opportunity, or meeting. |
| **Query** | Required. Describe what you want to learn. Information about the record is automatically included as context. |
### 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.
| 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.
## 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.
| 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.
### Wait
Pause the automation for a specified duration before continuing to the next action.
| Field | Description |
| ----------------- | ------------------------------------------------------------------ |
| **Wait duration** | Required. Enter a number. |
| **Unit** | Required. Choose **Seconds**, **Minutes**, **Hours**, or **Days**. |
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.
| Field | Description |
| ----------------- | ------------------------------------------------------ |
| **Message type** | Required. Choose **Email** or **SMS**. Default: email. |
| **To / CC / BCC** | For email: enter email addresses for each field. |
| **Email content** | For email: set the subject and body. |
| **SMS to** | For SMS: enter phone numbers. |
| **SMS body** | For SMS: enter the message text. |
### Create task
Create a new task — see [Task actions](#task-actions) above. This action appears in both the Task and System categories.
### Confetti
Trigger a confetti celebration on screen for selected team members.
| Field | Description |
| ----------- | -------------------------------------------------------------------------------- |
| **Users** | Required. Select which team members see the celebration. |
| **Style** | Required. Choose **Fireworks**, **Raining**, or **Cannons**. Default: fireworks. |
| **Message** | Optional. A celebration message to display. |
## 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 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.
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.