Linq Zapier integrationAutomate Linq with Zapier.
The Linq Zapier integration gives you 1 trigger, 0 actions and 0 searches. One door out, then: every contact your digital business card collects can leave Linq and land in the tool where you actually follow up, without copying it by hand.
Verified Trustpilot reviews · AI, automation & growth agency
What the Linq Zapier integration actually does
Linq is a digital business card: people open your no-code profile and leave their details. Connected to Zapier, it does one thing. Each time a new contact is created in your Linq account, Zapier picks it up and hands it to the next step of your automation, in whatever other app you chose.
One trigger sounds thin, and it is. It still covers the job most people want from a business card: getting the leads out. Three results come back again and again, all built on New Contact Created.
A running log of every lead. Each new contact becomes a row in a spreadsheet, so you finally have one list to sort, share and clean, instead of scrolling through the Linq app.
A ping you cannot miss. The same trigger can feed a message to your inbox or your team chat, so a fresh lead is seen while the conversation is still warm in your memory.
A record in the tool you sell from. Pass the contact to your CRM or contact list and the follow-up starts where the rest of your pipeline already lives.
Now the honest part. Zapier does not write anything into Linq: there is no action, so you cannot create, edit or delete a Linq contact from a Zap. There is no search either, so a Zap cannot look up an existing Linq contact. And a Zap never goes back in time: contacts collected before you switch it on stay where they are.
If you are still weighing tools, the n8n vs Zapier comparison is the next read.
The Zapier words you will meet on this page
Zapier has its own vocabulary. Here it is in plain words, once, so the rest of the page reads without a dictionary.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Here it is a new Linq contact; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, in another app since Linq has none.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant one is reported by the app itself the moment it happens. Linq's is polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app so later steps can use it. Linq offers none on Zapier.
- Connection
- Your Linq account linked to Zapier once, then reused by every step and every Zap that uses Linq.
What a Linq Zap really costs you
Linq is not a premium app, so it works from the free plan. The bill depends on what happens after the trigger, never on the trigger itself.
- Premium appNo, available on the free plan
- Tasks on the free plan100 per month
- Zaps on the free planUnlimited, two steps each
- Cost of the triggerZero tasks
Spotting a new Linq contact costs nothing, however often Zapier checks. You pay one task each time an action in the next app goes through; an action that fails is not counted. Add a second action and each contact costs two. The free plan stops at two steps, one trigger and one action, so a filter or an extra step makes it a multi-step Zap that needs a paid plan. The grid below is how long a new contact can wait before Zapier sees it.
Connect your Linq account in three moves
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box; type Linq and pick it from the list. You need an existing Linq account before you start.
- 02
Sign in to Linq
Click Add connection. A new tab opens on Linq: sign in with the account whose contacts you want to send out. Pick the right one if you run several, since every Zap reuses this connection.
- 03
Grant Zapier access
Accept the access request in that tab. The tab closes and Linq now sits on your Apps page as a connection, ready to be chosen as the trigger app in any new Zap you build.
Your first Zap: every Linq lead in a spreadsheet
GoalLog each new Linq contact as a row in a spreadsheet, and only keep the ones that match a condition you choose.
- 01
Start the build
Create a Zap and pick Linq as the trigger app, then New Contact Created as the event. Choose the Linq connection you added earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts of your Linq account, so you map the next steps on a real lead instead of a blank one.
- 03
Add the filter
Click the plus icon and add Filter. Set the field to look at, the rule and the value. Pick a text rule for text: a mismatched rule is why a filter never passes.
- 04
Add the spreadsheet action
Add your spreadsheet app as the action, choose the step that creates a row, then map each column to a value from the Linq contact. Test that step and read what came back.
- 05
Publish
Click Publish to switch the Zap on. With the filter it is a multi-step Zap, so it needs a paid plan; on the free plan, drop the filter and keep two steps.
The Linq trigger
1 event starts a Zap when something happens in Linq. Zapier checks for them at the interval your plan allows.
New Contact Created
Polling triggerIn Zapier“Triggers when a new contact is created.”
Starts your Zap whenever someone new is added to the contacts of your Linq account, and passes that contact to the steps you placed after it. It is the only way out of Linq on Zapier, so every Linq Zap begins here.
When a Linq Zap breaks, or seems to
Zapier attaches no help article of its own to Linq. What goes wrong here comes from how Zapier treats every polling trigger.
Most surprises are not errors at all. The Zap is doing exactly what Zapier promises, just not what you assumed. If a run really fails, the Zapier troubleshooting page is the place to go next.
Old contacts never show up
A Zap only reacts to contacts created after it is switched on. Nothing already stored in Linq is picked up; moving that backlog is a separate job.A new lead seems late
Linq's trigger is polling, so a contact waits for the next check. On the free plan that means up to 15 minutes before the Zap starts.A big batch arrives and stalls
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those runs back.The same contact does not run twice
Zapier remembers what it has already seen on a polling trigger, so one contact starts the Zap once. A missing duplicate is the design, not a bug.
Need help automating Linq with Zapier?
A person reads every message.
