Zapier Integration
Connect Fanflet to 7,000+ apps via Zapier webhooks for automated workflows.
Overview
The Zapier integration lets you send Fanflet lead events to any of 7,000+ apps—Google Sheets, Mailchimp, Slack, your CRM, and more. It works via webhook URLs: you create a Zap in Zapier with a webhook trigger, then paste the URL into Fanflet. Every time a new lead is captured for your sponsored content, Fanflet POSTs the event to your Zap automatically.
Prerequisites
- 1.A Fanflet sponsor account with at least one active speaker connection.
- 3.A Zapier account (Free tier works for basic Zaps; paid tiers unlock multi-step Zaps and higher volume).
Step 1 — Create a Zap in Zapier
Start a new Zap
Log into zapier.com and click Create Zap (or the + button).
Choose "Webhooks by Zapier" as the trigger
In the trigger search, type Webhooks by Zapier and select it. Choose the Catch Hook event type, then click Continue.
Zapier will ask you to Pick off a Child Key—leave this blank and click Continue. Fanflet sends a flat JSON payload, so you'll map individual fields in the action step instead.
Copy the webhook URL
Zapier will generate a unique webhook URL that looks like:
Copy this URL—you'll paste it into Fanflet in the next step. Don't close Zapier yet; you'll come back to test the trigger.
Step 2 — Connect in Fanflet
Open Integrations
In the sponsor dashboard, click Integrations in the sidebar. Find the Zapier card.
Add the webhook URL
Paste the webhook URL you copied from Zapier into the URL field and click Add. The card will update to show a green Connected badge.
Send a test event
Click Send test event in the Zapier card footer. This sends a test.ping event to your webhook so Zapier can detect the payload shape.
Multiple webhooks
Step 3 — Complete Your Zap
Test the trigger in Zapier
Back in Zapier, click Test trigger. Zapier should pick up the test event you just sent from Fanflet. You'll see the payload fields available for mapping.
Add an action
Choose what should happen when a lead arrives—for example:
- Google Sheets— append a row to a spreadsheet
- Slack— post a notification to a channel
- Mailchimp— add the email to an audience
- HubSpot— create or update a contact
- Email— send yourself a summary
Map the fields from the Fanflet payload (see Webhook payloadbelow) to the action's inputs.
Turn on your Zap
Test the full Zap, then Publish it. From now on, every lead captured on your sponsored content will flow through Zapier automatically.
Event Types
Fanflet can push the following event types to your webhooks. By default all events are enabled. You can control which events are delivered per connection in Event settings (see below).
| Event | Description |
|---|---|
subscriber.added | An attendee subscribed via a fanflet email form |
lead.captured | An attendee clicked or downloaded a sponsored resource (with consent) |
connection.accepted | Your connection request was accepted by a speaker |
connection.declined | Your connection request was declined by a speaker |
connection.ended | A speaker connection was ended (by either party) |
report.viewed | A shared report link was viewed |
Event Settings
Each integration connection has an Event settings panel (click to expand it on the connection card). Two controls are available:
Events to push
Check or uncheck individual event types. Only checked events will be delivered to this connection's webhooks. All events are enabled by default for backward compatibility.
Default campaign tag
A freeform text value (e.g., Q1-DENTAL-2026) that is included in every event payload as data.campaign_tag. Use this for CRM campaign attribution when no Fanflet campaign is assigned to the speaker. If the speaker is assigned to one or more active campaigns, the payload will include a data.campaigns array instead (see Webhook Payload below).
Webhook Payload
Every event POSTed to your webhook URL has this JSON structure. Payloads are automatically enriched with human-readable names and campaign context before delivery.
{
"event_type": "subscriber.added",
"sponsor_id": "uuid",
"timestamp": "2026-03-16T14:30:00.000Z",
"data": {
"subscriberId": "uuid",
"fanfletId": "uuid",
"speakerId": "uuid",
"subscriber_email": "attendee@example.com",
"subscriber_name": "Jane Smith",
"fanflet_title": "Southwest Dental Conference 2026",
"speaker_name": "Dr. Sarah Mitchell",
"campaigns": [
{
"id": "uuid",
"name": "Q1 Dental Outreach",
"analytics_tag": "Q1-DENTAL-2026",
"crm_reference": { "hubspot_campaign_id": "abc123" },
"attribution": "both"
}
]
}
}| Field | Description |
|---|---|
event_type | The domain event (e.g., subscriber.added, lead.captured, test.ping) |
sponsor_id | Your sponsor account UUID |
timestamp | ISO 8601 timestamp of the event |
data.subscriber_email | The attendee's email address (when a subscriber ID is present) |
data.subscriber_name | The attendee's name (if provided at signup) |
data.fanflet_title | Title of the fanflet that generated the event |
data.speaker_name | The speaker who hosts the fanflet |
data.resource_title | The resource that was clicked or downloaded (for lead.captured events) |
data.campaigns | Array of active campaigns from speaker assignments and resource-level tags (merged and deduplicated). Each entry has id, name, analytics_tag, crm_reference, and attribution ("speaker", "resource", or "both"). Present only when campaigns are assigned. |
data.campaign_tag | Fallback campaign tag from the connection's Default campaign tag setting. Present only when no campaigns are assigned to the speaker. |
Test events
event_type will be test.ping and the data field will contain sample values. Use this to set up field mapping in Zapier before real leads arrive.Managing Your Connection
Pause & resume
Click Pauseon the Zapier card to temporarily stop sending events. Leads are still captured in Fanflet but won't be pushed to your webhooks until you click Resume.
Remove a webhook
Click the delete icon next to any URL to remove it. If you remove the last URL, the connection is automatically disconnected.
Disconnect entirely
Click Disconnect to remove the Zapier connection and all its webhook URLs. You can reconnect at any time by adding a new URL.
Troubleshooting
Events showing “failed” in the activity log
Check that your Zap is turned onin Zapier. Paused or draft Zaps return errors when Fanflet POSTs to the webhook. Also verify the URL hasn't been deleted or regenerated in Zapier (each Zap gets a unique URL).
Test event works but real leads don't arrive
Make sure you have at least one active speaker connection and the speaker has a published fanflet with a sponsor block linked to your account. Leads are only generated when an attendee interacts with your sponsored content.
Duplicate events
If you have multiple webhook URLs registered, each URL receives every event independently. This is by design—remove extra URLs if you only need one destination.
Retry behavior
Failed events are retried up to 3 times with exponential backoff. If all retries fail, the event is logged as failed in the activity log. You can click Retry next to any failed event to re-send it manually.
Zapier free tier limits