WS Form

Estimated reading: 3 minutes

Overview

AFI captures submissions from the WS Form plugin and routes them to any receiver platform AFI supports — CRMs, email marketing tools, Google Sheets, Slack, webhooks, and more. As soon as a WS Form is submitted, AFI fires the integration, mapping each WS Form field onto the receiver’s fields.

Supported features

  • Listens for the submission event of any published WS Form (form ID is selectable in the integration).
  • Free version: AFI exposes text and email field types for mapping.
  • AFI Pro: exposes every WS Form field type, including selects, checkboxes, radios, files, hidden fields, and computed fields.
  • The form_id meta and all special tags ({{_date}}, {{_user_ip}}, {{_site_url}}, the UTM family, etc.) are available as mappable values.
  • Works with Conditional Logic — only send to the receiver when the submission matches your rules.

Requirements

  • WS Form LITE (free) or WS Form PRO 1.x or later, installed and activated.
  • At least one published WS Form on the site.

How to create the integration

  1. Go to AFI > New Integration.
  2. For Trigger, choose WS Form.
  3. Choose the specific WS Form you want to listen to from the dropdown. AFI fetches the list directly from the WS Form plugin.
  4. AFI reads the form’s fields and shows them in the mapping panel.
  5. Pick a Receiver (e.g. Mailchimp, HubSpot, Google Sheets) and the desired task.
  6. Map WS Form fields → receiver fields. Add any special tags or static values where the receiver requires data the form doesn’t collect.
  7. Optional: add Conditional Logic.
  8. Save. Submit the form once to confirm the integration works (check AFI > Log).

Notes & caveats

  • Free vs Pro field coverage. The free version of AFI only maps text and email fields. If your WS Form uses selects, checkboxes, file uploads, multi-row repeaters, or computed fields, you’ll need AFI Pro to expose them.
  • File uploads are sent as URLs (the public link to the uploaded file). Some receivers (e.g. Google Drive, Dropbox) can re-fetch the file from that URL; others (e.g. Mailchimp) expect plain text and will store the URL as-is.
  • Multi-row / repeater fields are flattened into a single value. If you need per-row processing, contact support.
  • Form ID renames. If you duplicate a WS Form or delete and recreate it, the form ID changes — your existing integration will quietly stop firing. Re-pick the form in the integration and re-save.
  • Drafts & partial submissions are not captured. AFI only fires on full, successful submissions.

Related