Start free
Read & reportControlled changes

See your Ashby numbers in Cloudflare R2.

Track job openings, applicant flow, and candidate progression with candidate tag updates.

  • A weekly status report that builds itself from Ashby
  • Overdue and unassigned work in a sheet every morning
  • Ask an AI assistant what slipped this week, using live Ashby data
AshbyCloudflare R2Cloudflare R2

Start free Connect Ashby

Updated November 2026

Ashby reportSample data
NameEmailPrimary role
Avery Chenavery@northwind.example1,240
Jordan Blakejordan@harbor.example640
Sam Okonkwosam@acme.example210
Refreshes on your schedule in Cloudflare R2

Who uses Datapipe with Ashby

Agency account managers

Send each client a status report from their own project, on a schedule.

Operations leads

See overdue and unassigned work across projects without exporting CSVs.

Founders and team leads

Get a weekly answer to "what moved, what slipped" in a sheet or in ChatGPT.

What you can do with Ashby

Read and report

Read published job requisitions, candidate profiles, and application stages using your Ashby API key.

  • Job openings
  • Candidate pipeline
  • Job applications

Explore metrics and dimensions

Controlled changes

  • Update candidate tags

Changes stay off until you allow them. Allowed changes apply to Ashby right away, and history keeps the values before and after.

See what you can change

Full read details

Interview stages and application statuses remain explicit.

Examples for your team

Read & report

Review candidate pipeline and application stages

Refresh active applicant submissions, target roles, and interview progression stages across open requisitions without manual exports.

  1. Scheduled refresh
  2. Latest Ashby data
  3. Updated report
Controlled change

Update a candidate tag before review

A teammate adds or removes a priority candidate tag on an applicant profile.

  1. Allowed
  2. Applied
  3. Recorded

Limit: History records the candidate ID and tag name.

Fix things in Ashby without opening it

Spot it, fix it

See the problem in your report, then make the fix in Datapipe instead of opening Ashby, finding the record and retyping it.

More people can help

Teammates and AI tools you allow can make changes without getting edit access to Ashby.

You decide what can change

Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.

Jobs you can stop doing by hand in Ashby

Update candidate tags

  • Add priority referral tag to candidate profile to expedite interviews

    TodayLog in to Ashby recruiting console, search candidate name, open candidate profile, click Add Tag, and select tag.

    With DatapipeNotice an executive referral applicant in the pipeline report and add the Executive Referral tag.

  • Remove obsolete screening tags following successful technical panel

    TodayOpen candidate record in Ashby, locate tag badge, click remove, and confirm.

    With DatapipeSpot outdated stage tags in your recruiting pipeline report and remove the stale tag.

Exactly what this can change

Adds or removes a tag on an existing candidate profile in Ashby. Candidate resume, applications, and interview records remain untouched. Every change is recorded in the Changes history.

Supported fields: Candidate tag, Action.

Recorded changeExample

AshbyUpdate candidate tagsCandidate · Alex Rivera (Staff Infrastructure Engineer) · made by Head of Talent

FieldBeforeAfter
TagsEngineeringEngineering, Executive Referral

Applied to AshbyRecorded in Changes history

You control who can change what

  1. A change is allowed for this data source
  2. A teammate or AI tool makes it
  3. It applies right away, or waits for approval if you set that
  4. Recorded with the values before and after

Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?

Provider rules and limits

Provider permissions still apply, and automations in Ashby may react to changes.

Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.

Before you connect

What you need

An API key or token from your Ashby account.

Read and write

Read access for reports. The change action needs edit access in Ashby and stays off until the owner, an admin or a project manager allows it.

Limits and exclusions

Anything your connected account cannot see in Ashby.

Full details and limits

Job requisitions, candidate profiles, and application progression records from your Ashby hiring workspace.

Reporting reads requisitions, candidates, and applications. Optional candidate tag additions and removals are off until allowed for this data source, and every change is recorded in history. Interview notes and resumes cannot be altered.

Reports you can build

3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.

What each dataset reports
  • Job openings

    Published and draft job requisitions, not filtered by report dates.

  • Candidate pipeline

    Candidate profiles, contact details and candidate tags.

  • Job applications

    Active applicant submissions, assigned jobs and interview stage progression.

Metrics and dimensions

17 report fields across 3 datasets.

Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.

Send Ashby data anywhere

Ask AI about your data

Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.

AI tools can also make allowed Ashby changes. They can never widen their own access.

Which open jobs in Ashby have the most active applications, and at which interview stage are they?

Senior Backend Engineer has 46 active applications, 12 of them at Technical Interview; Product Designer has 31, mostly at Recruiter Screen.

Better than exporting by hand

Start from a goal

How it works

  1. Create a project and choose Ashby in Data sources.

  2. Pick where it goes. This one sends the numbers to Cloudflare R2.

  3. Pick where it goes. Choose candidates, jobs, or applications and a destination.

Sample report

Ashby reportSample data
NameEmailPrimary roleTagsCandidateJob titleStatusCurrent stage
Avery Chenavery@northwind.example1,2401,240Alex Rivera1,240ActiveLead
Jordan Blakejordan@harbor.example640640Oct 28640PendingProposal
Sam Okonkwosam@acme.example210210Oct 29210RefundedWon

Sample numbers, so you can see the shape. Your report uses your accounts.

Works well with Ashby

Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.

Questions

Free to start. Paid plans add more data sources and refresh faster.

Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.

No. Name a project, add a data source, then choose a report and destination.

OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.

The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.

No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Ashby account. Nobody else gets a Ashby login from this.

Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.

Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.

Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Ashby received it, the request is marked Uncertain and is never retried automatically, so you can check Ashby first.

Yes. Datapipe reads the reports on this page and can make one kind of change: update candidate tags. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.

This page lists 17 report fields across 3 datasets. You pick the columns when you build the report.

Job requisitions, candidate profiles, and application progression records from your Ashby hiring workspace. Account permissions and the records available from the provider determine which rows can be read.

One for each Ashby account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.

Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.

Try Ashby with sample data first

Build the report first, then add Ashby when you are ready.

Start free Add data source