Action Components

Action components perform operations like sending notifications, creating records, or updating data. They’re typically the “end points” of your automation flows.

Important: Action components always execute their side effects when reached, even if their outputs aren’t connected to downstream nodes. This ensures emails are sent, tasks are created, etc.

Communication Actions

Send Email V2

Sends an email to specified recipients.

Configuration

Field	Description
Email Provider	SendGrid sends from your verified domain; Gmail sends from a connected mailbox. The fields below change with the provider you pick.
Sender Mailbox	Gmail only. The connected Gmail account to send from, or Use Role to send from the person holding a role on the account.
Sender Role (if role-based)	Gmail only, when the sender is Use Role. The account role to send as (for example, CSM or AE).
To Recipients	Comma-separated email addresses; supports @ notation
To (Stakeholders)	SendGrid only. Send to the account’s csm, csm’s manager, user, or user’s manager
Cc Recipients	Comma-separated email addresses to copy (optional)
CC (Stakeholders)	SendGrid only. Stakeholders to copy, from the same list as To (Stakeholders)
Subject	Email subject line
Body	Email body content (supports markdown and @ notation)
Include Citations	Send the citations of an upstream Stella or Pre-Built Agent node as numbered links, to internal recipients only (on by default). See Citations.
HIL Enabled	Turn on to require approval before the email is sent (off by default)
Configure Human-in-the-Loop (HIL)	The person or role who approves the email, when HIL Enabled is on
Attachments	Files to attach and send with this email. Upload files directly on the node.

Approval before sending

When HIL Enabled is on, the flow pauses and the approver you chose reviews the drafted email in Statisfy. They can edit the To and CC recipients, subject, and body, then approve to send it or reject it. This works with both Gmail and SendGrid.

Citations

When the body uses the output of a Stella or Pre-Built Agent node with Enable Citations on, each cited source appears as a numbered link ([1], [2]) and a References list at the end names each source. Citations link into Statisfy, so they are sent only when every recipient is internal:

Email: every To and CC address is at your company’s domain (or one of its alias domains) or belongs to a member of your workspace.
Slack channel: the channel is one Statisfy knows and isn’t shared with another organization (Slack Connect).
Slack DM: the person is internal by the same rule as email.

Otherwise the message is sent without its citations. Turn Include Citations off to always send without them. When the email needs approval, the approver sees it as it will be sent, and the recipients are checked again when it’s approved. Gmail Send V2 and Send Microsoft Teams Message always send without citations.

Attachments

Attach files to the outgoing email — for example, a PDF summary generated earlier in the flow, or a fixed one-pager you want every send to include.

Up to 10 files per email and 20 MB total across all attachments on a single email.
Supported types: PDF, Word, Excel, PowerPoint, images (JPEG, PNG, WebP, GIF), plain text, CSV, JSON, and log files.
When Human-in-the-Loop is in the flow, the approver sees each drafted email’s attachments and can remove any before the email is sent. See Approver review of attachments below.

Example Configuration

To: @account_data.owner_email
Subject: Action Required: @account_data.name health score dropped
Body:
  Hi @account_data.owner_name,

  The health score for @account_data.name has dropped to @account_data.health_score.

  Please review and take appropriate action.

Output Data

Returns confirmation of email sent with message ID.

Email Template V2

Sends an email using a pre-defined template.

Configuration

Field	Description
Template	Select from saved email templates
To	Recipient email address(es)
Template Variables	Values for the `account.`, `contact.`, and `user.*` variables the template uses. Each value is a literal or an `@` reference to an upstream node. See Template variables.
Attachments	Files to send in addition to the template’s own attachments

When to Use

Consistent branded communications
Complex email layouts
Reusable email content across automations

Templates are built in Email Templates and personalized with merge tags such as {{ contact.name }}.

Template variables

Use Template Variables to send templated emails from flows that have no account or contact context, such as flows started by a warehouse trigger. You can also use it to override a value the template would otherwise read from the CRM or the sender. When you pick a template, the node lists every account.*, contact.*, and user.* variable the template uses, plus contact.email. The editor shows how many variables are set as Template Variables (filled/total). For each variable, enter a literal value or type @ to reference an upstream node’s output:

{
  "contact.email": "@Warehouse Trigger.row.email",
  "contact.first_name": "@Warehouse Trigger.row.first_name",
  "account.name": "Acme Corp",
  "user.name": ""
}

