# PageUp integrations: applicants and applications

> Create an applicant, create an employee and create a position in PageUp. Connect PageUp to the rest of your human resources stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/pageup-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

PageUp is talent management software for recruiting, onboarding, performance reviews and learning, used by large employers to run hiring and HR processes. Tray.ai connects to PageUp through the HTTP Connector, so your workflows can call the PageUp API alongside the rest of your stack. API access comes through PageUp's partner program or API plan, so you need approved credentials first.

## Use cases

### Applicants

Read, create, and update applicants in PageUp from any Tray.ai workflow. The PageUp API covers calls such as create an applicant and find an applicant by email.

- Create an applicant
- Find an applicant by email
- Update an applicant

### Applications

Update applications in PageUp from any Tray.ai workflow. The PageUp API covers calls such as move an application status and set an application rank.

- Move an application status
- Set an application rank
- Set application flags

### Employees

Create, update, and delete employees in PageUp from any Tray.ai workflow. The PageUp API covers calls such as create an employee and update an employee.

- Create an employee
- Update an employee
- Archive an employee

### Positions

Create, update, and delete positions in PageUp from any Tray.ai workflow. The PageUp API covers calls such as create a position and update a position.

- Create a position
- Update a position
- Archive a position

## Challenges Tray.ai solves

### Keeping PageUp credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store PageUp credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the PageUp API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the PageUp API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to PageUp?

Yes. Tray.ai connects to PageUp through the HTTP Connector, which calls the PageUp API directly. Any call the PageUp API documents can run as a step in a Tray.ai workflow. API access comes through PageUp's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with PageUp?

The PageUp API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated PageUp connector?

PageUp runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated PageUp connector from the PageUp API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/