> For the complete documentation index, see [llms.txt](https://docs.sortment.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sortment.com/journeys/journey-components/action-blocks.md).

# Action blocks

The **Action** blocks in Sortment Journeys defines the communication or outputs triggered for users as they progress through a journey. These actions are critical for delivering messages across various channels - Email, SMS, WhatsApp - or for triggering updates and integrations via API.

Let's explore each block and how to configure them effectively:

### 1. Send Email

**Purpose**: Deliver an Email to users at a specific point in their journey.

**Configuration steps**:

* **Sending information**:
  * **Integration**: Defaults to the configured email provider (e.g., Sendgrid) but can be changed.
  * **Send as**: Auto-populated with the default sending identity (e.g., `Marketing Sortment`).
  * **Reply to**: Pre-filled, but editable to suit campaign needs.
  * **Send to**: Select the appropriate Email field from user properties.
  * [**Subscription group**](/settings/subscription-groups-and-contact-fields.md#how-subscription-groups-work-in-sortment) : Select subscription group you want to send message. Ensure the message respects user opt-in preferences.

<figure><img src="https://233844858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmbOMKRXus6KHDbeQALkO%2Fuploads%2Fgit-blob-2ecdc578b74676f1472bfac79cbe690cf59b6ca9%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* **Content**:
  * **Start from scratch:** Create a new email template manually.
  * **Browse templates:** Use an existing saved template.

{% hint style="danger" %}
**Status Tags**:

"Setup pending" appears if required fields like recipient or content are missing.
{% endhint %}

***

### 2. Send SMS

**Purpose**: Send a text message to users at a defined point in their journey.

**Configuration steps**:

* **Sending information**:
  * **Integration**: Default SMS provider (e.g., Twilio) is pre-selected. Can be changed.
  * **Send to**: Choose the user’s mobile number from available properties.
* **Content**:
  * **Start from scratch:** Create a new message.
  * **Browse templates:** Select from saved SMS templates.

<figure><img src="https://233844858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmbOMKRXus6KHDbeQALkO%2Fuploads%2Fgit-blob-19a3969c310aab1f5d31e64668654bf41e32960d%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Status tags**:\
"Setup pending" appears when the block is not fully configured or some entries are missing.
{% endhint %}

***

### 3. Send WhatsApp

**Purpose**: Sends a WhatsApp message to users.

**Configuration steps**:

* **Sending information**:
  * **Integration**: Pre-set based on your default WhatsApp channel. Editable.
  * **Send to**: Choose a WhatsApp contact property from the user profile.
* **Content**:
  * Select from already existing templates or create a new one from scratch.

<figure><img src="https://233844858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmbOMKRXus6KHDbeQALkO%2Fuploads%2Fgit-blob-cb8a0a6bfeab7736cb87bb23731670bf2769f900%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="danger" %}
Setup pending will appear if the block isn’t fully configured (e.g., missing template or incomplete integration).
{% endhint %}

### 4. Call API

**Purpose**: Sends an HTTP request to an external API as part of a user’s journey. Useful for webhooks, syncing external systems, or fetching decision data.

<figure><img src="https://233844858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmbOMKRXus6KHDbeQALkO%2Fuploads%2Fgit-blob-390335e354684184d1d38557ac7e2da3ae1a3345%2Fa10.png?alt=media" alt="" width="348"><figcaption></figcaption></figure>

**Configuration fields**:

* **Method**: Choose from standard HTTP methods:
  * `GET` – retrieve data from an endpoint.
  * `POST` – send new data to an endpoint.
  * `PUT` – update existing data.
  * `DELETE` – remove data.
* **Endpoint**: Enter the full API URL. (Must begin with `http://` or `https://`).
* **Headers**: Add key–value pairs for content-type, auth tokens, etc.
* **Request Body**: JSON formatted. (Use **tidy mode** or expand for easier editing).
* **Mapping API Response**:
  * **Use keys from response payload:** Map data returned by the API for use in later blocks.
  * Paste a JSON response to extract and select values, or manually add fields.

{% hint style="success" %}
Note: Use the “@” symbol to dynamically reference user-specific properties from your schema throughout the API call configuration.
{% endhint %}

{% hint style="danger" %}
"Setup pending" will appear until all required fields (at minimum, method and endpoint) are properly configured.
{% endhint %}

***

### 5. Update trait

**Purpose**: Updates a user trait (property) within the journey. Helpful for tracking status, assigning flags or storing metadata.

<figure><img src="https://233844858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmbOMKRXus6KHDbeQALkO%2Fuploads%2Fgit-blob-6513c1034fac1a87b3acf68816444f73698d9827%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

**Configuration fields**:

* **Select property**: Choose or create a trait (e.g., `status`, `segment`).
* **Set value to**: Define the new value for the selected trait.
  * You can enter static values directly (e.g., `"betaUser"`).
  * Or insert dynamic values from earlier steps in the journey using the **@** token selector (e.g., from API response or event payload).

**Use cases:** Track engagement, assign test variants, or mark users progress for downstream targeting.

***

### 6. Add to journey

**Purpose**: Move users to another journey, enabling modular flows and multi-step campaigns.

**Configuration fields**:

* **Add users to**: Choose a target journey from the list of available, externally enabled journeys.

{% hint style="warning" %}
**Note:** Only published journeys that are configured to accept external entries will appear in the dropdown.\
\
If the desired journey isn’t listed, ensure the target journey includes a **Trigger block**, is fully configured, and has been **published**. You’ll need to complete those steps before you can connect it via the **Add to Journey** block.
{% endhint %}

This block is useful for handing off users to specialised flows, like feedback collection, re-engagement campaigns, or transactional messaging sequences.