LinkupAPI Zapier integrationAutomate LinkupAPI with Zapier.
The LinkupAPI Zapier integration has 0 triggers, 3 actions and 4 searches. Another app starts the Zap, then LinkupAPI fills in a person's profile or a company's details, or finds companies and profiles that match your keywords. The free plan accepts it.
Verified Trustpilot reviews · AI, automation & growth agency
What the LinkupAPI Zapier integration does for you
The LinkupAPI Zapier integration connects LinkupAPI, a service that feeds live web data and B2B prospecting channels to AI tools, to the rest of your apps. It runs inside a Zap: an automation on Zapier made of one trigger, then one or more actions that run every time the trigger event happens. LinkupAPI only brings actions and searches; the trigger comes from another app.
A company card built from a web address. Someone fills in a form with their work domain, and Get Company Information by Domain returns what LinkupAPI knows about that company, ready for a spreadsheet row. A profile completed from three fields. Enrich Profile takes a first name, a last name and a company name and locates the matching professional profile. A list of targets on demand. Search Funded Companies or Search Hiring Companies return companies that match your keywords, so the next steps can file them wherever your team works.
Here is what Zapier does not do with LinkupAPI. There is no trigger: nothing on the LinkupAPI side starts a Zap, so you always begin with an event elsewhere, such as a new form entry, a new row or a new contact. Nothing gets written into LinkupAPI either; it reads and returns. And some options cost extra LinkupAPI credits, on top of Zapier tasks. LinkupAPI has no dedicated n8n or Make page on this site yet; to weigh the tools, read the n8n vs Zapier comparison.
Zapier vocabulary in one minute
Eight words come back on every line of this page. Here they are in plain English, once.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant one is reported by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists, so the steps after it can reuse what it found.
- Connection
- Your app account linked to Zapier once, then reused by every step of every Zap that touches that app.
What a LinkupAPI Zap really costs
LinkupAPI is not a premium app, so it works from the free plan. You pay Zapier in tasks, and the trigger, from whichever app, costs nothing.
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- TriggerFrom another app, never billed
- LinkupAPI actionsOne task each time one succeeds
- SearchesMake the Zap multi-step, so a paid plan
Each LinkupAPI action that succeeds counts one task, and a failed one counts nothing. The free plan gives you 100 tasks a month and Zaps of two steps: a trigger plus one LinkupAPI action. Any of the four searches, a filter or a second action makes the Zap multi-step, which needs a paid plan. LinkupAPI also bills its own credits for some options. Since LinkupAPI has no trigger, the grid below only matters if the app that starts your Zap uses a polling trigger.
Connect your LinkupAPI account in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need a LinkupAPI account first, plus access to anything you do not own and want the Zap to touch.
- 02
Pick LinkupAPI
Type LinkupAPI in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the LinkupAPI side for the sign-in.
- 03
Sign in and allow access
Log in to LinkupAPI in that tab and grant Zapier access to the account. The connection is then offered in every step that uses LinkupAPI, in this Zap and the next ones.
Your first Zap: form domains turned into company rows
GoalEach form entry with a work domain becomes a spreadsheet row holding the company details LinkupAPI returned.
- 01
Start from the form
Create a new Zap and pick your form tool and its new-submission event as the trigger. Testing it brings back the three most recent entries, so you map on a real domain.
- 02
Ask LinkupAPI
Add LinkupAPI as the action app and choose Get Company Information by Domain. Map the domain field of the form into Company Domain, the one value the action requires.
- 03
Write the row
Add your spreadsheet as a second action with its new-row event, and map the company details LinkupAPI returned into your columns. Two actions mean a paid plan.
- 04
Test, then publish
Run each step once and read what came back before going further. If the row looks right, click Publish to switch the Zap on for every new entry.
The three LinkupAPI actions
LinkupAPI gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Enrich Profile
ActionIn Zapier“Finds and extracts comprehensive profile information using name and company to automatically locate the professional profile.”
Finds the professional profile of a person from their first name, last name and current company, then returns the details it extracted.
Get Company Information
ActionIn Zapier“Extracts detailed information about a specific company from their company page URL.”
Reads a company page from its URL and returns the detailed information found there.
Get Company Information by Domain
ActionIn Zapier“Searches and extracts company information using a domain name.”
Starts from a domain name and looks up the company behind it, then extracts its information.
The four LinkupAPI searches
4 search steps look for data that already exists in LinkupAPI, so a later step can use it.
A search step looks things up and hands what it found to the next steps. In the editor, LinkupAPI's searches sit at the bottom of the action list, under the SEARCH heading. Each one makes the Zap multi-step.
Search Companies
SearchIn Zapier“Searches for companies using various filters like industry, location, and employee range.”
Looks for companies from a keyword, with filters such as industry, location and employee range.
Search Funded Companies
SearchIn Zapier“Searches specifically for funded companies with detailed funding information.”
Narrows the search to companies that have raised money, and returns their funding details along with them.
Search Hiring Companies
SearchIn Zapier“Finds companies actively hiring by scraping job boards with optional company enrichment.”
Finds companies that are recruiting right now by reading job boards, with company details as an option.
Search Profiles
SearchIn Zapier“Searches professional profiles using multiple criteria like job title, industry, school, and location.”
Searches professional profiles from a main keyword, which can be a name, a role or a skill, and criteria like industry, school or location.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. LinkupAPI offers no such variant, so none of its four searches creates anything.
- If multiple search results are found?Three ways out when several results match: keep the first, which is the default, stop the Zap, or pass all of them on at once.
When a LinkupAPI Zap breaks
Zapier attaches no help article to LinkupAPI, so the cases below are the general limits that hit any Zap built around it.
None of them throws an error on day one. They show up later as a company that never got its row, or a counter of tasks and credits climbing too fast. When a run looks wrong, start with the Zapier troubleshooting page.
Old records stay unenriched
A Zap only reacts to what happens after you switch it on. Contacts and companies already in your tools are never picked up; enriching them is a separate job.A sheet that feeds itself
Start on a new row and write each search result as a new row in the same sheet, and every result starts the Zap again, burning tasks and credits.A bulk import held back
If a huge batch of records lands at once, after a bulk import for example, Zapier's flood protection can hold the batch back.No record enriched twice
When the starting app uses a polling trigger, Zapier remembers what it has already seen, so the same entry does not run LinkupAPI twice.
Need help automating LinkupAPI with Zapier?
A person reads every message.
