Private app on requestRecruiting / ATS
Greenhouse logo

Choosing a Docusign Greenhouse integration

A Docusign Greenhouse integration comes from Greenhouse, which sends offer letters through Docusign, or from the Greenhouse app Docusign publishes for Workflow Builder. For more, such as marking the hire after signing, Fluidlabs builds a private app for your account.

Greenhouse builds and supports its Docusign integration in Greenhouse Recruiting, and Docusign publishes and supports its Greenhouse app on the Docusign App Center. Fluidlabs built neither.

Docusign + GreenhouseWhat should Greenhouse and Docusign do together?An engineer replies within 48 hours with a scoped plan and a fixed price.

Used to reply to you about this request. Nothing else.

Status
Private app on request
Public integrations
By Greenhouse and Docusign
Private app hosting
US, EU or both
Fluidlabs security
ISO 27001, GDPR, SOC 2 Type II audit in progress

Which Docusign route fits your Greenhouse process?

Greenhouse builds a Docusign integration into its offers, and Docusign publishes a Greenhouse app for Workflow Builder. One of the two fits most teams. They differ in where the offer starts and what they write back to Greenhouse.

The line above each card names who publishes that route. Fluidlabs publishes none of the public routes. The last card is the private app we build for one customer.

Published by Greenhouse

Greenhouse's Docusign integration

Greenhouse builds it into Greenhouse Recruiting. Docusign tokens in your offer templates place the signature and date fields, a recruiter sends the offer with Send with Docusign, and Greenhouse uploads the signed letter to the candidate's profile. Greenhouse states that it works with any Docusign plan, and each user connects their own Docusign account.

Choose it when the agreement is the offer letter and recruiters send it from the candidate's offer in Greenhouse.

Published by Docusign

Greenhouse app from Docusign

Docusign publishes it on the Docusign App Center for Workflow Builder on an IAM plan, and its Read from Greenhouse step fills the offer letter with candidate, compensation and role data. The app pushes status updates to the candidate record and stores the signed letter in the candidate's file.

Choose it when the offer runs in a Workflow Builder workflow with web forms or steps in other systems.

Published by Zapier and Make

Connectors (Zapier, Make)

Make lists a Watch offers trigger for Greenhouse Recruiting and a Trigger Workflow action for Docusign IAM plans, so an approved offer can start a Workflow Builder workflow. Zapier lists Greenhouse triggers such as Candidate Hired. You build and maintain each automation.

Choose it when one Greenhouse event starts the agreement and your team maintains the automation.

Built by Fluidlabs for you

A private app for your account

Start with the public routes. A private app makes the Greenhouse updates neither publisher describes. After signing, it marks the application hired, closes the opening and writes the start date to the offer with a PATCH request, using a Harvest v3 OAuth token it renews. We build it for your account alone, publish it to your Docusign accounts only and host it.

Choose it when the signed offer must update the offer or the application in Greenhouse, or when a Greenhouse webhook must start the agreement.

Greenhouse's Docusign integrationGreenhouse app from DocusignConnectors (Zapier, Make)A private app for your account
Who publishes itGreenhouseDocusignZapier and MakeFluidlabs publishes it to your Docusign accounts only
Where it startsSend with Docusign on a candidate's offer in Greenhouse RecruitingA Workflow Builder start method, such as a link, a manual start or an API callA Greenhouse trigger, such as Watch offers in MakeA Greenhouse webhook, such as Offer approved, through the Workflow Builder API
Stages it coversThe offer stage only. Greenhouse recommends Forms for agreements at other stagesNot stated in the Docusign documentationDepends on the triggerAny stage change that Greenhouse reports as a webhook
Writes back to GreenhouseStatus on the Offer Details tab, and the signed letter on the candidate's profileStatus updates on the candidate record, and the signed letter in the candidate's fileDepends on the actions in the automationOffer fields, the hire and the opening, through Harvest v3
Who connects DocusignEach user connects their own Docusign account and connects again after 30 daysA Docusign administrator installs the app and connects it to GreenhouseYour team, in its Zapier or Make accountAn OAuth credential with the Harvest v3 scopes you approve
What it needsJob Admin or above in Greenhouse. Greenhouse states that any Docusign plan works and that Docusign recommends Business ProA Docusign IAM plan with Workflow BuilderA Zapier or Make account, and a Docusign IAM plan to trigger a workflowA written scope with a fixed price, then a monthly hosting plan

