smb_app_state_sync webhook reference | Developer Documentation

Check Business app contact sync with ChatArchitect

If your team keeps the WhatsApp Business app alongside ChatArchitect, check whether address-book contacts are available in the connected CRM and how changes affect existing records. The app remaining active does not establish automatic CRM contact synchronization.

The ChatArchitect API quick start does not specify address-book sync callbacks or rules for creating, updating or deleting CRM contacts. Confirm these for the particular connection with support. Follow the coexistence guide for the supported setup.

Separate address-book changes from customer messages

Meta's app-state-sync reference concerns the business app's address book. Its add action can describe both a newly added contact and an edited contact; removal is another action, with some name details absent. These platform definitions do not specify the transformed ChatArchitect callback or the CRM action.

• Confirm which business connection owns the address-book data before matching it to a CRM record.
• Check the supported contact identifier and matching rule. A changed display name alone is insufficient to choose a record.
• Keep add/update handling separate from removal handling. Do not create a new CRM contact on every name update.
• Removing an address-book entry does not establish that a CRM record and its conversation history should be deleted.

A contact shared by a customer inside a conversation is another message type. Use the incoming contact-card checklist for that case. A synchronized address-book entry does not establish that the person agreed to receive marketing; review the permission workflow before adding them to a campaign.

Verify the supported contact workflow

1. Identify the connected business number, receiving integration and intended destination for contact data. Confirm whether the route provides an initial contact import, later updates or neither.
2. For a custom application, obtain a redacted supported example, contact-identity mapping, add/update/removal semantics and duplicate-handling rules. Use the webhook overview for receiver checks.
3. If the route is confirmed, use a test contact your team is permitted to manage. Compare the original app address-book entry with any corresponding CRM record before enabling automatic changes.
4. Check a supported name update and verify that it affects the intended record once. Confirm which existing CRM values the integration is allowed to replace.
5. Review removal behavior using an approved test or a redacted supported sample. Confirm that unrelated records, tasks and history are retained according to the receiving system's policy.
6. Record the source-change time and processing result separately. Check how repeated or delayed events are handled before applying them to live contacts.

When contact data differs between the app and CRM

If automatic synchronization is unavailable, use the receiving system's normal reviewed contact-maintenance process. Confirm the customer association before updating a CRM name or number. A contact sync check does not establish that earlier chat history was imported.

For support, provide the business connection, integration version, change time with time zone, available reference and the expected record/action. Use test details or a redacted sample and follow the data-handling guide. See Meta's address-book sync reference for the provider interface; confirm ChatArchitect's mapping before automating contact changes.