Pinpoint Zapier integrationAutomate Pinpoint with Zapier.
The Pinpoint Zapier integration, in plain words. Pinpoint gives Zapier 4 triggers, 0 actions and 0 searches: it tells other apps what happens in your hiring. Here is what each trigger catches, how often, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pinpoint Zapier integration actually does
The integration plugs Pinpoint, the recruiting software that in-house talent teams use to run their hiring, into Zapier, which chains apps together without code. It works in one direction: events in Pinpoint, a new job, a new applicant, a stage change, start work in the other tools your company already uses.
Three results, each tied to a real trigger. First, a hiring team that hears about applicants without logging in: New Application starts a Zap (the automation you build in Zapier) for each application submitted, so the next step can post it in a team chat or add it to a sheet. Second, the rest of the company kept in step with the process: Application Stage Update catches a candidate moving from one stage to another, which is the moment to warn a hiring manager or prepare onboarding. Third, openings and talent pools shared beyond HR: New Job and New Talent Pipeline Candidate let other tools know when a role opens or someone joins the pool.
Now what it does not do. Pinpoint has no action on Zapier: no Zap can create a candidate, move an application or post a job in Pinpoint. There is no search either, so a Zap cannot look up a candidate or a job that already exists. And all four triggers are polling ones, checked on a timer rather than reported instantly. Data flows out of Pinpoint, never back in.
Weighing tools before you build? There are side-by-side pages for Make vs Zapier and n8n vs Zapier.
Zapier vocabulary in one minute
Eight words come back on every Zapier screen. Here they are in plain terms, with recruiting as the example.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new application in Pinpoint. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started. Pinpoint has none on Zapier, so actions always happen in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and the count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only what it has not seen before. All four Pinpoint triggers work this way.
- Instant trigger
- A trigger the app reports itself the moment the event happens. Pinpoint offers none, which is why timing depends on your plan.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a Pinpoint Zap costs in tasks
Pinpoint is not a premium app on Zapier, so it works on the free plan. Because Pinpoint only offers triggers, it never costs a task by itself.
- Any Pinpoint trigger0 tasks
- Each successful action in another app1 task
- Free plan100 tasks a month, two-step Zaps only
- Paid plan required for PinpointNo
Watching Pinpoint is free, however often Zapier checks. What counts is each action in the other app that succeeds: one message posted, one row added. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps, one trigger and one action, and it checks every 15 minutes. A filter, say to keep only one job's applicants, or a second action turns the Zap multi-step and calls for a paid plan, which also checks more often.
Connect your Pinpoint account
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. In the dialog, type Pinpoint in the search box and pick it from the list of results.
- 02
Sign in to Pinpoint
Click Add connection. Pinpoint opens in a new tab: sign in with the account your recruiting team works in. Without a Pinpoint account of your own, the connection cannot be made.
- 03
Grant access
Approve the access Zapier asks for. If the Zap has to read jobs or applications you do not own yourself, check first that your user has read rights on them. Every Pinpoint trigger then reuses this connection.
Your first Pinpoint Zap, step by step
GoalWhen a new application arrives in Pinpoint and meets your condition, post a message about it in the hiring team's chat.
- 01
Pick the trigger
Build a new Zap, choose Pinpoint as the app that starts it and New Application as the event, then select your Pinpoint connection.
- 02
Test on real data
Run the test. Zapier brings back the three most recent items from your Pinpoint account, so you map the rest of the Zap from a real application rather than a guess.
- 03
Add the filter
Add a Filter step and set the field to look at, the rule and the value, so only the applications that concern this team go through. The Zap is now multi-step: paid plan.
- 04
Add the chat message
Add the action of your team chat that posts a message, choose the channel and build the text from what the Pinpoint test brought back.
- 05
Test, then publish
Test the message step and read what came back. If it looks right, click Publish to switch the Zap on. It then checks Pinpoint at the interval of your plan.
Pinpoint triggers
4 events start a Zap when something happens in Pinpoint. Zapier checks for them at the interval your plan allows.
Application Stage Update
Polling triggerIn Zapier“Triggers when a job application is moved from one stage to another.”
Catches the moment an application moves from one stage of your hiring process to another, and passes that application on to the next steps of the Zap.
New Application
Polling triggerIn Zapier“Triggers when a new job application is submitted in Pinpoint.”
Every job application submitted in Pinpoint becomes the start of a Zap, with the application handed to the steps that follow.
New Job
Polling triggerIn Zapier“Triggers when a new job is created in Pinpoint.”
Reacts to the creation of a job in Pinpoint, which makes it the natural starting point for anything that should happen when a role opens.
New Talent Pipeline Candidate
Polling triggerIn Zapier“Triggers when a new candidate applies to, or is added to, the talent pipeline.”
Fires when someone joins your talent pipeline, either because they applied to it themselves or because your team added them.
When a Pinpoint Zap breaks
Zapier attaches no help article to Pinpoint, and no limit specific to the app is documented. What breaks is what can break on any Zap built on polling triggers.
Four cases to know before you publish. None of them shows up as an obvious error on the first test, which is why they deserve a read now. For a step-by-step way to debug a Zap, see Zapier troubleshooting.
No backlog
A Zap only reacts to what happens after it is switched on. Jobs and applications created earlier are never picked up; moving them is a separate job.A flood held back
After a bulk import of candidates or a migration, a trigger that suddenly returns a huge batch can be held back by the flood protection Zapier applies.Seen once, sent once
On a polling trigger Zapier remembers what it has already seen, so the same item does not start the Zap twice, even if it shows up again in a later check.A filter that never passes
Filter rules are typed: a text rule only works on text, a number rule only on numbers. Pick the wrong type and the filter blocks every application.
Need help automating Pinpoint with Zapier?
A person reads every message.
