message_template_components_update webhook reference | Developer Documentation

Check changed WhatsApp template content in ChatArchitect

After editing a WhatsApp template, check which version your connected tool will send and which customer response it expects. A changed account preview does not establish that a CRM selection, variable mapping or button action has refreshed.

You can edit templates in wtargeted.com. Use the template change guide for the editing workflow. This checklist covers the content seen by dependent tools after the change. The ChatArchitect API quick start does not specify template-component callbacks or automatic refresh across integrations; confirm that behavior with support.

Identify the template and the changed content

• Record the connected account, template name, language and any identifier exposed by your tool.
• Keep the earlier wording, variable order and configured buttons as a comparison. Identify the person responsible for each affected campaign or automation.
• Compare the saved result in the account with the selected version in the sending tool. Similar names or different language versions need separate checks.
• Review the text, variable meanings, samples and button actions together. An unchanged variable count does not establish that the same customer fields still belong in those positions.

Meta's component-update reference describes a notification after a template edit, identifying the template and its language and reporting content elements. Some elements are conditional on the template's components. This provider interface does not establish which fields ChatArchitect forwards, whether a notice is a complete snapshot or how a CRM refreshes its stored selection.

The confirmed Submit template form offers text, variables and buttons. Use the component guide for those choices. Additional Meta header, footer or button formats are not established customer features merely because they appear in its event reference.

Recheck each dependent sending workflow

1. Arrange for affected future sends to be paused or reviewed using the controls available in the sending system. Check already accepted attempts separately; changing a template does not establish that they were cancelled.
2. Find the exact template and language in wtargeted.com. Check the current text and review result before treating the revised version as ready.
3. Refresh or reselect the template through the supported action in the connected tool. For a custom application, the quick start documents fetching templates with getHSM; use the returned send syntax and confirm the integration's refresh rules.
4. Inspect every variable mapping using harmless sample values. Review buttons for changed labels, destinations and expected responses. For a reply button, use the template-button reply checklist.
5. Run a permitted test through the intended tool and inspect the received message using the preview checklist. Compare the rendered wording, substituted values and each available action.
6. Record the checked template version and result with the workflow owner before allowing the next affected send.

A component change is separate from a review/status change, a quality change or a category change. Check the applicable result rather than treating one notification as approval, delivery or completion of a CRM refresh.

When the account and sending tool disagree

For support, provide the connection, template name and language, change time with time zone, affected sending tool and redacted before/after examples. Describe the expected and observed refresh without including App Secret or customer lists. See Meta's component-update reference for provider details; obtain ChatArchitect's event contract before automating updates.