Distinguish an inbound event from an outbound AI tool call. Your system can report an event to a configured receiver, while the assistant can call an enabled endpoint for a record it needs; neither is a universal native integration.
WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.
For inbound store events, map the configured receiver’s event/topic and customer fields. The receiver recognizes source headers and payload hints for configured order/cart/status flows. A provider preset alone does not prove that every event is emitted or that every payload is compatible.
For an AI HTTP tool, configure the endpoint, authentication and input fields. Gather the required customer identifier before asking the source for account-specific data, then answer from the returned record. An identifier alone is not a full customer-authentication guarantee.
Test the payload, authorization, missing fields and failed-source behavior. Real journey triggers include lead/deal/appointment/store/inactivity events where emitted by the supported code paths; an external event or endpoint does not automatically authorize a WhatsApp send.
Obtain explicit permission for the WhatsApp messages the recipient expects and honor opt-outs. The customer-service window opens or resets with each user message and lasts 24 hours. Outside it, use an appropriate approved template; template approval does not replace consent or guarantee delivery.
Source endpoints and permissions need separate testing. Inbound/webhook send paths must be reviewed individually for consent and approved-template/window enforcement; do not assume every integration inherits campaign safeguards. No unrestricted chat initiation or universal calendar/refund execution is claimed.
Source endpoints and permissions need separate testing. Inbound/webhook send paths must be reviewed individually for consent and approved-template/window enforcement; do not assume every integration inherits campaign safeguards. No unrestricted chat initiation or universal calendar/refund execution is claimed.
Choose inbound event ingestion or an outbound read-tool task.
Configure authentication, event/field mapping and minimal required inputs.
Verify success and failure behavior without sending unconsented or ineligible messages.
No. A source event is not consent, template approval or an open customer-service window. Review the specific send path and current WhatsApp requirements before activation.
Obtain explicit permission for the WhatsApp messages the recipient expects and honor opt-outs. The customer-service window opens or resets with each user message and lasts 24 hours. Outside it, use an appropriate approved template; template approval does not replace consent or guarantee delivery.
WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.
WhatsApp opt-in and consent records
WhatsApp Business Platform pricing — Delivered-message billing depends on recipient market and category; consult the current rate card and account invoice.
Cloud API getting started — Account and number prerequisites; Meta controls availability and approval.
WhatsApp Business Messaging Policy — Consent, acceptable use and messaging restrictions still apply.