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:

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

Using Custom Event Parameters

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

🚧

Important

1. 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.

2. 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.

3. 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.

📘

Note

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. That alone doesn't mean the contact is picked up automatically: even a standard EmailAddress has to be mapped explicitly in the block's Advanced parameters, and the Email field must contain the exact event variable — for example ${EmailAddress} or ${emailAddress}, matching what your payload sends.

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 result means the block received no valid email address, phone number, or token to work with.

📘

Note

If the Email field of a sending block contains a standard variable such as ${email} or ${emailAddress} and its value in the event is empty, the message is still sent — to the contact's email channel taken from the workflow context. Skipping the send when the value is empty works only with a non-standard variable name: a block whose Email field references a custom variable with an empty value doesn't send the message.

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.

A message block sends one message to one recipient — it cannot send to several addresses at once. To send a copy of the message to each additional static address:

1. Copy the block with the selected message in the workflow — one block per additional address, plus the original block that sends the message to the contact themselves.
2. In the copied block's advanced parameters, enter the static address in the Email field and clear the Contact ID field, so the message goes to the specified address rather than to the contact from the workflow context.