Integration not firing

Estimated reading: 3 minutes

Your integration is saved, but submitting the form (or running the trigger event) doesn’t produce anything on the receiver side. Work through this checklist in order.

1 — Open the log first

Always start here. Go to AFI > Log and look for an entry timed to your test submission.

No entry at all → AFI never saw the submission. Continue to step 2.
Entry with a red status → AFI saw it but the receiver rejected the call. Click the row to see the API response — that error tells you what to fix.
Entry with a green status, but the data didn’t appear on the receiver → AFI thinks it succeeded. Re-check on the receiver (maybe under a different segment / tab) or see Fields arriving blank.

2 — Update AFI to the latest version

A significant share of “stopped working” tickets resolve to please update the plugin. Many receiver APIs (Klaviyo June 2024, Constant Contact OAuth, Pipedrive, etc.) have changed in ways that broke older AFI versions. Update before debugging further.

3 — Confirm the integration is active

AFI > Integrations — find the integration row. Status must be the green check-mark icon, not paused/disabled.
Open the integration in edit view and click Save again. This re-arms hooks that may have been broken by a plugin update or server restart.

4 — Verify the sender plugin is connecting

AFI listens for the sender plugin’s submission hook. If the sender plugin’s own validation rejects the submission, AFI never runs.

Submit the form once with valid test data. If the form’s own “Thank you” message doesn’t appear, the sender plugin itself is failing — fix that first.
Anti-spam plugins (CleanTalk, Wordfence) may intercept before AFI runs. Disable temporarily to test, then whitelist your test IP.
Fluent Forms — older AFI versions hooked into fluentform_before_insert_submission which fired even when Fluent Forms rejected the form. Fixed in v1.126.9 (hook moved to fluentform/submission_inserted). Update.

5 — Check the form / field selection

If you renamed or rebuilt the form in the sender plugin, the form ID may have changed. Re-open the integration, re-pick the form, save.
If your sender plugin lazy-loads its field schema (Forminator, Avada Form, some Elementor Pro setups), submit the form once with sample data first — AFI reads fields from the latest saved submission.
Click the Refresh button next to the Form Name dropdown.

6 — Check Conditional Logic

If you’ve added rules, they may be filtering out every submission. Temporarily remove the rules, test, and add them back one by one to find the offending rule. See Conditional Logic isn’t firing.

7 — Server-side issues

WP Cron must be running if your integration relies on the background queue.
WSOD / fatal errors after update — usually a PHP version mismatch or another plugin conflict. Update AFI to the latest; if it persists, deactivate other plugins one by one.
Cloudflare / WAF can block POST calls from your WordPress server to the receiver’s API. Add the receiver’s domain to your firewall’s allow-list.

8 — Last resort: turn on Error Email

Go to AFI > Settings > General and tick Send Error Email. From now on, AFI will email the admin every time a receiver call fails — useful to catch the next silent breakage without watching the log.