Flowsign connects to anything that can call a REST API or receive a webhook. We have step-by-step guides for four automation platforms, and native connectors are on the way.
One thing to know: something has to make the call. That can be an automation platform, the other tool's own automation feature, or your code.
A public API and webhooks, with guides for four platforms
Everything starts with two building blocks:
- A REST API for making things happen in Flowsign.
- Webhooks for hearing about what happened.
We have written step-by-step guides for:
There is no Flowsign app to install from a marketplace. You catch a Flowsign webhook as the trigger, and call the API with the platform's HTTP step as the action. Any other tool with an HTTP request step and a webhook step works the same way.
From there you reach the thousands of apps those platforms connect to. Some common recipes:
- Launch a package from a template when a CRM deal reaches a stage or a form submission arrives.
- Post to a chat channel when a package completes.
- File the signed PDF and its certificate of completion in your document store.
Webhooks and the REST API, for building your own
Prefer writing code to wiring up a platform? Use the same two building blocks directly.
Webhooks
Webhooks tell your system when something changes. There are 15 events in two families:
- Packages: sent, completed, declined, expired, voided, on hold, resumed, scheduled and deleted.
- Signing sessions: sent, opened, completed, declined, cancelled and reminded.
The practical details:
- Every delivery is signed with HMAC-SHA256.
- Endpoints must be HTTPS, and a workspace can hold up to 20 of them.
- Failed deliveries are retried, and each endpoint has a delivery log.
- You can rotate secrets and send a test event.
REST API
The REST API (v1) is how you make things happen. You can:
- Create packages from PDFs or from a template.
- Send and void packages.
- Download signed PDFs and certificates of completion.
- Manage templates and signing groups.
- Read custom fields.
Requests authenticate with an API key that starts with fsk_. Keys are scoped by role, so a key can do no more than the role it was issued with.
Sign-in and provisioning
Identity is an integration too. Flowsign supports:
- Single sign-on with Microsoft Entra ID over SAML.
- SCIM user provisioning, so people are added and removed in one place.
- Sign in with Google.
On the way
These are native connectors, built into the app so no automation platform sits in between. Today they appear in the app with a Coming soon label.
- Platforms: Slack, Xero, HubSpot and Salesforce.
- Document delivery: SharePoint, Google Drive and OneDrive.
- Contacts: Outlook Contacts, Entra Directory and Google Contacts.
You can already connect Slack, Xero, HubSpot, Salesforce, SharePoint, Google Drive and OneDrive today through the API and webhooks. Use an automation platform or your own code.
How to get started
Connectors, the API, webhooks, single sign-on and custom fields are part of the Enterprise plan. The pricing page shows what each plan includes.
- As an owner, open Settings > Integrations. The integrations page lists every connector with its current status.
- Create an API key if you want to call the API, and a webhook endpoint if you want to receive events.
- Pick your platform in the integration guides and follow the walkthrough for it.
Start with one small flow, such as a chat message when a package completes. Send a test event to check it end to end before you build on it.
