Concepts
Integrations and API
Truffle connects natively to Ashby, Breezy HR, Bullhorn, JazzHR, Pinpoint, Recruitee, Teamtailor, Workable and Indeed. Zapier reaches 7,000+ more apps, and the REST API and webhooks cover the rest.
Checked against the live product 5 Oct 2026 Changelog Copy as Markdown
Truffle is the screening step. It runs next to the tools you already use for posting jobs and tracking candidates. There are four ways to connect it: a native connection to your applicant tracking system (ATS), an import address for job boards such as Indeed, a Zapier connection, or your own code on the REST API and webhooks.
Connecting an integration needs a paid Truffle plan. On a free account the Integrations page shows an upgrade banner instead.
The Integrations page
In Settings, open Integrations & API, then the Integrations tab.
- Connected lists the integrations your company has switched on. Each shows a health status (
Connected,DegradedorAction needed) and the date of its last activity. - Available lists the native integrations you can connect from inside Truffle, including Slack, Ashby and Pinpoint. They share one pattern to connect, manage and disconnect. Zapier is listed here too and opens its own setup page.
- Built in lists what works without an integration. That is email import, plus Airtable or Google Sheets through a ready-made Zapier recipe.
Native ATS connections
Every native ATS connection follows the same pattern. You choose a stage or trigger in your ATS. When a candidate reaches it, Truffle sends them the screening. When they finish, results such as the match score, the summary and a screening link write back to the candidate in your ATS.
Truffle’s scores never reject anyone. They rank candidates against your criteria and show why. You decide who moves forward or is disqualified, in your ATS.
Where you connect depends on the ATS. Some connect from Truffle’s Integrations page and some from the ATS’s own marketplace or integration settings. Each integration page has the exact steps. Most connections rely on the ATS’s API, which some ATSs keep on their paid plans, and each integration page names the plan.
| ATS | How a screening starts | What comes back |
|---|---|---|
| Ashby | Add Truffle as an activity on a stage of the job’s interview plan, then send the screening from the candidate’s Ashby profile | Interview match score and match level, questions asked and answered, a written summary, assessment score (High, Mid or Low), and a link to Truffle |
| Breezy HR | Move the candidate into the Breezy stage you chose as the trigger | Match score, summary and screening link |
| Bullhorn | The Bullhorn workflow step you choose, such as Screening or Pre-Submit | Match score, summary and screening link, in the fields you choose |
| JazzHR | A new application in JazzHR, or a workflow stage you choose | Match score, summary and screening link, in a custom field, tag or note |
| Pinpoint | Screen resume with Truffle or Send Truffle interview on the candidate | Resume match score and tier, interview score and tier, assessments as a tier, and a link to Truffle |
| Recruitee | Move the candidate to the Recruitee stage you mapped | Match score, summary and a Candidate Shorts link |
| Teamtailor | Move the candidate to the Teamtailor stage you mapped | Match score, summary and screening link |
| Workable | Move the candidate to the Workable stage you chose | Match score, summary, screening link and assessment results |
Ashby
Ashby connects through Ashby’s assessment partner API. Create an API key in Ashby with Truffle as the integration partner, then open Ashby on Truffle’s Integrations page and paste it in. Truffle generates a key of its own and shows it once. Paste that key into the Truffle integration in Ashby. Then add Truffle as an activity on each job’s interview plan and choose the Truffle position under Assessment Type.
When you send the screening from the candidate’s profile, Truffle emails the candidate their link and posts the status back as In progress once they start. Resume screening results do not post as a score in Ashby. Ashby gets the completed status and a View in Truffle link to the full breakdown. Cancelling the screening in Ashby disqualifies the candidate’s Truffle application.
If results stop arriving, Reconnect generates a new Truffle key to paste into Ashby.
Step by step: Connect Ashby.
Pinpoint
With Pinpoint, you run Truffle from inside Pinpoint. An owner or admin connects it from the Integrations page. Truffle creates a key and shows it once. You paste that key into the Truffle plugin’s configuration in Pinpoint.
The plugin adds two actions to a Pinpoint candidate:
Screen resume with Trufflescores the candidate’s resume against the position’s resume criteria. It does not contact the candidate. The resume must be a PDF or DOCX file of up to 5 MB.Send Truffle interviewsends the candidate Truffle’s interview invitation.
Each action only offers open Truffle positions that are set up for it. Closed, archived or expired positions refuse new sends. When scoring or the interview finishes, the result lands on the candidate’s Pinpoint record. If you replace the key, the old one keeps working for 7 days.
Step by step: Connect Pinpoint.
Indeed and email import
Each position has its own private import address. Turn on Auto-import applicants under Get candidates on the position, and copy the address it shows.
To connect Indeed, add that address to the job’s application method in Indeed and tick “Send an individual email each time someone applies”. Without that setting, Indeed sends summaries instead of individual applications and nothing imports. Truffle reads the candidate’s name, contact address and attached resume (PDF or DOCX) from each email and adds them to the position. Indeed gives a per-candidate relay address in place of the candidate’s own email, and Truffle accepts the relay as their address.
There is nothing to install and no Indeed login to hand over. Notifications from LinkedIn and ZipRecruiter are accepted the same way. If an email cannot be imported, it shows in the position’s import activity with the reason and what to do. What happens to an imported candidate follows how the position is set up, covered on Getting candidates in.
You can also point Indeed’s apply button at your Truffle application link, so candidates start screening as part of applying.
Zapier
Zapier connects Truffle to 7,000+ other apps without code. If your ATS has no native connection, Zapier or the REST API is how you connect it. Truffle offers two Zapier actions:
- Invite Candidate pushes a candidate from another tool, such as your ATS, into Truffle.
- Interview Completed triggers when a candidate finishes their interview.
To set it up, open Zapier from the Integrations page, choose Set up, then Create Zapier Key. Truffle shows the key once; paste it into Zapier when it asks you to connect your Truffle account. Step by step: Connect Zapier.
The REST API
The API gives you programmatic access to Truffle. Use it to invite candidates, create jobs, and pull jobs and screening data into your own systems. It is available on paid plans only.
You manage keys from the API keys tab under Integrations & API in Settings. Until Truffle approves your account for API access, the API keys and Webhooks tabs show Request API Access instead. Once access is approved, an owner or admin can create a key with a name and a description, regenerate it, or delete it. The key is shown once. Each key has one of three permission levels.
| Permission | What it allows |
|---|---|
| Read | View candidates, jobs, and screening results |
| Write | Create candidates, send invites, update records |
| Admin | Full access, including webhooks and settings |
Webhooks
Webhooks send your system a notification when an event happens in Truffle. Set them up from the Webhooks tab, next to API keys.
Two events are supported:
- Screening completed (
interview.completed) - Résumé scored (
application.resume_scored)
To create a webhook, give it a URL and a name, then select the events it should receive. You can edit it, send a test event, or delete it. There is no delivery history view in Truffle, so log deliveries on your own side.
Step by step: Create API keys and webhooks.
What it does not do
- Truffle’s scores never reject anyone. Native connections write results back, and you move or disqualify candidates in your ATS.
- An ATS without a native connection connects through Zapier or the REST API.
- Resume screening results do not post as a score in Ashby. Ashby gets the completed status and a link to the breakdown in Truffle.
- The Pinpoint plugin only sends to open positions set up for it, and it returns assessments as a tier, without a score.
- Indeed imports only work when Indeed sends an individual email for each application. Truffle never signs in to Indeed.
- Integrations, the API and Zapier need a paid Truffle plan. A free account cannot connect them.
- Webhooks cover two events: Screening completed and Résumé scored. Truffle does not show a delivery history.
- The API keys and Webhooks tabs open only after Truffle approves your request for API access.
Related
See something here that doesn't match what you see in Truffle? Tell us and we'll fix the page.