Agreements Start Where Your Team Works. Signed Copies Go Back There.
Start an agreement from an AI assistant, a Slack message, a forwarded email or your CRM. The signed copy goes back to where the deal lives.
- An admin connects the CRM and Slack
- Test documents never reach your CRM
- Only links travel on WhatsApp
Start an agreement from
Zoho CRM · deal
Northwind Systems · SOW 04
Stage: Contract₹21.4 lakh · owner Karthik. A Zap sends the SOW template at this stage.
FlowVerify
Statement of Work 04
FV-2611-118 · 2 signers · sent from a template
The deal contact becomes a signer.
Zoho CRM · contact and deal
- Deal moved to Closed Won
- Statement of Work 04_signed.pdf attached to the contact
- Note on the contact: Signed, 13 Nov 2026
Slack · Shalini Bose
/flowverify send vendor-nda.pdf to Farah Qureshi, due 20 Nov
FlowVerify drafts it and sends you a link to review.
FlowVerify
Vendor NDA · Nandi Freight
FV-2611-102 · Farah Qureshi · Aadhaar eSign
Sent only after you confirm the draft.
Slack · direct message
- Vendor NDA signed by Farah Qureshi
- Completed 13 Nov 2026, 11:24 · FV-2611-102
- A link back to the document, not the file
Email · forwarded by Shalini Bose
To: send+7kq2m4…@inbound.flowverify.co
Fwd: Offer letter
Send to: Rohan IyerDue: 25 NovOffer Letter.pdf
FlowVerify
Offer Letter · Rohan Iyer
FV-2611-124 · fields placed for you
A single-use link opens the draft on Review.
Email · everyone on the document
- Completion email to Rohan Iyer and Shalini Bose
- Offer Letter_signed.pdf to download
- Certificate of Completion with it
Test documents never reach your CRM.
Catalogue
Every Connection, and What Moves Through It
Each tile says what the connection does. Open one to see which data travels in which direction, and how access is given and taken away.
28 connections. Pick one to see what moves and how it is authorised.
Need One That Is Not Here?
Tell us the tool and what should happen when a document is signed. Anything with a Zapier app or an HTTP API can already call FlowVerify.
How it flows
Four Flows, Drawn End to End
Each one starts in a tool your team already has open, and ends with the signed copy filed where it belongs.
Delivery
Signers Get It Where They Already Reply
Email always goes out. Add WhatsApp for the link and the reminders, send from your own domain, or start the whole thing by forwarding an email.
WhatsApp, With a Link and Nothing Else
The invite, reminders and the completion notice. The signer opens the link and signs in the signer app.
10:51
11:02
11:02
Reply STOP to stop messages on WhatsApp.
Email From Your Own Domain
Verify the domain with a DNS record and signing emails carry your name and a verified sender line.
- From
- Kiran Exports <[email protected]>
- Subject
- Shalini Bose sent you Vendor NDA to sign
Hello Farah, the mutual NDA we discussed is ready. It takes two minutes and one signature.
Review & signSent securely with FlowVerify
Forward an Email to Send
Your own words above the forwarded message decide the recipients, the roles and the deadline.
- To
- send+7kq2m4x9…@inbound.flowverify.co
- Subject
- Fwd: Rate revision letter
Send to: Farah Qureshi <[email protected]>
Due: 30 Nov
Rate Revision Letter.pdf
---------- Forwarded message ---------- (ignored)
Draft created, 2 fields placed, pre-send check run. A single-use link to the Review step goes to you alone and lasts 24 hours.
Control over every connection
Control
Every Connection Is Listed, Logged and Revocable
Settings, Integrations shows what is connected and who connected it. For a CRM it also shows every update FlowVerify made, what changed, and why a failed one failed.
- A CRM connection belongs to the workspace, not to the person who set it up.
- Tokens are stored encrypted. FlowVerify never sees your CRM password.
- Temporary CRM failures are retried, and a retry never writes a note or a PDF twice.
- Disconnect a tool or revoke a mandate and it stops at once. A revoked API key stops within a minute.
- Disconnect
Zoho CRMConnected
India data centre · connected by Shalini Bose
- Disconnect
SlackConnected
Kiran Exports workspace · alerts in #procurement
- Disconnect
Google DriveConnected
Shalini Bose’s Drive · signed PDFs to the FlowVerify folder
Recent CRM updates
- 11:24
Statement of Work 04
envelope.completed1 contact matched, deal moved, note logged, 1 PDF attached
Updated - 10:51
Statement of Work 04
envelope.sentDeal moved to Contract sent, 3 fields written
Updated - 09:12
Vendor NDA
envelope.sent1 contact created, note logged
Updated - Yesterday
Franchise Agreement
envelope.declinedThe CRM rejected the update. Check the field mapping.
FailedRetry
For developers
Build the Connection You Need
A REST API with a test mode, signed webhooks and two SDKs. Zapier, Make and n8n run on the same API with a workspace key, and the MCP server hands the same tools to an agent.
- REST API
- Webhooks
- Test mode
- TypeScript SDK
- Python SDK
- Zapier app
- MCP server
- Embedded signing
Subscribe an endpoint to signing events
Test keycurl -X POST https://api.flowverify.co/v1/webhooks \ -H "Authorization: Bearer fv_test_xxxxxxxx" \ -H "Content-Type: application/json" \ -d '{ "url": "https://hooks.kiranexports.in/flowverify", "events": ["envelope.completed", "envelope.declined"], "description": "ERP sync" }'The signing secret comes back once. Every delivery is then signed, retried on failure and kept in a 30-day log.
FAQ
Questions About Connecting FlowVerify
Looking for one tool in particular? Search the catalogue, or book a demo and we will walk you through it.
A CRM or the Slack app is connected by a workspace Owner or Admin, or by someone in a custom role that has the integrations permission. A CRM connection belongs to the workspace rather than to the person who clicked Connect, so it keeps working when they leave. Each person connects their own Google Drive, OneDrive or Dropbox. API keys and agent mandates are issued by admins, and an AI app that signs in needs approval from someone who is allowed to manage agents.
Only what that connection needs. A CRM receives the document name, reference, status, a link, the relevant dates and, if you switch it on, the signed PDF. Slack receives status notices. Webhooks carry ids and statuses, plus the name, email and role of the recipient on recipient events, and never documents, signing links, one-time codes or IP addresses. A storage tool receives the signed PDFs you save to it, and FlowVerify reads only the files you pick.
Disconnect a CRM, Slack or storage connection from Settings, Integrations. Disconnect an AI app from Agents, Connected apps, and it stops working for the workspace at once. Revoking a mandate stops the agent immediately. A revoked API key stops working everywhere within a minute. Documents that were already sent or signed are not affected.
No. Documents created with a test key never reach your CRM, never email, text or WhatsApp anyone, and are never charged. Test events still reach your webhooks, marked livemode: false, so you can build against them.
No, only links do. The signer gets the invite, reminders and the completion notice on WhatsApp with a link to the FlowVerify signer app, where the one-time code, consent and Aadhaar eSign steps run as usual. A signer who replies STOP receives no further WhatsApp messages.
No. Signing is always done by the signer, in the FlowVerify signer app. An API call, a Zap or an agent can prepare, send, remind and download. None of them can sign, approve or enter a one-time code on a signer’s behalf.
Book a demo
See It on Your
Own Agreements
Bring one agreement you send often. We run it through FlowVerify with you, live, from first draft to signed record.
What you get
- A live walkthrough on one of your own agreements
- A workspace set up for your team
- Answers from the people who build it