CONNECT YOUR WORKFLOW
Bring signing closer to the places your team already works. Explore developer tools, workspace connections and the next integrations we’re building.
Clear availability. Specific workflows. A team to help you connect.
Prepare · send · signTHE INTEGRATION DIRECTORY
Every connection has a different starting point. Explore what it does, what’s being built and how to take the next step.
21 integrations · Check each connection’s availability and supported workflow.
Automation
Bring signing into the automations your team already runs.
A private app package includes template sending, role and field mapping, signing events, and completed signed-PDF retrieval. Live qualification is pending; public customer installation is not available.
Private app qualification and a tested document handoff come before public availability.
Discuss Zapier accessLegal
Less retyping between your legal clients and their documents.
Native secure connection, client search and selected-contact import are unreleased development work. Matter selection and automatic signed-document return are still in development. Clio Grow is a separate product.
Developer access, supported regions and the full client-to-matter workflow need qualification.
Discuss your Clio workflowCRM
Start with CRM contacts. Keep agreements connected to the customer.
Native secure connection, contact search and selected-contact import are unreleased development work. Deal mapping, private file return and an in-record experience remain in development. There is no public PearSign marketplace listing yet.
Pilot account qualification and a verified signed-file handoff are next.
Discuss your HubSpot workflowCRM
Reuse customer details when preparing documents for signature.
Native secure connection, Contact search and selected-contact import are unreleased development work. Native Opportunity mapping and automatic signed Files return are still being developed. Account API access and object permissions apply.
An authorized Salesforce app and an API-enabled pilot organization are required.
Discuss your Salesforce workflowStorage
Connect a destination for supported signed-document exports.
PearSign includes a Google OAuth connection and signed-document export service. Availability depends on deployment configuration, the authorizing account and folder permissions.
Confirm your workspace configuration and destination with our team before relying on automatic exports.
Check Drive setupStorage
Keep supported signing exports with your team’s files.
PearSign includes a Dropbox OAuth connection and signed-document export service. The account and destination folder must be authorized and configured for your workspace.
Confirm the folder, permissions and export behavior with our team.
Check Dropbox setupDeveloper
Build your signing workflow with templates and stable fields.
Use scoped API credentials for documented template, envelope, status and download operations. The shared send path applies recipient validation, allowances and signing controls.
Review permissions and test your workflow before production.
Explore the APIDeveloper
React to signing events without checking every document.
Subscribe to supported document events and verify signed deliveries. Individual signer completion and all-party document completion are separate events.
Use event IDs for deduplication and plan for retries and outages. Workspace plan and webhook allowances apply.
Read developer documentationLegal
Client and case records. API entitlement and document return need qualification.
Client and case records. API entitlement and document return need qualification. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request MyCaseLegal
Engagement documents alongside matters. Approved API access is required.
Engagement documents alongside matters. Approved API access is required. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request PracticePantherLegal
Signed documents returned to the correct matter. Partner and production permissions need qualification.
Signed documents returned to the correct matter. Partner and production permissions need qualification. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request SmokeballLegal
Agreements connected to projects. Partner OAuth and document association need qualification.
Agreements connected to projects. Partner OAuth and document association need qualification. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request FilevineLegal
Signing alongside practice documents. Developer approval and document operations need qualification.
Signing alongside practice documents. Developer approval and document operations need qualification. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request LEAPLegal
Legal operations and signing. Litify-specific permissions are separate from Salesforce access.
Legal operations and signing. Litify-specific permissions are separate from Salesforce access. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request LitifyStorage
Signed-file return to SharePoint and OneDrive, with selected destinations and tenant consent.
CRM
Agreements attached to the right deal, with authorized record and file access.
Agreements attached to the right deal, with authorized record and file access. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request PipedriveCRM
CRM records and attachments, with regional OAuth and module permissions.
CRM records and attachments, with regional OAuth and module permissions. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request Zoho CRMAutomation
Signing inside visual automation scenarios. A dedicated app and tested recipes are planned.
Signing inside visual automation scenarios. A dedicated app and tested recipes are planned. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request MakeAutomation
Signing in your automation workflows. A dedicated node and tested templates are planned.
Signing in your automation workflows. A dedicated node and tested templates are planned. No native PearSign connector is available in this release.
Share your workflow so we can qualify access and prioritize a pilot.
Request n8nBanking
A product-specific banking document workflow. Banno, jXchange, SymXchange and document stores have different requirements.
A product-specific banking document workflow. Banno, jXchange, SymXchange and document stores have different requirements. No native PearSign connector is available in this release.
An institution or tenant sponsor, exact product/API and approved document contract are required.
Request Jack HenryBanking
Document signing for an authorized tenant workflow, with sponsored access and a defined document store.
Document signing for an authorized tenant workflow, with sponsored access and a defined document store. No native PearSign connector is available in this release.
An institution or tenant sponsor, exact product/API and approved document contract are required.
Request MambuBUILT AROUND THE CLIENT FILE
Engagement letters, client authorizations and the agreements that keep a matter moving. Our legal integration roadmap starts with Clio Manage and expands around the workflows firms ask for.
Explore legal integrationsBring the right details into the document.
Use your firm’s template and signing roles.
Native matter return is the next step we’re building.
FOR YOUR DEVELOPERS
Start with documented template and envelope operations, stable field mappings and signed events. Build a connection around your own application’s needs.
POST /api/v1/envelopes/send
Authorization: Bearer <your-api-key>
{
"templateId": "your-template-id",
"recipients": [{
"name": "Jane Client",
"email": "jane@example.com",
"roleId": "client-role"
}]
}Illustrative values. Use the IDs and permissions from your own workspace.
BEFORE YOU CONNECT
The PearSign API and signed webhooks support custom document workflows. Google Drive and Dropbox export services require workspace and provider setup. Native HubSpot, Salesforce and Clio Manage contact workflows and the Zapier app are in development and qualification; they are not publicly installable marketplace apps yet. Check the directory details or ask our team about your account.
Automatic native record attachment is still being developed for the new CRM connectors. The Zapier package includes completed signed-PDF retrieval for a downstream file action, but it must be privately qualified first. We will confirm the exact record, document and return behavior before offering a pilot.
Custom API integrations require a developer. The native CRM experience being developed uses secure sign-in and contact selection. The Zapier app is intended for no-code workflow setup after private qualification and publication.
The current native work targets Clio Manage. Clio Grow has a separate API and different document capabilities, so Manage support does not imply Grow support. Tell us which product and workflow your firm uses.
Those connections are planned and need product- or tenant-specific access and an institution-sponsored pilot. We will scope the authorized document workflow with you before promising compatibility. No general Jack Henry or Mambu connector is available in this release.
Contact our team with the platform you use, the document you send, the client or record it belongs to, and where the signed copy should return. We can discuss access requirements and whether a pilot fits your workflow.
LET’S CONNECT THE RIGHT THINGS
A CRM. A case file. Your own product. We’ll help scope the document workflow and the connection it needs.
Plan your integration Or contact our team