Filled values override the value from the CRM record or the sender.
Empty values fall back to the CRM or sender value.
contact.email picks the recipient. If no contact has that address, Statisfy creates one and sends to it. The new contact goes on the flow’s account when the flow has one, and on no account otherwise. It isn’t pushed to your CRM. An existing contact is used as is, and its accounts don’t change.

Attachments

Any attachments saved on the template are sent automatically. Files added on this node are sent in addition to the template’s attachments. The combined set is subject to the same caps as elsewhere: up to 10 files and 20 MB total per email. See Attachments under Send Email V2 for supported file types and approver review behavior.

Send Consolidated Email V2

Sends a single email to multiple recipients in a To / CC / BCC layout — useful for digests, weekly roll-ups, and shared announcements. Unlike Email Template V2 (which sends one personalized email per recipient), Consolidated Email sends one message that everyone in the audience receives together.

Configuration

Field	Description
Email Template	Select the template to send. Templates that reference `{{ contact.* }}` variables are not allowed here because per-recipient personalization isn’t possible in a single email.
To (Audience)	Segment whose contacts populate the TO field. All TO recipients see each other.
CC (Audience)	Optional segment whose contacts populate the CC field.
BCC (Audience)	Optional segment whose contacts populate the BCC field.
Test Mode	Toggle to send only to the test email below (skips HIL and recipient lists).
Test Email	Address to receive the test send.
Attachments	Files to send in addition to the template’s own attachments

When to Use

Send a weekly account digest to a CSM, their manager, and the AE on CC
Notify a customer’s executive sponsor and copy the internal team
Broadcast a release announcement to a curated audience

Attachments

Attachments saved on the selected template are sent automatically. Files added on this node are appended to the template’s attachments and applied to the single consolidated email. The combined set is subject to the same caps: up to 10 files and 20 MB total. See Attachments under Send Email V2 for supported file types and approver review behavior.

If the To audience has multiple recipients, the template body must not include {{ contact.* }} variables — those resolve per-recipient and can’t be personalized in a consolidated send. Use Email Template V2 instead if you need personalization.

Approval Behavior

Send Consolidated Email supports Human-in-the-Loop. When approval is required, the pending email shows the full TO / CC / BCC list and the resolved email body so reviewers can confirm the audience before sending.

Slack V2

Sends a message to a Slack channel.

Configuration

Field	Description
Channel	Select Slack channel
Message	Message content (supports Slack markdown and @ notation)
Include Citations	Send the citations of an upstream Stella or Pre-Built Agent node as numbered links, in internal channels only (on by default). See Citations.

Example Message

:warning: *Account Alert*

*@account_data.name* requires attention

• Health Score: @account_data.health_score
• Owner: @account_data.owner_name
• ARR: $@account_data.arr

<https://app.statisfy.com/accounts/@account_id|View Account>

Slack Formatting Tips

Syntax	Result
`text`	Bold
`_text_`	Italic
`:emoji:`	Emoji
`<url\|text>`	Hyperlink
`\n`	New line

Slack Channel Manager V2

Creates a Slack channel (or uses an existing one), invites people to it, and can post an opening message.

Configuration

Field	Description
Channel ID	An existing channel to use — leave blank to create or find one by name
Channel Name	Name of the channel to create or find
Private Channel	Create the channel as private (default: off)
Configure People and Roles	People to add to the channel — by comma-separated email addresses and/or by role
Message	An optional message to post to the channel once it’s ready

Notify User on Slack V2

Sends a direct message from the Statisfy Slack app to a specific person on Slack. Use this when you want to reach an individual privately instead of posting in a channel.

Configuration

Field	Description
Message	The DM body — supports markdown and @ notation. Markdown is auto-converted to Slack’s `mrkdwn` format.
Notify Person or Role	Choose who to message. You can target a specific person by email, or a role (e.g., Account Owner, CSM) — the role is resolved to the connected person on the relevant account.
Include Citations	Send the citations of an upstream Stella or Pre-Built Agent node as numbered links, to internal people only (on by default). See Citations.

Resolution Order

If multiple targeting options are configured, Statisfy resolves the recipient in this order:

Explicit email address
Role on the account (e.g., Account Owner) resolved through the account in flow context
Falls back to the user attached to the flow context (e.g., the task assignee)

