Ashby logo

Ashby

Extension app

By Fluidlabs

Offer letters pre-filled from Ashby candidates, jobs and offers, the signed document filed on the candidate.

View on the App Center ↗
Docusign App Center extensionUS region

Ashby for Docusign IAM

An Ashby Docusign integration that runs inside Workflow Builder: read a candidate, job consideration, job or offer to pre-fill the offer letter, create or update the candidate or move the job consideration to its next stage, add a note, and file the signed document under the candidate's Other Files.

Ashby for Docusign IAM is a Fluidlabs extension app listed on the Docusign App Center under the name Ashby. Its steps appear natively in Docusign Workflow Builder, and Fluidlabs runs the app on its own infrastructure (US region, AWS), so there is no Zapier, Make or other automation platform to set up.

Install from App Center ↗Read the documentationCompliance review ↓
Compare the routes

Three ways to get an Ashby offer letter signed

The routes start in different places. Here is what each one asks of your recruiting team.

Ashby's Docusign integration

Ashby's own integration sends e-signature offers and documents through your company's Docusign account and shows the status of each request within the offer details. Choose it when the offer starts in Ashby and needs a signature.

Automation platforms (Zapier)

Zapier lists Ashby triggers, such as Candidate Hired and Offer Created, beside Docusign actions. The automations run on Zapier and suit teams that already run their automations there.

This app

Ashby for Docusign IAM (this app)

Runs inside Docusign Workflow Builder: a Read step pulls the candidate, job consideration or offer into the workflow, the offer letter goes out pre-filled, File Upload files the signed document under the candidate's Other Files and a Writeback adds a note or moves the stage. Choose it when the offer process itself runs on Docusign IAM.

Capabilities

What it adds inside Workflow Builder

Once installed, the app's actions appear as native workflow steps. No code, no separate automation platform, no sync jobs to run.

Read from Ashby

Pull a Candidate, Job Consideration, Job or Offer into the workflow and use its fields as variables to pre-fill an offer letter. An Offer read returns its latest version with the candidate's name and email and the job title. Find a record by Record ID or by a searchable field such as Email, and return one record or up to five.

Writeback to Ashby

Create or update a candidate or a job consideration, or add a Note to a candidate. Update or Create keyed on Email updates the match or creates the candidate, and a job consideration moves to another interview stage by the stage's title. Empty values are ignored, so a workflow never clears a field.

File Upload to Ashby

File the signed document, up to 30 MB, under the candidate's Other Files. The folder holds the candidate's Record ID from an earlier step, and the same file sent to the same candidate again within 10 minutes is filed once.

Private or shared connections

An Ashby Organization Admin creates an API key with the permissions the documentation lists, and you paste it when you connect, as a Private connection for one user or a Shared one for the team. The key is checked with Ashby before the connection is saved, and disabling it in Ashby stops every connection that uses it.

Live in an afternoon

To connect Ashby to Docusign, install the app from the App Center like any Docusign extension, authorize your Ashby account, and add the steps to a workflow. Full setup, configuration and known behaviors are covered in the documentation.

1

Install from App Center

One click from the official listing into your Docusign account.

2

Connect Ashby

Authorize your Ashby account and name the connection.

3

Add steps to any workflow

The Ashby actions appear as native Workflow Builder steps.

What recruiting teams run on it

Offer letters

The offer letter goes out pre-filled from the offer

Read from Ashby reads the Offer by its Job Consideration Record ID, with the start date, salary and currency, the candidate's name and email and the job title. Prepare eSignature Template fills the letter, and Send Documents for Signature delivers it.

Signed and filed

The signed letter lands in the candidate's Other Files

After signing, File Upload to Ashby files the Combined Envelope File under the candidate's Other Files, found by the Record ID the Read step returned, so the recruiting team opens the signed letter from Ashby.

Pipeline updates

A note, a tag or the next stage, written back

A Writeback step adds a Note recording the agreement, tags the candidate, or moves the job consideration to its next interview stage, so the recruiter sees the outcome in Ashby without opening Docusign.

Security & compliance

Built to pass your security review

The documents your security team will ask for exist, are current, and are ready to hand over. Terms of service and the privacy policy are published on this site.

ISO/IEC 27001:2022
Certified
SOC 2
In progress

EUR 1M technology and cyber insurance, evidenced on request.

Certification

ISO/IEC 27001:2022 certificate

Independently certified by Swiss Approval, current to May 2027 and verifiable through the issuing body.

Download the certificate (PDF)
Data processing

Standard DPA

GDPR, UK GDPR and Swiss FADP covered, with the EU standard contractual clauses incorporated. Read it now, request the version for signature.

Download the DPA (PDF)
Terms

Service Terms

