Edit and update contact attributes - both system attributes (first name, last name, email, phone) as well as all custom contact attributes.

Actions by data type

Enter values:

Special feature for email and phone number:

A contact has only ONE primary email and phone number - this is used for automations, campaigns and all communication. The contact can have additional emails and numbers, these are only for documentation purposes.

Toggle "Set as primary email address":

Common use cases:

Important concept - saving data for other automations:

Use "Edit contact" to save information in contact attributes that you can later use in other automations with filters/conditions.

System variable "Current date/time" is particularly important:

Create a custom contact attribute of type "Date / Time" and save timestamps there for later timing logic.

Examples:

Timing-based routing logic

Status tracking

The principle:

Save data in contact attributes (especially timestamps with system variables) to use them later in other automations for intelligent filter and routing logic. This way you build complex, context-dependent automation flows.

Update contact lists of the selected contact.

Actions:

Works exactly like update label - only for contact lists instead of conversation labels.

Use cases:

Deletes the contact permanently.

Important - No follow-up path possible:

No further path can follow after this node. As soon as the contact is deleted, the automation ends automatically - the contact no longer exists.

Use case: Automate GDPR requests

Update labels of the selected conversation.

Actions:

Use cases:

Assigns the conversation to one or more users.

Settings:

1. Assign specific user:

2. Assign any user:

3. Reset assignment:

Important - Inbox access:

The selected users must have access to the inbox where the conversation is located. If a user does not have access to the inbox, the assignment will not take place.

Common use cases:

Marks the conversation as spam. No configuration needed.

Use case:

Marks the conversation as completed. No configuration needed.

Use case:

Deletes the conversation.

Settings:

Use case:

Moves the conversation to another inbox.

Use cases:

Creates a note in the conversation.

Common use cases:

Ends other running automations on this contact.

Important for automation hierarchy:

Control which automations are allowed to run simultaneously.

Use cases:

Starts another automation. With this node the current automation ends.

Settings:

Select automation:

Only automations with manual trigger can be started. The list only shows automations that are published, active and have the trigger "Manually triggered".

Input fields:

If the target automation has input fields in the manual trigger, they must be filled in here. All fields can be populated with variables.

Use cases:

Send and receive data from external systems via HTTP requests.

Settings:

Method:

URL:

Enter URL - can be dynamic with variables (variable icon available)

Additional request elements (optional):

Response:

The node shows the status (e.g. "Successful request - 200") and the response data in the body.

Test function:

Test the request directly in the node before you publish the automation.

Saved variables - Very important:

You can save specific fields from the response as variables:

Send conversion events to the Meta Conversion API to improve your ad performance. Ideal for click-to-WhatsApp ads.

Prerequisite:

Before you can use this node, the Conversions API must be activated for your WhatsApp channel:

Settings:

Select event type:

Select lead identification:

Meta must be able to identify the contact to assign the conversion event to the correct user.

Option 1: Click-to-WhatsApp ad ID

Option 2: Custom lead identification

Additional contact data (optional):

You can send additional contact attributes that Meta uses for ad optimization. Data that Meta requires in hashed form is automatically hashed by Superchat before sending.

Common use case:

You can use multiple conversion event nodes in one automation - one for each step in the funnel (e.g. first "Lead Submitted", later "Appointment Scheduled").