Prerequisites

Slack integration must be installed
The target user must have an email that matches a Slack workspace member
The Statisfy Slack app must be reachable in the user’s workspace

When to Use

Privately nudge an account owner when their account drops to At Risk
DM a CSM with the agenda before an upcoming meeting
Alert the assigned task owner without posting in a public channel

Slack channel messages and DMs are separate components — use Slack V2 to post in a channel and Notify User on Slack V2 to DM an individual.

Send Microsoft Teams Message

Posts a new conversation in a Microsoft Teams channel. The post comes from the Statisfy app.

Configuration

Field	Description
Channel	Select the Teams channel from the list. Click the refresh button to reload the list. You can also type the channel’s ID, its name, or “Team/Channel”. If two teams have a channel with that name, use “Team/Channel”.
Message	Message content in Markdown

Prerequisites

Microsoft Teams must be connected
Statisfy must be installed in the channel’s team, and the team must show Ready to send in the Teams settings

Teams has no direct messages, channel creation, or attachments in Agent Studio: there is no Teams version of Slack Channel Manager V2 or Notify User on Slack V2.

Gmail Send V2

Sends an email through a connected Gmail account.

Configuration

Field	Description
To	Recipient email address(es) - supports @ notation
Subject	Email subject line
Body	Email body content (supports HTML and @ notation)
CC	Carbon copy recipients (optional)
BCC	Blind carbon copy recipients (optional)
Role	Select which connected user’s Gmail account to send from

Prerequisites

Google Workspace integration must be connected
The sending user must have authorized Gmail access

When to Use

Send emails from a specific team member’s Gmail (e.g., the account owner)
Replies and follow-ups appear in the sender’s Gmail thread
Use instead of Send Email V2 when you need emails to come from a real person’s inbox

Gmail Reply Listener V2

Listens for replies to emails sent by Gmail Send V2 and triggers downstream actions.

Configuration

Field	Description
Linked Gmail Send	The Gmail Send V2 node to monitor for replies
Timeout	How long to wait for a reply before timing out

When to Use

Wait for a customer to respond to an outreach email
Trigger follow-up actions based on whether a reply was received
Build conversational email sequences

Task Management Actions

Create Task V2

Creates a new task in Statisfy.

Configuration

Field	Description
Title	Task title
Description	Task description
Assignee	User to assign the task to
Due Date	When the task is due
Priority	Task priority level
Account	Associated account (auto-populated from context)

Example

Title: Follow up with @account_data.name
Description: Health score dropped. Review and schedule call.
Assignee: @account_data.owner_email
Due Date: (3 days from now)
Priority: High

Create Task (Advanced) V2

Creates a task with full configuration options.

Additional Configuration

Field	Description
Task Type	Select task type
Tags	Add tags to the task
Custom Fields	Set custom field values
Watchers	Add users to watch the task

Add Task Comment V2

Adds a comment to an existing task.

Configuration

Field	Description
Task ID	The task to comment on (from context or specified)
Comment	Comment content
Mention Users	Users to mention in the comment (optional)

CRM Actions

Create Salesforce Case V2

Creates a case in Salesforce.

Configuration

Field	Description
Subject	Case subject
Description	Case description
Priority	Case priority
Account	Salesforce account ID
Contact	Salesforce contact ID
Case Type	Type of case

Prerequisites

Salesforce integration must be configured
User must have appropriate Salesforce permissions

Fields maintained by AI

The custom field actions below can also fill in fields marked Maintained by AI:

The field’s history shows the value as written by a flow. Writing the same value again adds nothing to the history.
While a person is holding their own value on the field, the flow skips that field and carries on with the others. The action’s result lists it under held fields, with the date the hold ends, and doesn’t count it as updated. Flows saved before this was added show held fields once their actions are updated.
A field maintained by another Statisfy AI can’t be written by a flow, and neither can a value that doesn’t fit the field’s type. The action stops at that field and fails with a message saying why; fields it already set stay set.

Custom Field Updater V2

Updates custom fields on Statisfy entities.

Configuration

Field	Description
Entity Type	Account, Contact, Task, etc.
Entity ID	The entity to update (from context or specified)
Field Updates	Key-value pairs of fields to update

Example

