- Home
- Resources
- Integrations
- LookBookLink
LookBookLink Zapier integrationAutomate LookBookLink with Zapier.
The LookBookLink Zapier integration gives you 1 trigger, 0 actions and 0 searches. It does one thing: each time your mobile portfolio collects a new lead, Zapier picks it up and hands it to the tool where you actually follow people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the LookBookLink Zapier integration does
LookBookLink is a portfolio you show from your phone, and it is also where visitors leave you their contact details. The Zapier integration lets a Zap (an automation you build once: a starting event in one app, then the steps that follow) catch every new lead it collects. Information flows out of LookBookLink only; nothing is written back into it.
Three results come out of the single trigger, New Lead. First, a lead list that grows without copy and paste: each contact your portfolio receives lands as a row in the spreadsheet you already work from. Second, a follow-up that starts on its own: the same lead can go into your email or CRM tool, so the person hears from you without you transferring anything by hand. Third, one place for all your sources: LookBookLink leads join the ones coming from your other channels, in the tool you check every day.
Now the limits. Zapier offers no action for this app, so no Zap can write into LookBookLink: you cannot update your portfolio or edit a lead from another tool. There is no search either, so a later step cannot look up an existing lead. And the trigger is a polling one: Zapier checks for new leads on a timer, so they do not arrive the second they are captured.
Before choosing, read our Zapier review and the comparison n8n vs Zapier. We have no dedicated n8n or Make page for this app yet.
Zapier words in one minute
Seven terms come back on this page. Here is each one in plain words.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap; once the Zap is on, Zapier waits for it. For LookBookLink, the only one is New Lead.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something. Here it always lives in another app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of exactly those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen yet.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. LookBookLink does not offer one, so its leads always wait for a check.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
What it really costs
LookBookLink is not a premium app, so it works on the free plan. You pay in tasks, and the trigger itself spends none.
- Tasks on the free plan100 per month
- Steps on the free plan2 (one trigger, one action)
- Premium appNo
- Cost of the trigger0 tasks
Catching a new lead costs nothing, and neither do the regular checks Zapier runs to find one. What counts is the action that follows: each successful step in your other app is one task. A failed action counts for nothing. The free plan gives 100 tasks a month and two-step Zaps only: New Lead, then one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Because New Lead is a polling trigger, the grid below sets how often Zapier looks for leads on each plan.
Connect your account in three steps
- 01
Find the app
In your Zapier account, open Apps and click + Add connection. Type LookBookLink in the search box of the dialog and pick it. You need a LookBookLink account first; Zapier only links it.
- 02
Sign in to LookBookLink
Click Add connection. A tab opens on the LookBookLink side: sign in with the account whose leads you want to collect. If the portfolio belongs to a teammate, make sure your login can read its leads.
- 03
Grant access
Allow Zapier to read the account. The connection then sits on your Apps page, and any Zap built on New Lead reuses it instead of asking you to sign in again.
Your first Zap: leads into a spreadsheet
GoalEvery new lead collected by your LookBookLink portfolio becomes a row in your spreadsheet, but only when the lead carries the detail you need to follow up.
- 01
Pick the trigger
Create a Zap, choose LookBookLink as the trigger app and New Lead as the event. Select the connection you set up earlier. Every run starts from here.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent leads of the connected account, so you can pick a real one and map from actual data.
- 03
Add a filter
Click the plus icon and add Filter. Fill the three boxes: the field to look at, the rule, and the value to compare with. Incomplete leads stop here. The Zap is now multi-step.
- 04
Add the spreadsheet step
Add an action in your spreadsheet tool, with its add-row event. Map each lead field into the column you want, one by one, and check the sheet you point at.
- 05
Test, then publish
Test the action and open the sheet to check that the row arrived. When it looks right, click Publish to switch the Zap on.
The LookBookLink trigger
1 event starts a Zap when something happens in LookBookLink. Zapier checks for them at the interval your plan allows.
New Lead
Polling triggerIn Zapier“Triggers when a new lead is received.”
Starts your Zap each time your LookBookLink portfolio receives a new lead, and hands that person's details to the steps that follow, so they can be filed, emailed or added to a list somewhere else.
When it breaks
Zapier ties no help article to this app. The risks below are the general ones that hit any Zap, seen from a single polling trigger.
Most surprises here come from timing and from what Zapier remembers, not from LookBookLink itself. When a run fails, see our Zapier troubleshooting page.
Old leads never come across
A Zap only reacts to what happens after you switch it on. Leads collected before stay in LookBookLink; moving that backlog is a separate job.A surge of leads gets held back
If LookBookLink suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold that batch instead of running it.The same lead will not fire twice
On a polling trigger Zapier remembers what it has already seen. That blocks duplicates, but a lead you edit later will not start the Zap again.Leads arrive in waves, not one by one
New Lead is checked on a timer set by your plan. Between two checks, new leads wait, so several can show up together on the next pass.
Need help automating LookBookLink with Zapier?
A person reads every message.



