automatic_events webhook reference | Developer Documentation

Why automatic_events is not a ChatArchitect callback workflow

ChatArchitect does not support automatic detection of leads or purchases from Click-to-WhatsApp conversations and reporting those events to Meta Conversions API. Do not expect the Meta automatic_events webhook as part of that unsupported workflow. See the Automatic Events availability guide for the product scope.

Identify what your receiver actually needs

Use the ChatArchitect webhook guide and API quick start to establish the event contract. Confirm additional event formats and integration mappings before implementing them.

If your application waits for an automatic event

1. Check whether the requirement came from Meta documentation, an application specification or a supported ChatArchitect integration.
2. Separate receipt of the customer's message from any lead, order or payment recorded by your CRM or another business system.
3. If ordinary messages or outgoing results are missing, follow the webhook guide for receiver registration, routing and processing checks. Changing a working receiver to request an unsupported event can affect the existing integration.
4. If your goal is conversion reporting, confirm a separate tracking arrangement with the responsible provider. Do not mark a purchase as completed from a chat or message status alone.

Prepare a focused support request

Provide the affected connection, receiving application, expected business action, test time with time zone and the event type actually received. Include a redacted example only when needed to explain a parsing or routing problem. Keep credentials and customer message contents out of screenshots and shared logs.

For a separately implemented Meta interface

The official Meta automatic_events reference describes that developer interface. Its payload examples do not define a ChatArchitect callback, a CRM conversion or a payment confirmation.