Entity Type: Account
Entity ID: @account_id
Field Updates:
  - last_automation_run: (current timestamp)
  - risk_flag: true

Opportunity Custom Field Updater V2

Updates custom fields specifically on opportunities.

Configuration

Field	Description
Opportunity ID	The opportunity to update
Field Updates	Custom field values to set

Upstream Custom Field Updater V2

Updates custom fields on parent/related entities.

When to Use

Update account fields from a task automation
Sync data from child to parent entities

Custom Object Field Updater V2

Updates field values on the instances (records) of a custom object, such as Invoices or Contracts.

Configuration

Field	Description
Custom Object	Required. The custom object whose instances you want to update. The filter and field pickers below only show this object’s fields.
Custom Object Filter	Optional. Narrows which instances of the selected object to update. Leave it empty to update every instance.
Custom Field Updater	The fields to set on each matching instance, and their values

When the flow runs for a specific record, the update is scoped to that record: instances of account-linked objects are limited to the current account, and instances of contact-linked objects to the current contact.

Output

Returns updated_count (fields updated) and instance_count (instances matched). If nothing matches, it returns No matching instances found with updated_count: 0.

When to Use

Update every instance of an account-linked object for the account the flow is running on
Update only the instances that match a filter on the object’s fields
Differs from Custom Field Updater V2, which updates fields on Statisfy entities (Account, Contact, Task, and so on) rather than custom object instances

Custom Field Populator V2

Sets several custom-field values on an entity in one step, from a table where each row is a field to write.

Configuration

Field	Description
Entity Type	The entity whose custom fields to populate (Account, Contact, Opportunity, etc.)
Field Schema	A table of fields to write — each row has a Custom Field Key, a Value, an Action (how to apply it), and an optional Reason

When the field is maintained by AI and the value changes, the Reason is shown in the field’s history, so people can see why the flow set the value. Other fields ignore it.

Output Data

Returns how many fields were updated, and any held fields a person’s hold kept from changing.

Project Actions

Create Project V2

Creates a new project from a template.

Configuration

Field	Description
Template	Project template to use
Project Name	Name for the new project
Account	Associated account
Owner	Project owner
Start Date	Project start date

Get Project Link V2

Retrieves the URL link to a project.

Configuration

Field	Description
Project ID	The project to get the link for

Output Data

{
  "project_link": "https://app.statisfy.com/projects/proj_123"
}

Document Actions

RTE Document Populator V2

Creates or updates a rich-text document — title, tag, and markdown content — for the account in the flow’s context.

Configuration

Field	Description
Document Segment	Which document to find or create (matched by tag/title) — selecting by tag is preferred
Document Tag	The tag to associate with the document. Select an existing tag, or type a new tag name and press Enter to create it
Document Title	The document’s title
Content (Markdown)	The markdown content written into the document

Fetch RTE Document V2

Retrieves content from a rich text document.

Configuration

Field	Description
Document Segment	Which document to fetch (matched by tag/title)

Pin Content V2

Pins content to an entity for quick access.

Configuration

Field	Description
Entity Type	Where to pin the content
Entity ID	The specific entity
Content	Content to pin

Data Actions

SQL Query V2

Executes a SQL query against your data.

Configuration

Field	Description
Query	SQL query to execute
Parameters	Query parameters (for safe interpolation)

SQL queries are executed with read-only access for safety. Use other action components for write operations.

Example

SELECT account_id, name, health_score
FROM accounts
WHERE health_score < 50
AND owner_id = :owner_id

Output Data

The component returns the query results in two formats:

html_table — the results rendered as an HTML table, ready for display (for example, embedding in an email or document).
data_table — the results as structured data for programmatic use by downstream nodes and agents. This matches the shape of the Integration Call V2 warehouse-query output, so you can process results from either component the same way.

{
  "html_table": "<table border=\"1\" class=\"dataframe\">...</table>",
  "data_table": {
    "columns": ["account_id", "name", "health_score"],
    "rows": [
      { "account_id": "acct_1", "name": "Acme", "health_score": 42 }
    ],
    "row_count": 1,
    "truncated": false
  },
  "row_count": 1
}

Use data_table when a downstream node needs to read individual values or iterate over rows. Use html_table only for display. If the query returns no rows, html_table contains a “No results found” message and data_table has empty columns and rows with row_count: 0.

Get Contact ID from Email V2

