For the complete documentation index, see llms.txt. This page is also available as Markdown.

Agentic Workflow Messages Actions

Overview

Messages actions send communications to the Contact Record in context. These actions are only available when the Agentic Workflow is built on a Contacts Object; they do not appear in Agentic Workflows built on other Object types such as Objects or Workflow stages.

Two actions are available:

  • Send Email: sends a templated or newly composed email to the Contact.

  • Send Text: sends a plain-text SMS message to the Contact using your configured text messaging provider.

Both actions support merge fields for personalization and share the same error handling model as other action steps.

Note: For error handling, see Agentic Workflow Error Handling.


Send Email

The Send Email action sends an email to the Contact Record currently in context.

Additional Description: An optional freeform text field for internal notes about the step. This value is not included in the email.

CC Team Members: Use the CC Team Members dropdown to copy one or more team members on the outgoing email. The following options are available:

  • None: No team members are copied. This is the default.

  • Last Active Team Member (Any Role): Copies the most recently active team member on the Record, regardless of role.

  • Last Active Team Member (Specific Role): Copies the most recently active team member on the Record who holds a specified role.

  • Specific Team Members: Copies one or more named team members selected at design time.

  • Custom Team Selector Field: Copies the team member resolved by a team selector field on the context Record.

Choose Email To Send: Select or create the email to send using one of two options:

  • CHOOSE EMAIL FROM LIBRARY: Opens the Choose Email Template dialog, where you can browse and select from saved Templates, Broadcasts, or Agentic Workflows emails.

  • CREATE NEW EMAIL: Opens the email builder to compose a new email directly.

  • Based on your email account type, a daily quota applies to emails sent via the selected integrated inbox


Send Text

The Send Text action sends a text message to the Contact Record currently in context.

Additional Description: An optional freeform text field for internal notes about the step. This value is not included in the message.

Text Message Body: Compose the message content in the Text Message Body field. Use + INSERT MERGE FIELD to insert dynamic values from fields on the context Record. Available merge fields are organized by category; for example, the Contact Info category includes fields such as Link to Record, First Name, Last Name, Email, and Date Created.

The body supports up to 10 message segments of 153 characters each, for a maximum of 1,530 total characters. The character counter below the field displays remaining characters in the current segment and total characters used.


Key Use Cases

Messages actions are applicable across any Workflow that requires direct communication with Contacts at a defined point in an automated process. The following examples illustrate common patterns in three industries where timely, automated outreach is a core operational requirement.

Industry Examples

Insurance operations depend on prompt, accurate communication with policyholders and claimants at key points in the policy and claims lifecycle.

Examples include:

  • Using Send Email to deliver a policy renewal notice to the Contact when an Agentic Workflow detects an upcoming expiration date, with merge fields populated from the policy record

  • Using Send Text to send an immediate SMS confirmation to a claimant when a new claim record is created and the Agentic Workflow reaches the notification step

  • Using Send Email to notify a Contact of a coverage change or endorsement, attaching a templated summary email composed in the email builder

  • Using Send Text to follow up with a Contact who has not responded to a previous outreach, using a short merge-field-personalized message within the 1,530-character limit

How Messages actions help:

  • Deliver policy and claims communications automatically at the right moment in the workflow, without requiring manual outreach from team members

  • Personalize messages at scale using merge fields drawn from the Contact Record

  • Maintain a consistent communication cadence across high-volume Contact populations such as renewal books or open claims queues


What's Next?

Continue to Agentic Workflow Code Steps to learn how the execution engine processes action steps at runtime, including the asynchronous queue model, execution lifecycle, step isolation, and ordering guarantees.

Last updated

Was this helpful?