Digital signatures: DocuSign, Dropbox Sign and PandaDoc (coming soon)
Coming soon: connect DocuSign, Dropbox Sign or PandaDoc and send contracts for e-signature straight from the chat. Meanwhile, send the PDF or your own signing link.
Watch this step in the video · The integrations page
Coming soon. These integrations are built but can't be connected in Omnifox yet; in Settings → Integrations their cards show as "Coming soon". This article describes how they will work. In the meantime you can send the contract as a PDF in the chat, paste a signing link you create in your own DocuSign, Dropbox Sign or PandaDoc account, or automate it with n8n, Make or Zapier.
What it is and when to use it
Once available, Omnifox will integrate with three e-signature providers — DocuSign, Dropbox Sign (formerly HelloSign) and PandaDoc — so you can send a signable contract right inside the conversation. The customer will get a signing link with their name and email already filled in; no sign-up, no downloads.
Perfect for closing contracts, proposals, authorizations or agreements without pulling the customer out of the chat.
Requirements
- An active DocuSign, Dropbox Sign or PandaDoc account.
- At least one template created in that provider (the base contract you'll send).
- Workspace admin rights to connect integrations.
Connect your signing provider (once available)
- Go to Settings → Integrations.
- Pick your provider's card — DocuSign, Dropbox Sign or PandaDoc. Today they show "Coming soon"; once available, you'll click Connect.
- Sign in to the provider and authorize access for Omnifox.
- Back in Omnifox, the card turns Active.
You can connect more than one provider, but the chat button uses whichever one is active for that workspace.
Send a contract for signing (once available)
- Open the customer's chat in the Inbox.
- In the composer, click the document icon — Send contract.
- The Send contract for signing modal opens: pick one of your available templates.
- Confirm. The customer receives a 📝 Contract for signature message with the link.
Omnifox uses the contact's name and email to pre-fill the signer, so make sure those fields are set on the contact record.
Verify it worked
- The contract bubble with the signing link stays in the chat.
- When the customer signs, the provider notifies Omnifox via webhook and the document status updates.
If it doesn't work
- No contract icon in the composer: no signing provider is Active in that workspace. While their cards show "Coming soon", the icon won't appear.
- "No templates available": create a template in the provider's dashboard (DocuSign/Dropbox Sign/PandaDoc); Omnifox only lists templates that already exist there.
- The customer's name/email isn't carried over: fill those fields on the contact record before sending.
- Error loading templates: the connection may have expired; reconnect the integration under Integrations.
Tips
- Keep one template per agreement type (service, NDA, renewal) so you can pick fast from the chat.
- To react to a signature, build a workflow that fires a message or creates a task when the contract is completed.
Related articles
Related articles
-
How to connect integrations and external apps
Connect Omnifox with your favorite tools from the integrations catalog in just a few steps.
-
Integrations and API complete guide
Integrations and API in depth, in 30 chapters: API keys, real calls, signed webhooks, n8n, MCP and SDKs, all really working.
-
Connecting Omnifox to Azur, Siigo, Alegra, QuickBooks or another accounting system or ERP
Omnifox doesn't have a native connector for accounting systems or ERPs today. Here's how to connect them anyway with workflows, the HTTP node, n8n, Make, Zapier or the API, with examples.
-
Generate and use API keys and webhooks
Create API keys to access Omnifox programmatically and set up webhooks to receive real-time events.
-
Getting started with integrations (webhook / OAuth / API key)
Connect Omnifox with your other tools: what's available today, what's coming soon, and when to use a webhook, an OAuth connection or an API key.