HubSpot, Docusign and Integration Glue each publish a Docusign HubSpot integration. HubSpot's app sends envelopes from records, and the Docusign app writes signed values back. Fluidlabs builds a private app for your account that sends those values on to billing.
Docusign publishes and supports the HubSpot app on the Docusign App Center and lists it on the HubSpot Marketplace as Docusign IAM. HubSpot and Integration Glue each publish and support a Docusign app there. Fluidlabs built none of them.
HubSpot and Docusign each publish an integration, and most teams can start with one of them. Compare the routes on two points: where the agreement starts, and which HubSpot data comes back after signing.
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 HubSpot
HubSpot builds it and lists it in the HubSpot Marketplace. It starts inside HubSpot: you create, send and track envelopes from a contact, company or deal record, and a Docusign card shows the status of each envelope. A HubSpot workflow can send an envelope from a template.
Choose it when your reps send agreements from HubSpot records and the signed values can stay in Docusign.
Published by Docusign
Docusign publishes it on the Docusign App Center. It adds three steps to Docusign Workflow Builder: Read from HubSpot, Writeback to HubSpot and Store Files in HubSpot. The steps cover standard objects and custom objects. It needs a Docusign IAM plan.
Choose it when you hold a Docusign IAM plan and the agreement needs HubSpot data in it and signed values back on the record.
Published by Integration Glue and others
Integration Glue lists it in the HubSpot Marketplace. A HubSpot workflow sends the envelope to up to four signatories. Integration Glue's app then attaches the signed copy to a note on the record and syncs envelope status to it. Zapier and Make also list both products, and a Zap can start a Workflow Builder workflow from a HubSpot deal stage.
Choose it when a HubSpot workflow should send the envelope and file the signed copy on the record, or one Zap should start a Workflow Builder workflow.
Built by Fluidlabs for you
The apps from HubSpot and Docusign connect the two products. Your private app adds the steps that carry signed values into billing or an ERP and write the order number back to the HubSpot deal. We build it for your account alone, publish it so that only your Docusign accounts can install it, and host it.
Choose it when the agreement process reaches past HubSpot and Docusign into a third system, such as billing or an ERP.
| HubSpot's Docusign app | HubSpot app from Docusign | Integration Glue's HubSpot app, Zapier and Make | A private app for your account | |
|---|---|---|---|---|
| Who publishes it | HubSpot | Docusign | Integration Glue. Zapier and Make list both products as connectors | Fluidlabs builds it for your account |
| Where it starts | Inside HubSpot, from a contact, company or deal record, or from a HubSpot workflow | Inside Docusign, from a start method such as a link, a manual run, a Docusign event or an API call | Inside HubSpot, from a HubSpot workflow. A Zap starts from a trigger on either product | From the HubSpot event you name, such as a deal stage change |
| Reads HubSpot data into the agreement | Yes, from mapped contact, company and deal properties | Yes, from the objects Docusign supports, custom objects included | Integration Glue's listing says it applies HubSpot fields in Docusign. A Zap depends on its actions | Yes, through the Docusign Read step or a read of its own |
| Writes signed values back to HubSpot | No. HubSpot states that its integration does not sync data. An envelope status change can start a HubSpot workflow | Yes, through the Writeback to HubSpot step | Integration Glue syncs envelope status and recipient details to the record. A Zap depends on its actions | Yes, through the Docusign Writeback step or HubSpot's API |
| Stores the signed document in HubSpot | Not stated in HubSpot's documentation. A user downloads the PDF from the Docusign card | Yes, through the Store Files in HubSpot step, for files up to 10 MB | Integration Glue attaches it to a note on the record and the file manager. A Zap depends on its actions | Yes, through the Docusign step or a note on the record |
| What it needs | A paid Docusign plan. HubSpot workflows need a Professional or Enterprise subscription | A Docusign IAM plan, and a Docusign admin to install it | An Integration Glue subscription, Free to Enterprise plans, or a connector account | A written scope with a fixed price, then a monthly hosting plan |
Verified on 27 September 2026. The last column describes what a private app can do once we confirm it against your accounts during scoping.
Each note below comes from the publisher's own documentation, in its terms. The first four belong to HubSpot's app, which HubSpot lists under the name Docusign. The last four belong to the app from Docusign, which Docusign lists under the name HubSpot.
HubSpot's app, listed as Docusign
HubSpot states that its integration lets you select and send documents and see their status. It does not sync information about contacts, companies, deals or the document between HubSpot and Docusign.
HubSpot's app, listed as Docusign
HubSpot fills mapped fields from the contact or deal record used to create the envelope. It does not fill them on an envelope created from a company record, because that envelope starts with no recipients.
HubSpot's app, listed as Docusign
In a contact-based workflow, the Docusign template can set only the enrolled contact as a recipient. In a deal-based workflow, the template cannot have more recipients than the deal has associated contacts.
HubSpot's app, listed as Docusign
Custom property mapping needs a Docusign eSignature Business Pro plan or higher. Workflow features need a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub or Data Hub.
App from Docusign, listed as HubSpot
Each Read from HubSpot step returns up to five matching records to the workflow.
App from Docusign, listed as HubSpot
The Store Files in HubSpot step stores files up to 10 MB. It needs a Read from HubSpot or Writeback to HubSpot step before it in the workflow.
App from Docusign, listed as HubSpot
Docusign lists Email and Feedback submission as objects the steps do not support, and the steps cannot create a new Lead record. Number fields arrive as text, so rules on them use only equal to and not equal to.
App from Docusign, listed as HubSpot
Workflow Builder does not support all list and dropdown fields. To write a Deal Stage or Lifecycle Stage value, you enter HubSpot's internal name for that value in the Writeback step.
The HubSpot app from Docusign reads, writes and files HubSpot records. A private app covers the four jobs below when your process reaches a third system. Each job rests on an ability HubSpot documents for its API, and we confirm it against your HubSpot account during scoping.
Your private app subscribes to changes of the dealstage property, or a HubSpot workflow calls it through the Send a webhook action, which needs Data Hub Professional or Enterprise. It then starts the Docusign workflow through the API.
The private app sends the deal's record ID as a start variable. The Docusign Read from HubSpot step uses that ID to find the deal and pull its fields into the agreement.
Once the agreement completes, your private app sends the signed values to your billing or ERP system, and the Docusign Writeback step or HubSpot's deals API puts them on the deal.
Your billing or ERP system creates the order, and the private app writes the order number to a custom deal property through HubSpot's deals API.
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.
Thirty minutes with the engineers. We map the records, the direction of travel and the edge cases.
You get a fixed scope and a fixed price in one document. It quotes hosting and maintenance too.
We build against test accounts. We walk you through the result before anything touches production.
We run your private app on infrastructure we operate. We version each deploy, so we can roll one back.
A rep moves the deal to Contract sent in HubSpot, and a Zap or your private app starts the Docusign workflow. The Docusign Read step fills the order form with the deal amount and the contact's details.
The customer signs and enters the contract term. The Docusign Writeback step puts the term and the signed date on the deal, and finance builds its renewal report from HubSpot.
The Docusign Writeback step puts the signed values on the deal, and your private app sends them to your billing system. Finance raises the first invoice without asking sales for the signed terms.
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.
HubSpot 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.
