Recruiting & ATS · Integration
TazWorks
Add TazWorks to your product for your customers, and give your AI agents governed access to it.
TazWorks is the platform background screening companies run on, so the account your product connects usually belongs to a consumer reporting agency rather than to the employer who wanted the check, and that shapes everything. A screening account defines its own packages, and which searches a package includes is that agency's commercial decision, so what your product can order is per-tenant configuration and never a fixed list. Reports come back over time rather than all at once, since a county court search can take days while an instant database hit returns immediately, which means status is something your product follows rather than reads once. This is consumer report data with regulatory obligations attached, so the connection is narrowed to the fields you chose, held encrypted per tenant, and audited on every call.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each screening account connect their own TazWorks credentials, so orders are placed under the agency that holds the relationship.
Read the packages that account offers, since which searches are included differs per agency.
Order a check for an applicant from your product and follow its status as individual searches complete.
React when a report finishes or its status changes, rather than polling a report that may take days.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports where an applicant's check stands and which searches are still outstanding.
An agent orders a check within scoped permissions, with the package and the requester recorded.
An agent flags reports that have sat incomplete beyond the expected turnaround.
Example prompt
Which background checks in this account have been pending more than five days, and which search is holding each up?
Set up TazWorks in 4 steps
- 01Enable the TazWorks connector in your fastn dashboard.
- 02Have each screening account connect their own credentials with least-privilege access.
- 03Map the applicant, package and report fields your product uses, and confirm which searches that account may order.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the TazWorks integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TazWorks integration without building it. Your customers connect their own TazWorks account inside your product and work their job requisitions, candidates and applications there, with no per-customer code on your side.
- Handle the part that actually costs time: candidate records are personal data with consent and retention rules attached. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a TazWorks update is not your on-call problem.
- One integration serves your product and your agents. The same governed TazWorks connection powers in-product features and gives AI agents scoped, audited access, so you keep hiring pipelines moving without manual re-entry without wiring it twice.
Used by these teams
Compare with
Checkr
Greenhouse
JobviteOften used alongside
Tools the same teams tend to run next to TazWorks, across other categories.
Slack
Notion
Box
DocusignTazWorks integration FAQ
How do I add a TazWorks integration to my product?
Enable the TazWorks connector in your fastn dashboard, then let each customer authenticate their own TazWorks account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TazWorks client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TazWorks account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TazWorks account and only ever sees their own job requisitions, candidates and applications. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this TazWorks integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports where an applicant's check stands and which searches are still outstanding.
Who maintains the TazWorks integration?
fastn does. When TazWorks changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is candidate data from TazWorks handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. That matters more here than in most systems, because candidate records are personal data that carry consent and retention obligations.
Can my product react when a candidate's status changes in TazWorks?
Yes, through event triggers: a stage move where TazWorks owns the pipeline, or a completed assessment, a returned report or a finished reference where it owns one step in it. Events are delivered per tenant and can be replayed after an outage, so a hiring team does not silently lose an update while your product was unreachable.
What can I build with the TazWorks integration?
A common starting point: let each screening account connect their own TazWorks credentials, so orders are placed under the agency that holds the relationship. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the TazWorks integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TazWorks does not change your per-connector cost. You can start free with 3 connected accounts.
Add TazWorks to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.