Resolves a contact ID from an email address.

Configuration

Field	Description
Email	Email address to look up

Output Data

{
  "contact_id": "contact_123",
  "contact_found": true
}

AI-Powered Actions

Risk Mitigation Agent V2

Uses AI to generate a risk mitigation plan.

Configuration

Field	Description
Account Context	Account information to analyze
Risk Factors	Specific risk factors to address

Output Data

Returns a structured risk mitigation plan with recommended actions.

Risk Summarization Agent V2

Creates a summary of risk factors and recommended actions.

Configuration

Field	Description
Account Data	Account information
Recent Activities	Recent activity context

Survey Template V2

Sends a survey to an audience from a saved survey template.

Configuration

Field	Description
Survey Template	The survey template to send
To (Audience)	Who receives the survey
Test Mode	Send a one-off test copy before sending to the real audience (default: off)
Test Email	The address the test copy is sent to when Test Mode is on
Template Variables	Values for the `account.`, `contact.`, and `user.*` variables the survey’s email uses. Each value is a literal or an `@` reference to an upstream node.

Template variables work the same way as on Email Template V2. Set contact.email to send the survey from a flow with no account or contact context, such as a warehouse trigger.

Integration Actions

API Call V2

Makes HTTP API calls to external services with built-in authentication support.

Configuration

Field	Description
URL	API endpoint URL (required)
Method	HTTP method: GET, POST, PUT, PATCH, DELETE, HEAD
Authentication	None, API Key, Bearer Token, or Basic Auth
Secret Value	Select stored secret for credentials (from Settings > Secrets)
API Key Header/Param Name	Header or query param name for API key (shown when auth = API Key)
API Key Location	Send API key in Header or Query Parameter (shown when auth = API Key)
Username	Username for Basic Auth (shown when auth = Basic Auth)
Send Custom Headers	Toggle to add custom HTTP headers
Headers (JSON)	Custom headers as JSON, e.g. `{"X-Custom": "value"}`
Send Query Parameters	Toggle to add URL query parameters
Query Parameters (JSON)	Query params as JSON, e.g. `{"page": "1"}`
Send Request Body	Toggle to add a request body (for POST/PUT/PATCH)
Request Body (JSON)	JSON request body
Timeout	Request timeout in seconds (default: 30)
Max Retries (rate limits)	How many times to retry when the API responds with `429 Too Many Requests`. Retries honor the response’s `Retry-After` header (falling back to exponential backoff), plus a small random delay. Default 3; set to 0 to disable. Range 0–10.
Follow Redirects	Whether to follow HTTP redirects (default: true)
Strict JSON Parsing	When enabled, invalid JSON in the request body, headers, or query parameters fails the component and logs the error to the Logs tab. When disabled (default), malformed JSON is silently ignored and the request still runs.

Example: Call External Webhook

URL: https://api.example.com/webhook
Method: POST
Authentication: Bearer Token
Secret Value: my-api-token
Body: {"account": "@account_data.name", "event": "health_drop"}

Output Data

{
  "url": "https://api.example.com/webhook",
  "success": true,
  "status_code": 200,
  "data": { "received": true }
}

All credentials are retrieved securely from Google Secret Manager. Configure your secrets in Settings > Secrets before using authentication. If the service you’re calling is already connected as a Statisfy integration, use Integration Call V2 instead — it reuses the integration’s stored credentials with no secret setup.

If the external service rate-limits you (HTTP 429), API Call V2 automatically retries up to Max Retries (rate limits) times before failing — waiting as long as the service’s Retry-After header asks. Raise this for strict-quota APIs, or set it to 0 to fail fast instead of waiting.

A non-2xx HTTP response (any 4xx or 5xx status) now fails the component and stops the flow at this node — downstream nodes do not run, and there is no error response for a later node to inspect. The status code and a short response snippet are written to the flow’s Logs tab. If you need to guard against failures, do it before the API Call — for example, validate inputs upstream, or run a separate lightweight probe request earlier in the flow and branch on its result.

Integration Call V2

Calls a connected integration’s API using the credentials already stored for that integration. Unlike API Call V2, you don’t provide a URL or select a secret — you pick an integration your org has connected, and Statisfy resolves the base URL and credentials for you.

When to Use Integration Call V2 vs. API Call V2

	Integration Call V2	API Call V2
