Ashby integrations for Docusign, BambooHR, Rippling, Workday, ADP, Slack and Checkr come from Ashby. Ashby for Docusign IAM is in development at Fluidlabs. For other connections, we build and host a private integration for your team.
Ashby publishes and supports its own Docusign integration. On 27 September 2026 the Docusign App Center listed no Ashby app. Ashby for Docusign IAM is in development at Fluidlabs.
Each card states what exists today and who publishes it. On the Docusign card, the chip marks our app in development. On the others, it marks a private integration we build and host for your team.
Recruiters send offer letters and other hiring documents for signature, and Ashby shows the signing status on the offer.
Public integration by Ashby.
Today: Ashby publishes a Docusign integration. It sends e-signature offers and documents through your Docusign account and shows the request status within the offer details.
After a candidate accepts an offer, a recruiter pushes them from Ashby to BambooHR, with the resume and offer letter on file.
Today: Ashby publishes a one-way sync from Ashby to BambooHR on all Ashby plans, and it can file the resume and offer letter in categories you pick. After a candidate accepts an offer, a user pushes them from their profile, or an admin turns on automatic pushes for hired candidates. Ashby states that it cannot send an amended start date after the push.
A hired candidate's name, contact details, salary and start date reach Rippling to start onboarding.
Today: Ashby publishes a one-way sync from Ashby to Rippling. It pushes name, email address, phone number, salary and start date by default.
Positions and job requisitions flow from Workday into Ashby, and hired candidates flow back to Workday.
Today: Ashby publishes a two-way Workday integration on its Enterprise plan. The sync runs once every 20 minutes.
A candidate marked Hired in Ashby becomes a pre-hire record in ADP Workforce Now.
Today: Ashby publishes the Ashby Connector for ADP Workforce Now. It sends new hire data to ADP Workforce Now once a user marks the candidate Hired.
Okta signs recruiters and interviewers in to Ashby and provisions their accounts from your directory.
Today: Ashby supports SSO and SCIM through WorkOS and names Okta among its identity providers. SCIM needs the Legacy Plus, Plus or Enterprise plan.
Hiring teams receive Ashby notifications in Slack and can get one private channel for each candidate's interview loop.
Today: Ashby publishes a Slack integration. The Ashby bot sends updates by direct message or channel. Ashby can create one private interview channel for each job consideration and reuses it across the interview loop.
A recruiter orders a Checkr report from the candidate's profile and follows its status in Ashby.
Today: Ashby publishes a Checkr integration in its Integrations Directory. A user starts each background check from an activity, and Ashby states that Checkr activities cannot start on their own.
Four systems handle a new hire between the accepted offer and the first payday. BambooHR for Docusign IAM, our live app, can run the third step, and Ashby's own BambooHR sync pushes hires too. We build the payroll step as a private integration and host it for you.
Candidate accepts the offer
New hire signs the offer and the contract
Workflow creates the employee record
New employee record reaches the payroll system
Each pattern rests on a documented part of Ashby's API. On the scoping call we pick one based on how soon the other system needs each change.
Ashby sends a webhook for the event type you choose, such as candidateHire or offerCreate, and signs it with your secret token. A relay checks the signature and calls the other system.
Use it when the other system must react to a hire or an offer as it happens.
A job passes the sync token from its last run, and Ashby returns the records updated since. Past 100 pages, Ashby rejects the incremental sync and asks for a full sync, so the job runs at least once a day, as Ashby recommends.
Use it for reporting, and for systems that accept a delay between runs.
The other system requests one offer from Ashby at the moment it needs the data, with the file handles for the signed documents. The API key carries read or write permission per module.
Use it when a form or an agreement needs the current values of one offer.
We took each fact from the vendors' own documentation and listings. The sources list at the foot of this page links each one.
Verified on 27 September 2026.
The engineers who build the integration also run it, so the people who answer your questions know the code.
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.
EUR 1M technology and cyber insurance, evidenced on request.
Independently certified by Swiss Approval, current to May 2027 and verifiable through the issuing body.
GDPR, UK GDPR and Swiss FADP covered, with the EU standard contractual clauses incorporated. Read it now, request the version for signature.
Licence, support response targets, availability, IP and liability for your use of the extension apps. Personal data stays with the DPA.
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.
Thirty minutes with an engineer, then a written scope with a fixed price.
Opens a short form here. You stay on this page.
Each vendor fact on this page comes from one of the pages below.
Ashby and the other product names and logos on this page are trademarks of their owners. Fluidlabs uses them to identify the products. Their use implies no endorsement. Docusign is a trademark of Docusign, Inc. To ask us to remove a mark, email hello@fluidlabs.com.
