Integrations overview
GuideForms integrations let you send lead and session data to external services automatically. When a visitor submits a lead form or completes a guide, the data can be forwarded to a webhook endpoint, added to FluentCRM, or used in other connected systems. Integrations are a Pro feature.
How integrations work
When a visitor triggers an integration event (submitting a lead form or completing a guide), GuideForms doesn’t send the data immediately. Instead, it adds a job to a processing queue. A background task (powered by WP-Cron) picks up queued jobs and delivers them to the configured services. This keeps the visitor’s experience fast — they never wait for an external API call to finish.
Available integrations
GuideForms ships with three built-in integrations:
- Webhook — Send an HTTP request to any URL when a lead is submitted or a guide is completed. Works with Zapier, Make, n8n, or any custom endpoint.
- FluentCRM — Create or update contacts in FluentCRM with lead data, assign lists and tags, and optionally sync the visitor’s guide selections.
- AAWP — Not a lead integration. AAWP connects Amazon product data as a filter source for your guides. See the dedicated page for details.
Per-guide activation
Integrations are configured per guide, not globally. In the Guide Editor, open the Integrations tab to see all available integrations. Each one has an Enable toggle — turn it on and configure the settings for that specific guide. This means you can send webhook data for one guide but not another, or assign different FluentCRM tags depending on the guide.
Queue processing
The integration queue runs via WP-Cron on a one-minute schedule. Each run processes up to 10 jobs in a single batch. If a delivery fails (network error, API timeout, etc.), GuideForms retries the job up to 3 times with exponential backoff:
- First retry — After 2 minutes.
- Second retry — After 4 minutes.
- Third retry — After 8 minutes.
After 3 failed attempts, the job is marked as failed and no further retries are made. Failed jobs are kept in the queue table for debugging.
Data sent to integrations
When an integration fires, it receives a standard set of data from the session:
- Guide ID and title — Which guide the visitor interacted with.
- Session ID — The unique session identifier.
- Selections — Every choice the visitor made, with step titles and selection labels.
- Result IDs — The post IDs that matched the visitor’s filters.
- Lead data — If the trigger is a lead form submission: all submitted fields (name, email, custom fields).
- Timestamp — When the event occurred.
Each integration type formats this data differently — webhooks send it as JSON, FluentCRM maps it to contact fields, etc. See the individual integration pages for payload details.
WP-Cron dependency
The queue depends on WP-Cron running reliably. On most WordPress sites, WP-Cron fires on every page load, which is fine for moderate traffic. On low-traffic sites or sites with DISABLE_WP_CRON set, you should set up a real server cron job to call wp-cron.php every minute. Without this, queued integrations won’t process until someone visits the site.