Quick answer
An integration can fail even when the website still loads. Forms, booking tools, mailing lists, inventory feeds, and payment connections need checks that follow data through the intended workflow.
Before you begin
List each integration, its owner, the information it transfers, and a safe way to test it. Identify notifications or actions that a test might trigger.
What to do
- Define the expected starting event and final result. For a form, this might include a saved entry, notification, and a record in the connected system.
- Check credential expiry, webhook configuration, recent vendor notices, and error alerts through authorized accounts. Do not expose tokens while collecting evidence.
- Run a labeled, coordinated test using synthetic information. Confirm each required destination instead of relying on a success message on the page.
- Record timing, identifiers, duplicate handling, and any missing fields. Test an error or retry path where the integration supports it safely.
- Assign a review schedule and an escalation contact. Repeat checks after plugin updates, account changes, or replacement of connected services.
How to check the result
The integration should produce the expected result without unexpected duplicates, private-data exposure, or live operational actions. A successful API response is not proof that staff received or processed the record.
If you need help
If data is missing, provide the test time, source event, and redacted record identifiers. Avoid repeatedly reconnecting accounts without understanding the current configuration; doing so can create duplicate subscriptions or lose historical mappings.
Related help
- Plan what happens after a website inquiry form is submitted
- Make website form notifications use an authorized mail path
- Create a clear handoff after a website incident
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
