---
title: "Messaging Action"
slug: "messaging-action"
updated: 2025-09-05T15:06:24Z
published: 2025-09-05T15:06:24Z
canonical: "docs.relaynetwork.com/messaging-action"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relaynetwork.com/llms.txt
> Use this file to discover all available pages before exploring further.

# RelayMessageAction

WARNINGThis action makes an external callout to Relay Network. Please be aware of any impacts this has against your Sales*f*orce API limits. [Salesforce Callout Limits](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_timeouts.htm)

The Relay Message action is used to trigger a Relay message to one or more users. This is a messaging only action and requires the user to have been previously onboarded to Relay.

---

### Relay Message Action Dialog

![SFDC - Flows - Action - Message](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/rn-sfdc-flows-action-message.png)

### Action Input Values

| Name | Description |
| --- | --- |
| Label | The label of the action which is displayed within the main flow layout. |
| API Name | The unique API Name of this flow action. |
| Description | Optional description of this action. |
| Relay Client ID | This optional field is used to identify the Relay Client ID in a multi-client setup. The majority of configuration will not be a multi-client setup. See: [Multiple Relay Clients in a Single Org](/v1/docs/multiple-relay-clients-in-a-single-org) |
| Run in background job (unmanned) Send via Future (managed) | This value determines if the **Relay Messaging Action** should run all processing (and callouts) in a background job. Sending in a background job is useful to prevent any slowdown in processing of the flow's primary logic and to get around pending transactions issues. - If no value is passed in, then the default value will be **{!$GlobalConstant.False}**. Valid values are: - {!$GlobalConstant.True} = Run the Relay action in a background job. - {!$GlobalConstant.False} = Run the Relay action in the current flow context. |
| Batch Request | Either this value or the *Single Request* value or both must be provided. - An apex-defined variable of type [RelayMessageRequest Resource](/v1/docs/relaymessagerequest-resource) which has the *Allow multiple values (collection)* option selected. - Allows you to send multiple Relay messaging requests in a single callout. This is more performant and reduced the consumption against your daily API limits. > [!CAUTION] > CAUTION > > When submitting a batch, make sure all records in the batch are of the same type. For example, don’t mix *account* and *contact* objects in a single batch. |
| Single Request | Either this value or the *Batch Request* value or both must be provided. - An apex-defined variable of type [RelayMessageRequest Resource](/v1/docs/relaymessagerequest-resource). - Typically used for Record Triggered flows as you are usually dealing with only the single record. |
| Dynamic input_ variable names | Optional. A flow variable resource with *Data Type* of **Text** and the *Allow multiple values (collection)* option checked. The resource collection should have been previously populated with a list of fields names. These field names will be used by this action to retrieve their values. The record, whose values will be retreived from, is identified by the *id* field provided in the *Batch Request* or *Single Request* resource. See: [Relay Dynamic Inputs](/v1/docs/relay-dynamic-inputs) |
| Dynamic input_ variable names and values |  |
| Trigger ID | Optional. Identifies the Relay message to be sent to the specified user(s). If no value is provided, then the *Trigger ID* must have been provided within the *Batch Request* or *Single Request* resource. The *Trigger ID* is defined within the Relay CXB Web Application. See: [Locating the Relay Trigger ID](/v1/docs/a-locating-the-relay-trigger-id) |

####