Advanced Workflow Block Parameters

Fill the advanced parameters in the following cases:

When using custom event parameters
For sending messages to an additional contact
For inserting dynamic content

List of Additional parameters:

Parameter	Description
Contact ID	Contact identifier in the system or an event parameter containing it.
Email	Contact's email address or an event parameter containing the email address.
Phone	Contact's phone number or an event parameter containing it.
Token	Contact's token or an event parameter containing it.
Language	Message language. Leave the field blank if you use a multilingual message in the workflow. Learn more about setting up multilingual campaigns >

Let's view each case of parameter configuration in detail.

📘
Note
If the Language field is empty, the language of a multilingual message is taken from the contact card: the matching language version is sent if it exists, otherwise the main version. A language passed in an event parameter is not applied automatically. To use it, put the full variable form in the Language field — for example $data.get('attribution.lang'); the short form ${attribution.lang} does not work.

Using Custom Event Parameters

By default, when starting a workflow, the event should pass standard parameters for contact identification:

Event parameters	Identifiers
ContactId	Contact ID
externalCustomerId	External ID
Email EmailAddress UserEmail ContactEmail	Email
Phone SMS PhoneNumber	Phone number
PushToken MobPushToken TelegramBotToken	Contact token

🚧

The primary identifier is ContactId. If it is not specified but at least one of the other identifiers is provided, ContactId will be automatically added to the event.

To start workflows, the system identifies the contact for which the event was received. The system searches for the contact using the following rules:

Contact ID has the highest priority among all parameters.

Entered contact email, phone number, or token are used for sending.

If externalCustomerId is specified, the message is sent to the contact it belongs to; among those contacts that were found by email address, phone number or token.

If externalCustomerId is not specified, the message is sent to the contact found by email address, phone number or token.

If a contact is not found, a new contact will be created for sending.

For data consistency, provide parameter names according to the specified list.

If the parameters in the event don't match the standard values, such as using PersonalEmail instead of EmailAddress, like on the screen below

In this case, specify the name of the corresponding variable in the Email field.

📘
EmailAddress is one of the standard parameter names the system can use to match an event to a contact, and the name comparison is case-insensitive. However, this does not mean that a contact is created automatically.
Even a standard EmailAddress has to be mapped explicitly in the block's Advanced parameters: the Email field must contain the exact event variable, for example ${EmailAddress} or ${emailAddress}, matching the spelling in your payload.
For a backend event, linking the event to the contact card additionally requires segmentation to be enabled for that event type.
The Empty contact media error means that the block received no valid email address, phone number, or token.
If the Email field of a sending block contains a standard variable — ${email} or ${emailAddress} — and its value in the event is empty, the message is still sent: the system falls back to the email channel of the contact identified in the workflow context. Skipping the send when the value is empty works only with a non-standard variable name.

Sending Messages to an Additional Contact

For example, if you need to duplicate the message sent to the user and send it to the manager.

Copy the block with the selected message in the workflow and specify the manager's contacts in the advanced parameters.

📘
A message block sends to one recipient at a time — it cannot send one message to several addresses at once. To send copies of an email to additional static addresses, add a separate message block for each address: in its Advanced parameters, enter the address in the Email field and clear the Contact ID field. Keep a separate block with default parameters for sending to the contact themselves.

The platform has no carbon-copy or blind-carbon-copy field — a message always has one sender and one recipient. Personalization in a copy is resolved for the address that copy goes to, so a copy sent to a static address doesn't carry the original contact's data.

Updated about 22 hours ago

Did this page help you?