Target	An integration already connected in Statisfy	Any HTTP endpoint you specify by URL
Credentials	Resolved automatically from the connected integration	You select a stored secret and auth type
Endpoint	Operation path only (e.g. `query`) — no host or scheme	Full URL
Warehouse queries	Supported (SQL query instead of endpoint)	Not supported

Use Integration Call V2 when the service you want to reach is already connected in Statisfy. Use API Call V2 for arbitrary external endpoints that aren’t connected integrations.

Configuration

Field	Description
Integration	Which connected integration to call. The dropdown is populated from your org’s connected integrations.
Endpoint	The operation to call, as that integration’s own API docs name it — e.g. `query` for Salesforce or `works.get` for DevRev. No host or scheme: the base URL is resolved from the integration.
Method	HTTP method: GET, POST, PUT, PATCH, DELETE (default: GET)
Payload (JSON)	Request body/params as JSON, e.g. `{"q": "SELECT Id FROM Account"}`. Supports flow variables.
Timeout (seconds)	Maximum time to wait for the call to complete before failing (default: 30)

Warehouse Integrations

When you select a warehouse or query-style integration (Snowflake, Postgres, Redshift, BigQuery, MySQL, Databricks, PostHog), the form changes:

The Endpoint field becomes SQL Query — enter the query to run against that warehouse.
The Method and Payload fields are hidden; they don’t apply to queries.
The result is returned as a table of rows.

Supported Integrations

Integration Call V2 supports connected integrations including Salesforce, HubSpot, Jira, Zendesk, Rocketlane, Wrike, DevRev, Pylon, Slack, Firefly, DealHub, Google Drive, Chorus, Fathom, Granola, Clari Copilot, Avoma, Attention, Unthread, Qualtrics, and Gainsight, plus the warehouse integrations listed above. Only integrations your org has connected appear in the dropdown.

Example: Query Salesforce

Integration: Salesforce
Endpoint: query
Method: GET
Payload (JSON): {"q": "SELECT Id, Name FROM Account WHERE Id = '@account_data.crm_id'"}

Example: Run a Snowflake Query

Integration: Snowflake
SQL Query: SELECT product, usage_minutes FROM usage_daily WHERE account_id = '@account_data.crm_id'

Output Data

{
  "integration": "salesforce",
  "endpoint": "query",
  "success": true,
  "data": { "records": [ { "Id": "001...", "Name": "Acme" } ] }
}

If the call fails (for example, the integration’s API returns an error), the component returns success: false with an error message instead of stopping the flow. Check the success field downstream before using the data. An unsupported integration or invalid JSON payload fails the node immediately.

Integration Call V2 uses the credentials of the integration as connected for your whole org. Any flow can call any connected, supported integration — there is no per-flow authorization step.

Stella V2

Executes natural language business intelligence queries using the Stella AI engine.

Configuration

Field	Description
Query	Natural language query to execute (e.g., “What are the top risks for this account?”)
Account Segment	Segment of accounts to run the query on (optional)

When to Use

Generate AI-powered account insights within automations
Run business intelligence queries as part of a workflow
Get natural language summaries of account data

Output Data

Returns the Stella query response as text.

Inside an automation, Stella still has full access to your customer data, but it can only use the MCP server and API tools set to Always allow in Stella’s external tools settings. Tools that need approval aren’t available, because no one is there to approve them while the flow runs.

Workflow Control

Sleep V2

Pauses workflow execution for a specified duration, then automatically resumes. Input data passes through unchanged.

Configuration

Field	Description
Sleep For	Number of time units to sleep (default: 1)
Time Unit	Hours or Days

When to Use

Wait before sending a follow-up message
Add a delay between actions (e.g., create task, wait 2 days, check status)
Schedule time-delayed notifications

Example: Follow-up Reminder

Trigger → Send Email → Sleep (2 days) → Send Follow-Up Email

The Sleep component pauses the entire workflow execution. When resumed, data passes through unchanged to the next node.

Human-in-the-Loop V2

Pauses workflow execution for human approval before continuing. The workflow resumes only after a user approves or rejects the request.

Configuration

Field	Description
Subject	A short title/description for the approval request
Notify on Slack	Send a Slack notification to the approver when approval is needed

When to Use

