Skip to content
BTS 2026Met us at the summit?Claim your summit offer
CRM, chat, storage, delivery and AI agents

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

Out for signature

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

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.

Tell us which tool

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.

01CRM

A Deal Reaches a Stage and the Agreement Goes Out

A Zap, or one API call from your own system, sends the right template when a deal reaches the stage you choose, with the deal contact as the signer.

When the last signer finishes, the Zoho CRM or HubSpot connection moves the deal to the stage you mapped, logs a note and attaches the signed PDF. Updates run in the background, so a slow CRM never slows a signer down.

  1. Deal stage
  2. Template sent
  3. Stage moved, PDF attached
HubSpot · Deal
Updated by FlowVerify

Sundaram Packaging · Supply 2027

₹2,40,000

  1. Qualified
  2. Proposal
  3. Contract sent
  4. Closed won

Written by FlowVerify when the last signer finished

  • Note logged on the contactSigned: Supply Agreement 2027 (FV-2611-136), with a link to the document
  • Supply Agreement 2027_signed.pdfStored privately in File Manager and linked from the note
  • Contact fields writtenAgreement status: completed · Signed on: 13 Nov 2026

02Slack

Send From Slack, Review the Draft, Then Confirm

Type /flowverify send with a file or a Drive link, or use the Send for signature shortcut on any message that has a file. FlowVerify drafts the document, places the fields and sends you a link to the Review step.

Nothing goes out until you confirm. /flowverify status shows who has signed, and the notice arrives in Slack when the document is complete.

  1. /flowverify send
  2. Review link in a DM
  3. Signed notice
Slack · FlowVerify app

Shalini Bose10:42

/flowverify send vendor-nda.pdf to Farah Qureshi <[email protected]>, due 20 Nov

FlowVerifyApp10:42

Draft ready: Vendor NDA · Nandi Freight
1 signer, 2 fields placed, due 20 Nov. Nothing is sent until you confirm.
Review and send

FlowVerifyApp11:24

Signed by Farah Qureshi
Vendor NDA · FV-2611-102 · Aadhaar eSign
View document

03Storage

Pick It From Drive, Get the Signed Copy Back

Pick PDFs or Google Docs from Drive, or Word files from OneDrive. Whatever is not a PDF is converted before you place fields.

When the document is complete, one click saves the signed copy to a FlowVerify folder in the same account. Older signed agreements can be brought into the repository the same way.

  1. Import from Drive
  2. Sign
  3. Saved to your folder
My Drive ›FlowVerify
  • Vendor NDA_signed.pdfSaved from FlowVerify · 13 Nov, 11:24New
  • Statement of Work 04_signed.pdfSaved from FlowVerify · 12 Nov, 16:05
  • Offer Letter_signed.pdfSaved from FlowVerify · 10 Nov, 09:48

Imported from Drive: Rate Card 2027, a Google Doc, converted to PDF and ready for fields.

04AI agents

A Conversation Sends, Inside a Mandate

Claude, ChatGPT, Cursor or your own agent connects through the FlowVerify MCP server. An admin issues the mandate: which templates, which actions, which recipient domains, how many sends a day.

A request outside the mandate is refused before anything is certified or emailed. Everything inside it is recorded against the agent, and through it against the person who issued the mandate.

  1. Asked in chat
  2. Mandate check
  3. Audit trail
Claude · mandate “Procurement agent”
3 of 20 sends today

Send the vendor NDA to Farah Qureshi at Nandi Freight.

  • send_from_templateVendor NDA to [email protected]

    Inside the mandate. Previewed, then sent on your confirmation.

    Allowed
  • send_from_templateVendor NDA to an address outside nandifreight.in

    Refused with 403 mandate_limit_exceeded, limit allowed_recipient_domains. Nothing was performed.

    Refused
  • void_envelopeFV-2611-102

    Refused with 403 mandate_limit_exceeded, limit allowed_actions. Nothing was performed.

    Refused

Audit trail: sent by agent “Claude” under mandate “Procurement agent”, issued by Shalini Bose.

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.

WhatsApp · Farah Qureshi's phone
Link only
Kiran Exports Private Limited has sent you “Vendor NDA” to sign. Document FV-2611-102.Review and sign

10:51

STATUS

11:02

“Vendor NDA” is waiting for your signature. Due 20 Nov 2026.Open the document

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.

Signing email
Verified sender
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 & sign

Sent securely with FlowVerify

Forward an Email to Send

Your own words above the forwarded message decide the recipients, the roles and the deadline.

Forwarded email
You confirm first
To
send+7kq2m4x9…@inbound.flowverify.co
Subject
Fwd: Rate revision letter

Send to: Farah Qureshi <[email protected]>

cc: [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.
Settings · Integrations
  • Zoho CRMConnected

    India data centre · connected by Shalini Bose

  • SlackConnected

    Kiran Exports workspace · alerts in #procurement

  • Google DriveConnected

    Shalini Bose’s Drive · signed PDFs to the FlowVerify folder

Recent CRM updates

  • 11:24

    Statement of Work 04envelope.completed

    1 contact matched, deal moved, note logged, 1 PDF attached

    Updated
  • 10:51

    Statement of Work 04envelope.sent

    Deal moved to Contract sent, 3 fields written

    Updated
  • 09:12

    Vendor NDAenvelope.sent

    1 contact created, note logged

    Updated
  • Yesterday

    Franchise Agreementenvelope.declined

    The 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 key
curl -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