Recruiting & ATS · Integration
PageUp
Add PageUp to your product for your customers, and give your AI agents governed access to it.
Embed a PageUp integration so your product can work with the hiring pipeline a customer already runs rather than asking a recruiter to re-enter it. PageUp is enterprise talent acquisition, so the records that matter are job requisitions and their approval state, applications and applicants, offers, onboarding steps and the recruitment documents attached along the way. Candidate records are personal data with consent and retention rules attached, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. Each customer authorises their own PageUp account, so one employer's candidates never mix with another's. fastn owns the auth, token refresh, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own PageUp account so requisitions and applications are reachable inside your product with no per-customer code.
React when an application moves stage so screening, assessment or onboarding steps start without a manual handoff.
Upload and read recruitment documents per tenant so paperwork stays attached to the right application.
Support customers whose requisition approval chains and application workflows differ as configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports where each candidate sits in one employer's pipeline, limited to the fields you mapped.
An agent files a document or note against an application within scoped permissions, with the write audited.
An agent summarises how long requisitions have been open and where they are stalling.
Example prompt
Which requisitions have candidates waiting on interview scheduling, and how long have they been at that stage?
Set up PageUp in 4 steps
- 01Enable the PageUp connector in your fastn dashboard.
- 02Have each customer authorise their own PageUp account so calls run under their credentials.
- 03Map the requisition, application, applicant and document fields your product needs, and only those, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the PageUp integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PageUp integration without building it. Your customers connect their own PageUp 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 PageUp update is not your on-call problem.
- One integration serves your product and your agents. The same governed PageUp 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
GreenhouseWorks well with
Workday
BambooHROften used alongside
Tools the same teams tend to run next to PageUp, across other categories.
Slack
Notion
Box
DocusignPageUp integration FAQ
How do I add a PageUp integration to my product?
Enable the PageUp connector in your fastn dashboard, then let each customer authenticate their own PageUp account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PageUp client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PageUp account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PageUp 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 PageUp 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 each candidate sits in one employer's pipeline, limited to the fields you mapped.
Who maintains the PageUp integration?
fastn does. When PageUp 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 PageUp 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 PageUp?
Yes, through event triggers: a stage move where PageUp 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 PageUp integration?
A common starting point: let each customer connect their own PageUp account so requisitions and applications are reachable inside your product with no per-customer code. 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 PageUp integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PageUp does not change your per-connector cost. You can start free with 3 connected accounts.
Add PageUp to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.