Verified on 28 September 2026. The last column describes what a private app can do once we confirm it against your accounts during scoping.

What Greenhouse's Docusign integration covers

Each note below comes from Greenhouse's own support articles, in its terms. Greenhouse lists its integration under the name Docusign, and the App Center listing of the Greenhouse app from Docusign states no limit.

  1. Offer stage only

    Greenhouse's integration, listed as Docusign

    The integration works only for candidates who are active in the offer stage. For agreements such as NDAs at earlier stages, Greenhouse recommends its Forms feature.

  2. Each user connects, every 30 days

    Greenhouse's integration, listed as Docusign

    Each person who sends or signs offers enables Docusign in their own Greenhouse account. Greenhouse states that sessions last 30 days, so users connect again after 30 days.

  3. Only the creator replaces an offer

    Greenhouse's integration, listed as Docusign

    Only the person who created the original offer can replace or resend it, and a resend fails when the offer went out more than 30 days ago.

  4. Signature date stays in the Activity Feed

    Greenhouse's integration, listed as Docusign

    Greenhouse shows the signature date in the candidate Activity Feed. The date does not appear in the offer data points of Greenhouse's essential reports.

  5. Tokens need their own line

    Greenhouse's integration, listed as Docusign

    Docusign tokens must sit on their own line in the offer template. A custom offer token with the same name takes precedence, and the Docusign token stops working.

  6. Hired candidates need an unhire first

    Greenhouse's integration, listed as Docusign

    Before you send a new agreement to a candidate marked as hired, you unhire the candidate.

What a private app covers

Greenhouse's integration and the app from Docusign cover most offer letters. A private app covers the four jobs below. It calls Harvest v3 with an OAuth token from the client credentials flow and requests a new token when one expires. Each job rests on an ability that Greenhouse or Docusign documents, and we confirm it against your account during scoping.

Mark the application hired after signing

Once the candidate signs, the private app marks the application hired through Harvest v3, records the start date and closes the matching opening on the job.

Write signed terms to the offer

Harvest's Update offer endpoint takes a PATCH request. The private app sends the offer's start date and offer custom fields, and Greenhouse creates a new offer version when the start date, the opening or a version-triggering custom field changes.

Send an agreement on a stage change

The private app receives Candidate stage change webhooks and sends the agreement for the stage you name, such as an NDA before the onsite. It files the signed copy on the application as a midfunnel_agreement through Harvest's Create attachment endpoint.

Start from an approved offer

Make's Watch offers trigger and Trigger Workflow action start the workflow when someone approves an offer. A private app takes Greenhouse's Offer approved webhook instead, checks its HMAC SHA-256 signature and starts the workflow with an API call.

Greenhouse's API, as we design around it

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 28 September 2026.

Authentication
Harvest v3 uses OAuth 2.0 and bearer tokens. A customer-built integration uses the client credentials flow, and a partner integration uses the authorization code flow under a signed Greenhouse partnership agreement. Access tokens expire, and a customer-built integration requests a new one with its client ID and secret.
Webhooks
Greenhouse Recruiting sends webhooks as JSON POST requests over HTTPS for events such as Offer approved, Candidate stage change and Candidate hired. A Signature header carries an HMAC SHA-256 digest of the body, and Greenhouse makes up to 7 attempts over 15 hours when a delivery fails.
API limits
Harvest v3 applies separate rate limits to custom and partner integrations on a fixed 30-second window. The X-RateLimit-Limit header returns the number of requests the window allows, and a request past it returns 429 with a Retry-After header.
Test environment
Greenhouse offers a sandbox to organizations on the Pro subscription tier. The sandbox has the same features as production, and logins do not carry over between the two environments.
Marketplace listing
Greenhouse Partner Directory. Greenhouse reviews integration requests on the first Monday of each month. A request needs at least one mutual customer and an active website with a privacy policy.
API styles
REST
How a build runs

