Integrations · Zapier
QuikPitch for Zapier
Zapier connects QuikPitch to thousands of other apps with no code. It's the quickest way to get applicants into Greenhouse, Workable or Lever, tell a team in Slack, or log everything in a spreadsheet.
Get started
1. Make an API key
In your QuikPitch dashboard go to Integrations → API keys, make a key (name it something like “Zapier”) and copy it. It's shown once. If you ever need to cut Zapier off, revoke that key.
2. Accept the invite
Open the invitation we send, and accept it in Zapier. QuikPitch is then in your app list.
3. Make a Zap
- In Zapier choose Create → Zap.
- For the trigger pick QuikPitch, then one of the events below.
- When asked to connect, paste your API key. It should show your company's name.
- Click Test trigger: you'll see real applications from your account, with every field.
- Add what should happen next, then turn the Zap on.
Send applicants to your ATS
This works the same way for Greenhouse, Workable and Lever: a QuikPitch trigger, and your ATS's own “Create candidate” action. Native connections to each are on the way; until then this does the job, and you can set it up today.
The Zap
- Trigger: QuikPitch →
New Applicationto send everyone, orApplication Shortlisted or Moved Backto send only the people you shortlist. For a busy job the second keeps your ATS free of candidates you never wanted there: add a Filter step that continues only ifStatusisshortlisted. - Action: choose Greenhouse, Workable or Lever and its “Create candidate” (the name differs a little in each).
- Match the fields as below, test it, and turn it on.
| In your ATS | Use from QuikPitch |
|---|---|
| Name | Candidate Name |
| Candidate Email (only set if they shared it) | |
| Job | Match to your ATS job using Job Title |
| Source | “QuikPitch” |
| Notes | Link to Application in QuikPitch: this is how your team watches the video |
Moving people from the ATS side
It works the other way too. Use your ATS (or any app) as the trigger and QuikPitch → Shortlist an Application as the action, passing it the application's ID, which you can keep in the candidate's notes. Rejecting someone and inviting them to interview each send the candidate a personal message, so those stay in QuikPitch.
- Start a new Zap. For the trigger, use your ATS, or
Webhooks by Zapier → Catch Hookif you're sending from your own system. - Add
QuikPitch → Shortlist an Applicationas the action and connect your QuikPitch account. - In the
Applicationfield, open the options (⋮) and switch from the list toCustom(some accounts call itDynamic). The list is only a picker of recent applications; Custom lets the Zap use the ID it was sent. - Click the field and pick the application ID from the trigger's data. Leave
Move Toas Shortlisted. - Test the step (it really does move that application), then publish the Zap.
What it can do
Triggers: what starts a Zap
| New Application | Someone applies for one of your jobs. |
| Application Shortlisted or Moved Back | An application is shortlisted, or moved back to new. |
| Application Rejected | You reject an application. |
| Interview Confirmed | An interview time is agreed: the candidate picks one, or you confirm one they suggested. |
| Interview Declined | A candidate declines an interview. |
Triggers arrive within seconds and nothing polls, so there's no delay and no wasted runs.
Action
| Shortlist an Application | Shortlists an application, or moves it back to new. |
Search
| Find Application | Looks one up by its ID, with its full details. |
The fields you can use
| Application ID | Identifies the application (use it with the Shortlist action). |
| Job Title, Job ID | The job it's for. |
| Status | new, shortlisted, interview or rejected (and Previous Status, when it moved). |
| Link to Application in QuikPitch | Opens it in your dashboard, for anyone on your team signed in. |
| Candidate Name | Their name. |
| Candidate Email | Only if they applied without an account, or ticked “share my email” on their application. |
| Candidate Phone | Only for people who applied without an account. |
| Candidate Current Job Title, Location | From their application. |
| Candidate Profile URL, Username | For QuikPitch members. |
| Source, Applied At, Updated At, First Viewed At | Where and when. |
| Interview fields | On the two interview triggers: type, link or address, length, the confirmed time (as text, and as a universal date-time for calendars) and its timezone. |
Good to know
- Candidates' contact details. QuikPitch members' emails and phone numbers stay private unless they choose to share their email on an application. People who apply on your own website without an account give theirs to apply, so you always have it.
- The link opens in QuikPitch. Anyone on your team who is signed in can use it. Add your hiring managers as team members (a Viewer seat can watch the videos).
- Your Zapier plan decides which other apps you can use. QuikPitch doesn't charge for the connection, but some apps in Zapier (some ATS connectors, and Webhooks) are marked Premium and need a paid Zapier plan. Check the tag when you pick the app.
- Each Zap subscribes by itself when you turn it on and unsubscribes when you turn it off. You can have up to 100 on the go.
- Prefer to build it yourself? Everything the Zapier app uses is in the API and webhooks.
If something stops working
Zapier shows the step that failed in Zap History. The usual causes:
- “QuikPitch didn't accept your API key”. The key was revoked or mistyped. Make a new one under Integrations → API keys and reconnect.
- Your ATS step fails. Its login has expired (reconnect it in Zapier), or it needs a field QuikPitch didn't send, like an email.
- “Can't be moved this way”. An application that's been rejected, or is at the interview stage, can't be shortlisted from a Zap.
- Nothing happens at all. Check the Zap is on, and that the QuikPitch subscription is active: connections pause with the account.
Still stuck? Email hello@quikpitch.co.

