Meta in workflows

If the agent's automatic reply isn't enough — you want to filter, decide, notify someone or record a contact before replying — you can handle Meta inside a workflow. The Workflows section provides triggers, an agent node and a send action.

When a workflow is worth it

• You only want to reply to certain messages (for example those containing a keyword) and ignore the rest.
• You want to save the contact, open a ticket or notify the team before or after replying.
• You want the reply to go through a condition or a wait.
• You want to process the leads collected by Meta's ad forms.

“Meta DM received” trigger

Starts the workflow when a direct message arrives on Instagram or Facebook. You can restrict it to a single platform or leave it on both, and choose which connected Meta account to listen on. The received message and the sender's details are available to the following nodes.

“Meta Agent” node

Has the reply written by the brain of a Meta agent you already configured: you choose which agent and what text to feed it. The node returns the reply as data without sending it: you decide whether and how to send it, for example with the send node below. This way you reuse the agent's instructions, documents and tools inside your own logic.

“Send Meta DM” action

Sends a direct message to a person on Instagram or Facebook. You specify the Meta account, the recipient (usually taken from the trigger) and the text, which can be the one produced by the “Meta Agent” node or a fixed text. Remember the 24-hour window: outside it, Meta may refuse the send.

“Meta Lead Ads” trigger

Starts the workflow when someone fills in a contact form linked to your Meta ads. You choose the account, the Page and the form to listen on; the fields the user filled in reach the workflow, where you can save them to your address book, start a call or send a welcome message.

Avoiding double replies