Leadspin Zapier integrationAutomate Leadspin with Zapier.
The Leadspin Zapier integration gives you 1 trigger, and no action or search. It picks up the leads your wheels collect and hands them to another tool. Zapier checks for them on a timer, so how fast they arrive depends on your plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Leadspin Zapier integration actually does
Leadspin collects leads through a game: visitors spin a wheel and leave their details. Zapier picks up each new lead from the wheel you choose and passes it to another tool, a CRM, an email tool or a spreadsheet. It is a one-way street: Leadspin starts Zaps, it never receives anything from them.
Wheel leads in your CRM, without exports. A visitor plays, New Wheel Leads picks the lead up, and the next step creates the contact in your CRM. Sales sees every player in the tool they already use.
A follow-up for each player. The same trigger can add the lead to an email tool, so the people who played hear from you without anyone moving a file around.
A tally per wheel. Because each Zap watches one wheel, a Zap per wheel sending rows to a sheet gives you a running list for each game.
What Zapier does not do here. One trigger, nothing else: a Zap cannot create a wheel, change one or edit a lead in Leadspin. The trigger is a polling one, so leads arrive at the pace of your plan, up to 15 minutes apart on the free plan. Leads collected before the Zap was switched on stay behind.
Adding a filter or a search to a Zap makes it multi-step, and a multi-step Zap needs a paid Zapier plan. If you are still choosing a tool, see our n8n vs Zapier comparison and our Zapier review.
Zapier vocabulary in one minute
Seven words you will see in the editor. Each is explained here once, then used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Leadspin, it is always a new lead registered on a wheel.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, here always in another app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts tasks, not players.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the new ones.
- Instant trigger
- A trigger the app reports itself the moment the event happens. Leadspin has none: its only trigger is a polling one.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
What a Leadspin Zap really costs
Leadspin is not a premium app, so it runs from the free plan. Zapier bills actions, not the checks it makes on your wheel.
- Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
- Premium appNo, Leadspin works on the free plan
- Trigger typePolling, the plan interval applies
The trigger never costs a task, and neither do Zapier's checks for new leads, however often they happen. Each action that succeeds counts once: a lead sent to a CRM costs one task, to a CRM and an email tool two. An action that fails is not counted. On the free plan, Zaps stop at two steps, one trigger and one action; a filter or a second action makes the Zap multi-step and needs a paid plan. The grid below is what matters here: it sets how long a new lead can wait before Zapier sees it.
Connect Leadspin to Zapier in three steps
- 01
Add a connection
Open the Apps page of your Zapier account and click + Add connection. Search for Leadspin in the dialog and pick it. You need a Leadspin account first, with access to the wheels whose leads you want to send on.
- 02
Sign in to Leadspin
Click Add connection. A tab opens on Leadspin: sign in with the account that owns, or can read, the wheels you plan to watch. The Zap only sees what this account sees.
- 03
Grant access
Allow Zapier to access the account. The connection then appears on your Apps page and every Leadspin trigger reuses it. Link it once, and every new Zap you build on a wheel picks it from a list.
Your first Leadspin Zap, step by step
GoalSend every lead from one Leadspin wheel into your CRM, so sales can follow up on each player.
- 01
Create the Zap on New Wheel Leads
Start a new Zap, choose Leadspin and the New Wheel Leads event, then your connection. In the required Wheel field, pick the wheel whose leads should reach the CRM.
- 02
Test with a real lead
Run the test: Zapier brings back the three most recent leads of that wheel. If the wheel is new, play it once yourself so there is a lead to pick.
- 03
Add a filter
Click the plus icon and add Filter. Set the field, the rule and the value, so only the players sales should call go through. The Zap becomes multi-step and needs a paid plan.
- 04
Add the CRM action
Add your CRM and its create-contact action. Map the lead details from Leadspin into the contact's fields, then test the step once.
- 05
Check, then publish
Check the new contact in the CRM, then click Publish. Zapier now checks the wheel at your plan's interval and sends each new lead on, at one task per lead.
The Leadspin trigger
1 event starts a Zap when something happens in Leadspin. Zapier checks for them at the interval your plan allows.
New Wheel Leads
Polling triggerIn Zapier“Triggers when a new lead is registered.”
Picks up each lead registered on the wheel you select, by asking Leadspin for its newest entries on a schedule. Zapier remembers what it has already seen, so the same player does not start the Zap twice.
When a Leadspin Zap breaks
Zapier attaches no help article to Leadspin and documents no limit of its own. What goes wrong is what goes wrong on any Zap, plus the delay of a polling trigger.
Most problems come from a Zap doing exactly what it was set up to do. Check these four cases first. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Leads arrive in batches, late
New Wheel Leads is a polling trigger: Zapier checks at your plan's interval, every 15 minutes on Free. Several players in between arrive together.Older leads never come through
A Zap only reacts to leads registered after you switch it on. Earlier players stay in Leadspin; moving them is a separate job.Leads from another wheel are missing
Each Zap watches the single Wheel picked in its required field. Players on any other wheel never reach that Zap.A big wave goes quiet
A trigger that suddenly returns a huge batch, after an import or a migration, can be held back by Zapier's flood protection.
Need help automating Leadspin with Zapier?
A person reads every message.
