Piloterr Zapier integrationAutomate Piloterr with Zapier.
The Piloterr Zapier integration gives you 0 triggers, 1 action and 4 searches. Piloterr never starts a Zap on its own: another app does, and Piloterr fills in the blanks with LinkedIn profiles, company records and website details along the way.
Verified Trustpilot reviews · AI, automation & growth agency
What the Piloterr Zapier integration is good for
Piloterr is a web data service with more than 50 ready-made data sources. On Zapier, it acts as an enrichment step: another tool hands over a LinkedIn link, a domain or a web address, and Piloterr sends back what it knows about that person, company or site, so the rest of your automation can use it.
Three useful results, each tied to a real operation:
Contacts that arrive with their profile. A lead lands in your CRM with a LinkedIn link, and Get LinkedIn Profile brings back the profile details so your sales team stops copying them by hand.
Company records from a simple domain. Get Company Database takes a domain such as the one in a sign-up email and returns company data, while Get LinkedIn Company does the same from a company page link.
A view of the prospect's website. Get Website Technology tells you which site builder, analytics or hosting a site relies on, and Get Website Crawler fetches the raw content of a page for a later step to read.
What Zapier does not do here: Piloterr has no trigger, so it can never be the event that starts a Zap (the word is explained below). Four of its five operations are searches, which makes any Zap that uses them multi-step, and it only reads data: nothing is written back to Piloterr.
If you are still choosing a platform, the n8n vs Zapier comparison is worth a look.
Zapier vocabulary, one line each
A handful of Zapier words carry the whole page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Piloterr has none, so the trigger always comes from another tool, like your CRM.
- Action
- What the Zap does after it starts: the step that fetches, writes or sends something for you, such as a LinkedIn profile.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan allowance is a count of those.
- Search step
- A step that looks up something that already exists, like a company behind a domain, so the steps after it can use the result.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Piloterr account linked to Zapier once, then reused by every step of every Zap that calls Piloterr.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A search, a filter or a second action makes one, and it needs a paid plan.
What Piloterr on Zapier will cost you
Piloterr is not a premium app, so it is available on the free plan. Whether a given Zap stays free depends on which Piloterr operation you put in it.
- Trigger from your other app0 tasks
- Successful Get LinkedIn Profile1 task
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- Any Piloterr search in the ZapMulti-step, paid plan
The trigger from your other app never costs a task. Get LinkedIn Profile is an action, so each successful run counts as one task, and a failed one does not. The free plan allows two-step Zaps: one trigger and one action, so a trigger plus Get LinkedIn Profile fits. The four Piloterr searches are another story: any Zap containing a search step is multi-step, and multi-step Zaps need a paid plan. The interval grid below only matters if the app that starts your Zap uses a polling trigger.
Connect your Piloterr account to Zapier
- 01
Open the Apps page
In Zapier, open Apps and click + Add connection. You need a Piloterr account that already exists; Zapier links an account, it never opens one on your behalf.
- 02
Pick Piloterr
Type Piloterr in the dialog's search box, select it and click Add connection. A new tab opens where Piloterr asks you to sign in with that same account.
- 03
Sign in and grant access
Sign in to Piloterr in that tab and allow Zapier to use the account. The connection then serves every Piloterr step you add, in this Zap and in the next ones.
Your first Piloterr Zap
GoalWhen a new sign-up arrives through your form tool, look up the company behind its email domain and update your CRM with it.
- 01
Pick a trigger in another app
Create a Zap and choose your form tool with its new-entry event. Piloterr has no trigger, so the Zap always starts from an app like this one.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from that account, so you map the next steps on a real sign-up rather than an empty one.
- 03
Add Get Company Database
Add Piloterr and pick Get Company Database, which sits in the search part of the list. Map the domain from the sign-up into Domain Name. This search makes the Zap multi-step, so it needs a paid plan.
- 04
Add the CRM step
Add your CRM and its update action, then map what Piloterr found into the matching fields. Run the step once and check the result in the CRM.
- 05
Publish
When every step has been tested, click Publish to switch the Zap on. Only sign-ups that arrive from then on get enriched; older ones stay as they are.
Piloterr actions on Zapier
Piloterr gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Get LinkedIn Profile
ActionIn Zapier“Get profile information from a LinkedIn URL.”
Give Piloterr a LinkedIn profile link or username and it returns the information on that profile for the next steps to use. It is the only Piloterr operation that counts as an action, so it works in a two-step Zap on the free plan.
Piloterr searches on Zapier
4 search steps look for data that already exists in Piloterr, so a later step can use it.
Four of Piloterr's operations are search steps: they look up a company or a website and hand the result to the steps that follow. In the editor they sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when a search does not return exactly one result.
Get Company Database
SearchIn Zapier“Get data about a company with a domain name.”
Hand it a domain name and Piloterr returns data about the company that owns it. The domain can come with or without the www part.
Get LinkedIn Company
SearchIn Zapier“Get company information from a LinkedIn URL.”
From a LinkedIn company page link or username, this search pulls the company information shown on LinkedIn.
Get Website Crawler
SearchIn Zapier“High performance API for web scraping to scrape any website and get the HTML.”
Fetches a web page and returns its raw content, so a later step can read, store or analyse it.
Get Website Technology
SearchIn Zapier“Get the website technology from a website : cms, framework, analytics, cdn, hosting, etc.”
Looks at a website and reports the technology behind it: content management system, framework, analytics, content delivery and hosting.
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 the steps that relied on it are skipped. Turned on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns a search into a find-or-create. Piloterr offers no such variant, since its searches only read data and create nothing.
- If multiple search results are found?Three ways out when several results match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a Piloterr Zap breaks
Zapier attaches no help article and no documented limit to Piloterr. What breaks comes from Zapier's general rules and from the inputs each operation requires.
Four cases come back most. Most of them show no clear error, which is why they are worth knowing before you publish. The Zapier troubleshooting page covers the rest.
Old records are never enriched
A Zap only reacts to what happens after it is switched on. Leads already in your CRM are not sent through Piloterr, and enriching that backlog is a separate job.The Zap rewrites what started it
If the CRM update at the end changes the very record your trigger watches, the Zap can set itself off again and again and burn through tasks.A big import gets held back
Importing a long lead list at once can make the trigger return a huge batch, and Zapier's flood protection may hold it back instead of running every lookup.A search that finds nothing stops the Zap
With the default setting, a Piloterr search that returns nothing ends the run and skips the CRM update. Switch on the no-results setting if the Zap should carry on.
Need help automating Piloterr with Zapier?
A person reads every message.
