Skip to main content
Webhook lets ChatbotX send contact data to another application, such as a CRM, Google Sheets, Zapier, or Make. Creating and enabling a Webhook does not send data by itself. ChatbotX sends the Webhook when its configured event matches an Action executed by a Perform Action node in Flow Builder.

​
Webhooks interface

The Webhooks page contains these management areas:
  • Folders: Group Webhooks so they are easier to manage.
  • Webhooks: A list of every Webhook you created, with a toggle to turn each one on or off.
  • Create Webhook: Click + Create Webhook, then enter a name.
webhooks_create

​
Create and configure a Webhook

1

Create a Webhook

Open Webhooks, click + Create Webhook, enter a name, and click Create.
2

Choose the condition

Under When this happens, select the event the Webhook should listen for. The Webhook is sent when an Action in a Flow produces this event.Available groups include:
  • Tags: Tag Applied and Tag Removed
  • Custom Fields: Custom Field Changed, DateTime Based Trigger, New Contact, conversation assignment, and other contact events
  • Sequences: Subscribed To Sequence and Unsubscribed From Sequence
  • Entry Point Link: Contact Referred A New Contact and Contact Referred Existing Contact
3

Enter the destination URL

Paste the URL of the external application into the URL field. ChatbotX sends the request to this address when an Action in a Flow matches the configured event.
4

Save the Webhook

Click Save, then make sure the Webhook is enabled in the Webhooks list.
webhooks_rule

​
Webhook event scope in Flow Builder

Webhook events are limited to Flow Builder and do not monitor changes across the entire Workspace. ChatbotX checks for a matching Webhook event only when an Action runs inside a Perform Action node. The same type of change made elsewhere in the Workspace does not trigger the Webhook.
For example, assume a Webhook is configured with the Tag Applied event:
  • Webhook is sent: A contact reaches a Perform Action node that applies a Tag. The Action matches the configured event, so ChatbotX sends the Webhook.
  • Webhook is not sent: The same type of Tag change happens outside Flow Builder. ChatbotX does not treat that Workspace-level change as a Webhook event.
This scope lets you control exactly where the Webhook can run. Place the matching Action at the required point in the Flow instead of relying on activity elsewhere in the Workspace.
1

Open the Flow

Open Flows, then create a new Flow or edit the Flow that should send data to the external application.
2

Add a Perform Action node

Add a Perform Action node at the point where ChatbotX should send the Webhook.
3

Choose a matching Action

Open the Perform Action node, click Create, and choose an Action that produces the event configured in the Webhook. For example, if the Webhook listens for Tag Applied, add an Action that applies a Tag.
4

Connect and publish the Flow

Connect the node to the correct path in the Flow, then click Publish.
Choose an Action in a Perform Action node in Flow Builder

​
How a Webhook works

When a contact reaches a Perform Action node, ChatbotX executes the selected Actions. If one of those Actions matches an event configured for an enabled Webhook, ChatbotX sends an HTTP POST request to the saved URL. The receiving app, such as a CRM, Google Sheets, Zapier, or Make, then handles that data using its own logic. Common data included in the payload:
  • Contact name and contact ID
  • Channel, such as Messenger, WhatsApp, or Zalo
  • Existing Tags and Custom Fields
  • Information about the event that triggered the Webhook

​
Real examples

Each Webhook has its own toggle, so you can disable it without deleting the configuration. A disabled Webhook does not send data when a matching Action runs in a Flow.