Licence, support response targets, availability, IP and liability for your use of the extension apps. Personal data stays with the DPA.

Download the Service Terms (PDF)
Security overview

Security & Data Protection Overview

Certifications, hosting and encryption, access control, secure development, monitoring and incident response, in one document for your security assessment.

The Security & Data Protection Overview and the DPA prepared for signature are provided on request: , or email secops@fluidlabs.com.

FAQ

The Ashby Docusign integration, answered

Does Ashby integrate with Docusign?
Yes, in more than one way. Ashby publishes its own Docusign integration, which sends e-signature offers and documents through your company's Docusign account. Ashby for Docusign IAM, published on the Docusign App Center by Fluidlabs, a Docusign Build IAM Specialized Partner, works at the workflow layer instead: it adds Read, Writeback and File Upload steps for Ashby inside Docusign Workflow Builder.
Is this the official Ashby integration for Docusign?
It is a Fluidlabs app, not one from Ashby or Docusign. Fluidlabs, a Docusign Build IAM Specialized Partner, built it, operates it and supports it, and it is listed on the Docusign App Center under the name Ashby, with Fluidlabs as the publisher.
How is this different from Ashby's Docusign integration?
Ashby's integration works from inside Ashby: it sends offers and other hiring documents for e-signature through your Docusign account and shows the request status within the offer details. This app works from Docusign. It runs inside Workflow Builder, reads the candidate, job consideration, job or offer, files the signed document on the candidate and writes the outcome back to Ashby, with routing and logic managed in Docusign. Teams that run the offer process on Docusign IAM use this app; teams that send offers from Ashby can use Ashby's integration, which files the signed copy itself.
Do I need Zapier or Make to connect Ashby and Docusign?
No. The steps appear natively in Docusign Workflow Builder once you install the app from the Docusign App Center, and Fluidlabs runs the app on its own infrastructure. There is no Zapier, Make or other automation platform to set up, and no sync jobs to monitor.
Which Ashby records can the workflow use?
Five objects. Candidates and job considerations, a candidate's application to one job, can be read, created and updated. Jobs and the latest version of each offer are read only, and notes are added to a candidate. Custom fields are not part of this version.
Can the workflow move a candidate to the next stage?
Yes. A Writeback step on a job consideration moves it to a stage of the job's interview plan, by the stage's title. A move to an Archived stage needs an Archive Reason, and a move to Hired or to an Archived stage can start the automations your Ashby account runs on those stages, so check them before you automate the move.
Does it work with Docusign Maestro?
Yes. Maestro is now called Docusign Workflow Builder, and that is where the Ashby steps run. Read from Ashby, Writeback to Ashby and File Upload to Ashby are added to a workflow like any other step.
What do I need to use it?
An Ashby account, an Ashby Organization Admin who can create an API key, and a Docusign account with admin rights to install and manage apps in the App Center. The key needs Read on Jobs, Candidates, Hiring Process Metadata, Organization, Offers and Api Keys, and Write on Candidates.
Where does our candidate data go?
Candidate, job and offer data moves between Ashby and your Docusign account at workflow runtime: the Read step pulls the fields you select into workflow variables, and the Writeback and File Upload steps send data and signed files back to Ashby. Fluidlabs operates the app under ISO 27001 certification, hosted in the US region on AWS.
How long does setup take?
The install is a short sequence: search for Ashby in the Docusign App Center, click Install App, then Install and Authorize. Click Connect Account, choose a Private or Shared connection, name it and click Log In, then click Allow, paste the Ashby API key and click Continue to Docusign. The three Ashby steps are then available in Workflow Builder, and building the workflow takes as long as your process needs.
What does support look like?
Named support at docusign-support@fluidlabs.com, monitored weekdays 09:00-19:00 CET, with priority-based response targets set out in the Service Terms.
Can Fluidlabs build the hiring workflow for us?
Yes. Fluidlabs builds Docusign extension apps and the Workflow Builder flows around them as a service. The team behind this app can design and configure your Ashby offer workflow end to end.

Need Ashby to do more than the app covers?

The app covers the steps on this page. When you need a custom object, a module the app skips, or a sync on your own schedule, we scope that work as an integration and put a fixed price in writing. Enterprise Integration starts at $45,000.

Scope a custom integration →See Enterprise Integration →

Setup documentation

Install steps, configuration and known behaviors, kept current.

Read the docs →

All Fluidlabs integrations

Every app we run on the App Center, plus the roadmap.

Browse integrations →

Need a different app built?

We build, submit and operate App Center extension apps.

Extension-app development →

Ready to connect Ashby?

Install in minutes, or talk to us about a workflow built around it.

Install from App Center ↗Book a 20-minute call