From the first call to a hosted integration

  1. Scoping call

    Thirty minutes with the engineers. We map the records, the direction of travel and the edge cases.

  2. Written scope

    You get a fixed scope and a fixed price in one document. It quotes hosting and maintenance too.

  3. Build and review

    We build against test accounts. We walk you through the result before anything touches production.

  4. Hosted and monitored

    We run your private app on infrastructure we operate. We version each deploy, so we can roll one back.

What recruiting teams run on it

Send the offer letter from the candidate's offer in Greenhouse

The recruiter generates the offer from a template with Docusign tokens and sends it with Send with Docusign. The candidate signs, and Greenhouse uploads the signed letter to the profile.

Fill the offer letter from Greenhouse in a Workflow Builder workflow

The Read from Greenhouse step pulls the candidate's details, compensation and role into the offer letter. After signing, the app from Docusign stores the signed letter in the candidate's file.

Mark the hire when the candidate signs

A private app marks the application hired, records the start date and closes the opening, so the recruiter stops updating Greenhouse by hand after each signed offer.

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

Greenhouse and Docusign, answered

Does Greenhouse integrate with Docusign?
Yes. Greenhouse builds a Docusign integration into Greenhouse Recruiting for offer documents: tokens in the offer template place the signature fields, and Greenhouse uploads the signed letter to the candidate's profile. Docusign publishes a Greenhouse app on the Docusign App Center for Docusign Workflow Builder.
Does Fluidlabs have a Greenhouse app on the Docusign App Center?
No. Docusign publishes and supports the Greenhouse app on the Docusign App Center, and Fluidlabs built none of the public Greenhouse integrations. If the app from Docusign covers your process, use it. We can set it up in your account and build the Workflow Builder workflow around it. For the rest, such as marking the hire after signing, we build a private app for your account.
How does a Greenhouse offer letter Docusign workflow run?
You add Docusign tokens such as {{CANDIDATE_SIGNATURE}} to the offer template and generate the offer document in Greenhouse Recruiting. You click Send with Docusign, finish the offer email and select Preview on Docusign. There you can change the signing order. Greenhouse shows the status on the Offer Details tab and uploads the signed letter to the profile.
Can I use the Greenhouse Docusign integration before the offer stage?
No. Greenhouse states that its Docusign integration works only for candidates who are active in the offer stage, and it recommends Forms for agreements at earlier stages. A Workflow Builder workflow can start from a link, a manual start or an API call, and the Docusign listing for the Greenhouse app does not state which stages its steps cover.
What changes for a Greenhouse integration built on Harvest v1 or v2?
Greenhouse's Harvest documentation carries a notice that it deprecated the v1/v2 API and would remove it on August 31, 2026. Its v3 guide states that OAuth becomes the only supported authentication method, so an integration on Basic authentication moves to Harvest v3 and OAuth credentials.
Can a Docusign workflow call another system's API without a custom build?
Yes, when the other system's API fits the step. On qualifying IAM plans, such as IAM Professional and above, Docusign Workflow Builder has a Make a Web Request step, and Docusign installs the HTTP app the step needs. The step sends GET, POST or PUT requests to another system's API. The Docusign guide "Configure a Make a Web Request Step" lists Basic Auth connections, and the Docusign overview, "Connect to Any Service Using Web Requests", also lists OAuth 2.0 client credentials. If your system's API accepts one of those connections and each call is one of those requests, a workflow can call it. We check that on the scoping call. A custom build covers other sign-in methods and request types, and work that runs outside a workflow.
How does Fluidlabs price a custom integration?
We agree a fixed price in a written scope before work starts, then a monthly hosting plan. You see both numbers in the same document. Nothing bills hourly.
Who hosts and maintains what Fluidlabs builds?
Fluidlabs does. The engineers who build a private app or integration run it, monitor it and patch it. You choose the US region, the EU region or both, and your data stays there. Docusign and the other publishers on this page run and support their own public apps. The security and compliance section on this page has our certificate and agreements to download, and a form to request our security overview.

Related pages

Docusign + Greenhouse

Scope your Greenhouse and Docusign integration

Thirty minutes with an engineer, then a written scope with a fixed price.

Opens a short form here. You stay on this page.

Sources (26)

Each vendor fact on this page comes from one of the pages below.

Greenhouse 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.