What AFI doesn’t do
Some integrations and features come up regularly in support but are out of AFI’s scope. If you’re after one of these, AFI isn’t the right tool — and this page exists to save you the back-and-forth.
Two-way sync
AFI is a one-way, fire-and-forget pipe: form/event happens on WordPress → data is pushed to the receiver. There is no support for syncing changes back from the receiver into WordPress, nor for keeping records in lockstep across both sides.
If you need two-way sync (e.g. WordPress users ↔ HubSpot contacts always in sync), use a dedicated sync tool. AFI can push the initial signup; a separate tool handles the round-trip.
Real-time data export / CSV download from AFI
AFI doesn’t include an export / backup interface for past form submissions or log entries. If you need ongoing data export:
- Form submissions live in the sender plugin’s own database. Export them from the sender plugin (Gravity Forms, WPForms, Forminator all have entry exports).
- AFI Logs live in
wp_adfoin_log. You can SQL-export the table if needed. - AFI Integrations live in
wp_adfoin_integration. Back this up before site migrations.
Captcha / spam filtering
AFI doesn’t filter spam. If you’re getting junk submissions, install a Captcha or anti-spam plugin (CleanTalk, Akismet, hCaptcha, reCAPTCHA) on the sender form. AFI fires after the sender plugin accepts the submission — so filtering upstream stops spam reaching the receiver too.
File hosting / attachment storage
When a sender form has a file upload, AFI passes the file’s URL to the receiver — it doesn’t re-upload the file itself. The file stays on your WordPress media library (or the sender plugin’s upload folder).
- Receivers that can re-fetch from URLs (Google Drive, Dropbox) will retrieve the file.
- Receivers that expect plain text (Mailchimp custom fields) just store the URL as a string.
If you want the file uploaded to cloud storage instead of left on WordPress, pair AFI’s Google Drive / Dropbox receiver action with the form submission.
Updating existing records in Google Sheets / spreadsheets
AFI appends a new row to a Google Sheet (or Smartsheet, or Zoho Sheet) per submission. It doesn’t find an existing row by email and update it. If you need that, do the dedup downstream (e.g. via a Google Apps Script triggered on edit) or use a CRM as the receiver instead.
Custom payment processing
AFI doesn’t process payments. If a sender plugin handles payment (WooCommerce, GiveWP, EDD, WPForms Payments), AFI can push the post-payment data, but the payment itself goes through the sender’s gateway.
Replacing your sender plugin’s notifications
AFI runs alongside the sender plugin’s built-in admin / user notifications — it doesn’t suppress them. If you want the sender plugin to stop emailing on each submission (e.g. when integrating CF7 with Zoho Desk), turn off the sender’s own mail via its settings. For CF7 specifically, add skip_mail: on to the form’s Additional Settings.