Automate your signatures with Make
Connect Certyneo to Google Sheets, Slack, HubSpot, Notion, Airtable and 2,000+ other apps in Make (ex-Integromat). Every signature event can start a scenario, and any module can create an envelope to sign — without writing a line of code.
The Certyneo app for Make is in private beta, available by invitation, and under review for the Make marketplace. Request the invite link from your workspace or through support.
Why connect Certyneo to Make
Make bridges Certyneo and the rest of your stack, with a visual scenario builder loved by European teams. You automate signature follow-up and contract sending without any development.
Instant triggers
Start a scenario as soon as an envelope is sent, signed by a recipient, completed or declined. Events arrive by webhook — no polling, no wasted operations.
Action and searches
Create an envelope from a Certyneo template or from documents already uploaded, send it immediately, fetch an envelope by ID or list them by status.
Zero code
Build your automations in Make's visual editor. No infrastructure to maintain, no webhook to host on your side.
Secured by API key
The connection authenticates with a limited-scope Certyneo API key, which you can revoke at any time from your dashboard.
Available triggers
Each trigger starts a scenario at the exact moment the event happens in Certyneo.
| Trigger | Triggers when… |
|---|---|
| Envelope sent | An envelope leaves draft status and goes to its recipients. |
| Recipient signed | A recipient completes their signature. Triggers once per signer, not just at the end. |
| Envelope signed | Every recipient has signed: the envelope is finalised, with a download link for the signed PDF. |
| Envelope refused | A recipient refuses to sign the envelope, with the reason given. |
Action and searches
Drive Certyneo from any module connected to Make.
Create an envelope
Builds an envelope from a Certyneo template or from documents already uploaded, with its recipients, and sends it immediately if you want.
Get an envelope
Fetches an envelope by its ID, with its status and recipients, to chain other modules.
List envelopes
Paginated list of your envelopes, newest first, with an optional status filter.
Set up the integration
A few minutes are enough to connect Certyneo to your Make scenarios.
- 1
Add Certyneo to your scenario
In Make, create a scenario, add a module and search for Certyneo (invite-only during the beta), then pick a trigger, the action or a search.
- 2
Generate your API key
Open Certyneo → Settings → REST API and create a key with the envelopes and webhooks scopes. Copy it: it is shown only once.
- 3
Build your scenario
Paste the key into the Make connection to link your account, then map the event or envelope fields to your other modules.
- 4
Test and activate
Run the scenario once with real data, check the module output, then activate it. Your automations then run on their own.
Security and compliance
The Make connection relies on the public Certyneo API, with the same level of requirements as the rest of the platform.
- End-to-end encrypted exchanges over HTTPS.
- Limited-scope API keys: grant only necessary permissions.
- Hosted in Europe and GDPR-compliant — Make also offers a European data centre.
- Revoke a key at any time from your dashboard.
Frequently asked questions
Which Certyneo plan do I need to use Make?
A live key (sk_live_…) requires a plan with API access (Standard and above). Free and Personal plans get a sandbox key (sk_test_…) to test the whole flow on test envelopes, with no e-mail sent to signers.
How do I get my API key?
In Certyneo, go to Settings → REST API and create a key with the envelopes:read, envelopes:write and webhooks:write scopes. It starts with sk_live_ (or sk_test_ for the sandbox) and is shown only once: copy it immediately.
Is the app already public on Make?
It is in private beta: Make lets us share it through an invite link while the marketplace review is pending. Request the link through support or from your Integrations settings.
Which signature events are covered?
Envelope sent, recipient signed, envelope finalized and envelope refused. Other events in the envelope lifecycle are exposed by the API and can be added as triggers.
Does my data go through Make?
Only the metadata your automation needs (subject, status, signer e-mails, temporary download link) goes through Make, over encrypted exchanges. Document content is not sent in trigger payloads.
Is the Make integration paid?
Certyneo does not charge extra for the integration. Each run consumes Make operations according to your Make plan (the free plan includes 1,000 per month).
Go further
Automate your contracts today
Connect Certyneo to your favourite tools through Make and let your signatures trigger the rest.