One automation layer for
rules and outbound events
ChatbotX lets teams define what should happen when contact data changes, conversations move, or new people arrive, then push the right action inside the platform or out to external systems through Webhooks.
When X happens, do Y automatically
Use one rule builder to monitor contact events, conversation state, sequence changes, and referral activity, then launch the next action without manual follow-up.
Build every rule from two columns
The rule builder follows a simple model: choose the condition that should be monitored, then choose the actions ChatbotX should perform when that condition is true.
When this happens
Choose the event or state change to watch
Tags, field changes, assignment events, new contacts, archived conversations, sequence membership, and entry-point referrals can all start a rule.
Actions
Choose what the system should do next
Apply tags, update fields, start another flow, transfer to a human, or push the result into Google Sheets automatically.
VIP handling
When the tag VIP is applied, transfer the conversation to a human agent immediately.
Sequence enrollment
When a contact subscribes to a sequence, add a lifecycle tag like Being nurtured.
Welcome flows
When a new contact arrives from an entry point link or campaign source, start the right welcome flow automatically.
Tags
Trigger when a tag is applied or removed so segmentation and routing can update in real time.
Tag Applied
Tag Removed
Conversation and field events
Watch contact data and handoff states so one rule layer can react to operational changes across the inbox.
Custom Field Changed
DateTime Based Trigger
Transferred to Human or Bot
New Contact
Unsubscribed From Broadcast
Archived, Follow Up, Assigned, Unassigned
Sequences
Use sequence membership changes to sync lifecycle state and trigger the next nurture step automatically.
Subscribed To Sequence
Unsubscribed From Sequence
Entry Point Link
React when a contact refers a new or existing person so referral-driven journeys can branch instantly.
Contact Referred A New Contact
Contact Referred Existing Contact
What the system can do next
Add Tag
Apply a tag to the contact automatically.
Remove Tag
Remove a tag when the rule no longer applies.
Set Custom Field
Write a new value into any chosen custom field.
Clear Custom Field
Reset a field when the state should be removed.
Start Another Flow
Launch the next flow automatically from the same event.
Transfer Conversation to Human
Hand the chat to a person or team member immediately.
Google Sheets
Push contact data into a connected sheet without copy and paste.
New Contact to Google Sheets
Use a rule to capture ad-driven leads the moment they arrive, then write the name and other mapped fields to Google Sheets automatically.
Condition
New Contact
Action
Google Sheets with mapped columns
Result
Every new lead is saved automatically with no manual spreadsheet work.
Rule logic note
A single rule can include multiple conditions and multiple actions at the same time. ChatbotX runs the rule only when all configured conditions are met together.
Send ChatbotX events to external systems
Webhooks turn internal events into outbound HTTP POST requests, so CRM, helpdesk, reporting, and automation tools can react as soon as the chosen condition happens.
Organize and control each webhook
Folders
Group Webhooks by campaign, workflow, or channel so the list stays manageable.
Webhook list with toggles
Every webhook can be turned on or off individually without being deleted.
Create Webhook flow
Create a webhook, enter a name, choose the condition, paste the endpoint URL, then save.
Webhooks use the same condition families
The event list mirrors the Triggers feature, so teams can choose the same contact and conversation signals whether the next action should happen inside ChatbotX or in an external system.
Tags
Tag Applied, Tag Removed
Custom Fields and conversation state
Field changes, DateTime triggers, transfers, New Contact, Broadcast unsubscribe, Archived, Follow Up, Assigned, Unassigned
Sequences
Subscribed To Sequence, Unsubscribed From Sequence
Entry Point Link
Contact Referred A New Contact, Contact Referred Existing Contact
URL setup
Paste the endpoint URL of the external application that should receive the event. That address becomes the destination ChatbotX calls every time the chosen condition is met.
HTTP POST behavior
When the selected condition happens, ChatbotX automatically sends an HTTP POST request to the configured endpoint so downstream tools can continue the workflow.
Payload contents
Typical payload data includes contact name and ID, channel, tags, custom fields, and information about the event that fired the webhook.
What teams usually connect
CRM sync
Create or update leads in HubSpot or Salesforce when a new contact arrives or an important tag changes.
Support handoff
Create a ticket in Freshdesk or Zendesk when a conversation transfers to a human agent.
Sheets and reporting
Push milestone data, qualified leads, or closed orders into Google Sheets the moment the event happens.
Sequence downstream automation
Notify email or automation tools when a customer subscribes to a sequence so follow-up systems stay aligned.
Keep Webhooks manageable at scale
Each webhook has its own toggle, so teams can pause behavior without deleting it. Folders make it easier to group endpoints by campaign, business unit, or channel.
Why teams pair both layers
Use Triggers & Actions when the next step should happen inside ChatbotX. Use Webhooks when the same event needs to notify another app and continue the workflow outside the platform.
Frequently
asked
questions
