Zapier Integration
Send Fanflet events to 7,000+ apps via webhooks. Up to 5 webhook URLs on Studio, with retry and a payload preview.
Overview
The Zapier integration sends Fanflet lead events to any of 7,000+ apps: Google Sheets, Mailchimp, Slack, your CRM, and more. It works through webhook URLs. You create a Zap in Zapier with a webhook trigger, then paste the URL into Fanflet. Each new lead captured for your sponsored content fires a POST to the Zap automatically.
Plan requirement
Sponsor Studio
Prerequisites
- 1.A Sponsor Studio account with at least one active speaker connection.
- 2.A Zapier account. Free tier works for basic Zaps. Paid tiers add multi-step Zaps and higher volume.
Step 1. Create a Zap in Zapier
Start a new Zap
Log into zapier.com and click Create, then Zaps.
Choose "Webhooks by Zapier" as the trigger
In the trigger search, type Webhooks by Zapier and select it. Pick the Catch Hook event, then click Continue.
Zapier asks you to Pick off a Child Key. Leave this blank and click Continue. Fanflet sends a flat JSON payload, so you map individual fields in the action step.
Copy the webhook URL
Zapier generates a unique webhook URL shaped like:
Copy the URL. Paste it into Fanflet in the next step. Keep the Zapier tab open. You return to it after sending a test event.
Step 2. Add the webhook URL to Fanflet
Open Integrations
In the sponsor dashboard, click Integrations in the sidebar. Find the Zapier card.
Add the webhook URL
Paste the URL you copied from Zapier into the URL field and click Add. The card updates to show a green Connected badge and lists the URL with a counter like 1 of 5 webhook URLs.
Send a test event
Click Send test event in the Zapier card footer. Fanflet sends a test.ping event to every registered URL so Zapier detects the payload shape.
Multiple webhooks
Inspect the test payload
Step 3. Finish the Zap in Zapier
Test the trigger in Zapier
Back in Zapier, click Test trigger. Zapier picks up the test event Fanflet posted. The payload fields appear and are ready for mapping.
Add an action
Pick what should happen when a lead arrives. Common options:
- 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 fields from the Fanflet payload (see Webhook payload below) to the action inputs.
Turn on your Zap
Test the full Zap end to end, then Publish. From this point, every lead captured on your sponsored content flows through Zapier.
Event types
Fanflet pushes the following event types. All events are enabled by default. Choose which events fire per connection in Event settings on the connection card.
| Event | Description |
|---|---|
subscriber.added | An attendee subscribed through a fanflet email form. |
lead.captured | An attendee clicked or downloaded a sponsored resource with consent. |
connection.accepted | A speaker accepted your connection request. |
connection.declined | A speaker declined your connection request. |
connection.ended | A speaker connection ended (by either party). |
report.viewed | Someone opened a shared report link. |
Event settings
Each connection has an Event settings panel. Click to expand it on the connection card. Two controls live there:
Events to push
Check or uncheck individual event types. Only checked events deliver to this connection. All events are enabled by default for backward compatibility.
Default campaign tag
A freeform text value (e.g., Q1-DENTAL-2026) 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 includes a data.campaigns array instead (see Webhook payload below).
Webhook payload
Every event POSTed to your webhook URL has this JSON structure. Payloads are 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 email (when a subscriber ID is present). |
data.subscriber_name | The attendee name, if provided at signup. |
data.fanflet_title | Title of the fanflet generating the event. |
data.speaker_name | The speaker hosting the fanflet. |
data.resource_title | The resource clicked or downloaded (for lead.captured events). |
data.campaigns | Array of active campaigns, merged from speaker assignments and resource-level tags 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 is test.ping and the data field contains sample values. Use this to set up field mapping in Zapier before real leads arrive. Test events are tagged TEST in the activity log and hidden by default.Activity log
The Recent activity card on the Integrations page lists every event Fanflet sent across all your integrations. Each row shows platform, event type, status, attempt count, time, and any error message returned by the destination.
Filter by status
The status dropdown filters by Success, Failed, Pending, or Retrying. Default is all statuses.
Show test events
A checkbox toggles test pings on and off. Test events stay hidden by default to keep the log focused on real leads. Toggle it on to confirm a fresh test reached the destination.
Retry failed events
Failed rows show a retry icon at the end of the row. Click it to re-send the event. Successful and pending rows have no retry control. The list refreshes once the retry completes.
Pagination
The log paginates 25 events per page. Use Previous and Next at the bottom of the table to walk back through history.
Pause vs disconnect
Pause and resume
Click Pause on the Zapier card to stop sending events without removing the connection. Webhook URLs and event settings stay intact. Leads still record in Fanflet. Click Resume to start delivery again. Use pause for temporary stops, like a Zapier maintenance window.
Remove a webhook URL
Click the trash icon next to any URL to remove it. Removing the last URL auto-disconnects the integration. The connection record is deleted along with its event settings.
Disconnect entirely
Click Disconnect to remove the Zapier connection and every webhook URL in one step. To reconnect, add a new URL. Past activity stays in the log.
Troubleshooting
Events show as failed in the activity log
Confirm the Zap is turned on in Zapier. Paused or draft Zaps return errors when Fanflet POSTs to the webhook. Verify the URL has not been deleted or regenerated in Zapier. Each Zap gets a unique URL.
Test event works but real leads do not arrive
Confirm at least one active speaker connection exists and the speaker has a published fanflet with a sponsor block linked to your account. Leads only generate when an attendee interacts with sponsored content.
Duplicate events
With multiple webhook URLs registered, each URL receives every event independently. By design. Remove extra URLs if you only need one destination.
Retry behavior
Failed events retry up to 3 times with exponential backoff. After the final attempt fails, the event is logged as failed. Click the retry icon next to a failed row to re-send it manually.
Zapier free tier limits
Where to go next
- HubSpot integration. Direct contact and deal sync without Zapier in the middle.
- Sponsor lead generation. How leads are captured, consent rules, and what flows into the payload.