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 : Select subscription group you want to send message. Ensure the message respects user opt-in preferences.

• Content:

  • Start from scratch: Create a new email template manually.

  • Browse templates: Use an existing saved template.

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.

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.

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.

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.

5. Update trait

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

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.

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