Require manager approval before sending external communications
Review AI-generated content before it’s sent
Gate critical actions (e.g., creating Salesforce cases) behind human review

Example: Approval Before Email

Trigger → Generate Email (LLM) → Human-in-the-Loop → Send Email

The workflow pauses at the Human-in-the-Loop node. An approver reviews the generated email in Statisfy and approves or rejects it. If approved, the workflow continues and sends the email.

Approver review of attachments

When the held draft is an email from Send Email V2, Email Template V2, or Send Consolidated Email V2, the approval view lists each attachment on the drafted message. The approver can:

Remove any attachment from a specific draft before approving.
Undo a removal from the Pending changes panel to restore an attachment before the draft is approved.

Attachments the approver removes are excluded from the outgoing email when the draft is approved.

Approval requests appear in the Approvals section in Statisfy. Enable Slack notifications to alert approvers immediately.

Best Practices

Use @ notation for dynamic content

Always use @ notation to reference data from upstream nodes rather than hardcoding values. This makes your automations flexible and reusable.

Test actions individually

Use the play button to test each action node before activating the full flow. This catches configuration errors early.

Handle missing data gracefully

Add conditions before actions to check that required data exists. This prevents errors when data is unexpectedly missing.

Log important actions

For critical actions, consider adding logging or notifications so you can track what the automation did.

​Action Components

​Communication Actions

​Send Email V2

​Configuration

​Approval before sending

​Citations

​Attachments

​Example Configuration

​Output Data

​Email Template V2

​Configuration

​When to Use

​Template variables

​Attachments

​Send Consolidated Email V2

​Configuration

​When to Use

​Attachments

​Approval Behavior

​Slack V2

​Configuration

​Example Message

​Slack Formatting Tips

​Slack Channel Manager V2

​Configuration

​Notify User on Slack V2

​Configuration

​Resolution Order

​Prerequisites

​When to Use

​Send Microsoft Teams Message

​Configuration

​Prerequisites

​Gmail Send V2

​Configuration

​Prerequisites

​When to Use

​Gmail Reply Listener V2

​Configuration

​When to Use

​Task Management Actions

​Create Task V2

​Configuration

​Example

​Create Task (Advanced) V2

​Additional Configuration

​Add Task Comment V2

​Configuration

​CRM Actions

​Create Salesforce Case V2

​Configuration

​Prerequisites

​Fields maintained by AI

​Custom Field Updater V2

​Configuration

​Example

​Opportunity Custom Field Updater V2

​Configuration

​Upstream Custom Field Updater V2

​When to Use

​Custom Object Field Updater V2

​Configuration

​Output

​When to Use

​Custom Field Populator V2

​Configuration

​Output Data

​Project Actions

​Create Project V2

​Configuration

​Get Project Link V2

​Configuration

​Output Data

​Document Actions

​RTE Document Populator V2

​Configuration

​Fetch RTE Document V2

​Configuration

​Pin Content V2

​Configuration

Action Components

Communication Actions

Send Email V2

Configuration

Approval before sending

Citations

Attachments

Example Configuration

Output Data

Email Template V2

Configuration

When to Use

Template variables

Attachments

Send Consolidated Email V2

Configuration

When to Use

Attachments

Approval Behavior

Slack V2

Configuration

Example Message

Slack Formatting Tips

Slack Channel Manager V2

Configuration

Notify User on Slack V2

Configuration

Resolution Order

Prerequisites

When to Use

Send Microsoft Teams Message

Configuration

Prerequisites

Gmail Send V2

Configuration

Prerequisites

When to Use

Gmail Reply Listener V2

Configuration

When to Use

Task Management Actions

Create Task V2

Configuration

Example

Create Task (Advanced) V2

Additional Configuration

Add Task Comment V2

Configuration

CRM Actions

Create Salesforce Case V2

Configuration

Prerequisites

Fields maintained by AI

Custom Field Updater V2

Configuration

Example

Opportunity Custom Field Updater V2

Configuration

Upstream Custom Field Updater V2

When to Use

Custom Object Field Updater V2

Configuration

Output

When to Use

Custom Field Populator V2

Configuration

Output Data

Project Actions

Create Project V2

Configuration

Get Project Link V2

Configuration

Output Data

Document Actions

RTE Document Populator V2

Configuration

Fetch RTE Document V2

Configuration

Pin Content V2

Configuration