Create an API key
Open Settings, then API keys. Name the key, pick the role it acts as and the workspaces it works in. The key is shown once.
Signing that fits into the tools you already use.
Send packages from your other systems and hear back when they are signed. Flowsign connects through a REST API and webhooks, with guides for Zapier, Make, n8n and Power Automate.
Coming soon
Two pieces, any tool. The API sends packages. Webhooks tell your systems what happened next.
Guides for four automation platforms. Step-by-step guides for Zapier, Make, n8n and Power Automate. Each uses the platform's own webhook and HTTP steps, so there is no Flowsign app to install.
Send packages from other systems. Create a package from a published template, name a recipient for each role, fill the merge fields, and send it now or schedule it.
Webhooks when something happens. Flowsign posts to your URL when a package is sent, completed, declined, voided or expired, and when a recipient opens, signs or declines.
API keys with a role. Each key acts with the permissions of the role you pick, in the workspaces you choose. Set an expiry date, and revoke a key at any time.
Signed copies where you keep records. Download the signed documents as one PDF or a zip, along with the certificate of completion, and file them in your own system.
Docs your AI assistant can read. The docs are published as an MCP server and as plain text, so an assistant can look up endpoints and webhook events for you.
How it works. From API key to a signed package in three steps.
01
02
Send from your system
Your automation or your own code calls the API with a template and its recipients, and Flowsign sends the package.
03
Hear back when it is signed
Add a webhook endpoint in Settings and tick the events you want. Flowsign posts to it as each package moves along.
Watch how it works
All videos- Coming soon
Connecting Zapier, Make and n8n
Where integrations live and how to connect your automation tool.
Read the guide - Coming soon
Setting up SSO, API keys and webhooks
Where single sign-on, API keys and webhooks live in settings.
Read the guide
Frequently asked questions
The API and webhooks are included on the Enterprise plan. Creating an API key or a webhook endpoint also needs the matching permission on your role, which an owner can give you. See pricing for details.
No. The guides use each platform's own webhook and HTTP steps, with a Flowsign API key and a webhook endpoint. Some platforms keep those steps for their paid plans.
Yes, if something can make the call. Any automation platform, or your own code, that can make an HTTP request or receive a webhook can connect to Flowsign through the same API and webhooks.
Every delivery is signed with a secret that belongs to your endpoint, so the receiver can check it. Failed deliveries are retried, and each endpoint has a delivery log kept for 30 days.
Not through the docs connection. The docs MCP server and text exports are read-only, so an assistant can look things up but cannot see your workspace or send anything. To let an agent act in Flowsign, give it the REST API with an API key.
More from Flowsign
Workflows. Answers decide documents and signers.
Explore workflowsBulk send. One template, hundreds of packages.
Explore bulk sendSigning. Sign on any device.
Explore signing