Skip to main content
Certyneo
Make integration

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 verified by Make and available now in the module search, alongside other approved third-party apps.

Verified application on the Make marketplace See the Certyneo application on Make

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 on any of the eleven lifecycle events: creation, sending, viewing, signing, approval, return, resubmission, completion, refusal, cancellation or expiry. Events arrive by webhook, with no polling and 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.

TriggerTriggers when…
Envelope createdA new envelope is created as a draft, before it is sent to any recipient.
Envelope sentAn envelope leaves draft status and goes to its recipients.
Recipient viewedA recipient opens their signing link for the first time, before signing, declining or approving.
Recipient signedA recipient completes their signature. Triggers once per signer, not just at the end.
Approver approvedAn approver validates the envelope and the workflow moves on to the next signer or step.
Envelope returned to senderAn approver sends the envelope back for correction instead of approving it, with their reason.
Envelope resubmittedThe sender edits and resends an envelope that had been returned; every approver goes back to pending.
Envelope signedEvery recipient has signed: the envelope is finalised, with a download link for the signed PDF.
Envelope refusedA recipient refuses to sign the envelope, with the reason given.
Envelope cancelledThe sender cancels the envelope before completion: every pending signing link stops working.
Envelope expiredThe deadline passes before every recipient has signed; the envelope moves to expired status.

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.

15 ready-made Make templates

Every instant Certyneo trigger is covered by at least one public scenario. Install it in your Make organization, connect your accounts, and the scenario runs — nothing to build.

Logging to Google Sheets

Every event becomes a timestamped row you can share with people who have no Certyneo access.

  • Log signed Certyneo envelopes to Google Sheets

    Available in the Make gallery

    Adds a row with the ID, subject, timestamp and signed PDF link as soon as every recipient has signed.

    Certyneo → Google Sheets

    Trigger · Envelope signed

    Open on Make

  • Log new Certyneo envelopes to Google Sheets

    Under review at Make

    Records every newly created envelope, with its sender and recipient count, before it is even sent.

    Certyneo → Google Sheets

    Trigger · Envelope created

    Open on Make

Google Sheets to Certyneo

A row added to the spreadsheet creates and sends the envelope, with the subject, recipient and documents it lists.

  • Create a Certyneo envelope from a new Google Sheets row

    Under review at Make

    Turns each new spreadsheet row into an envelope sent to the listed recipient, with the listed documents.

    Google Sheets → Certyneo

    Open on Make

  • Create a Certyneo envelope from a Google Sheets row and notify Slack

    Under review at Make

    Same flow, plus a Slack confirmation naming the subject and recipient of the envelope that was sent.

    Google Sheets → Certyneo → Slack

    Open on Make

Daily digests

Once a day, the status of every envelope in progress, in a spreadsheet or in Slack.

  • Log a daily digest of Certyneo envelope statuses to Google Sheets

    Under review at Make

    Lists every envelope and its status each day in a tracking sheet, for reporting without opening Certyneo.

    Certyneo → Google Sheets

    Open on Make

  • Post a daily Slack summary of Certyneo envelope statuses

    Under review at Make

    Posts a morning recap of envelopes in progress, grouped by status, to a Slack channel.

    Certyneo → Slack

    Open on Make

Real-time Slack alerts

A message in the channel of your choice at every step of the signing flow, from the first click to a refusal.

  • Post a Slack message when a Certyneo envelope is sent

    Under review at Make

    Tells the channel as soon as an envelope leaves draft and goes to its recipients.

    Certyneo → Slack

    Trigger · Envelope sent

    Open on Make

  • Post a Slack message when a Certyneo recipient opens an envelope

    Under review at Make

    Flags the first time a recipient opens their signing link, with their name and the time.

    Certyneo → Slack

    Trigger · Recipient viewed

    Open on Make

  • Post a Slack message when a Certyneo recipient signs

    Under review at Make

    Announces each individual signature, with the signer's name and address, without waiting for the flow to end.

    Certyneo → Slack

    Trigger · Recipient signed

    Open on Make

  • Post a Slack message when a Certyneo approver approves an envelope

    Under review at Make

    Shows which approver validated the envelope and that the flow moves on to the next step.

    Certyneo → Slack

    Trigger · Approver approved

    Open on Make

  • Alert Slack when a Certyneo envelope is returned to sender

    Under review at Make

    Alerts when an approver sends the envelope back for correction, with their reason.

    Certyneo → Slack

    Trigger · Envelope returned to sender

    Open on Make

  • Post a Slack message when a Certyneo envelope is resubmitted for approval

    Under review at Make

    Lets the channel know that a corrected envelope is back in approval.

    Certyneo → Slack

    Trigger · Envelope resubmitted

    Open on Make

  • Send a Slack message from Certyneo envelope declined

    Under review at Make

    Posts a recipient's refusal, with the reason they gave.

    Certyneo → Slack

    Trigger · Envelope refused

    Open on Make

  • Alert Slack when a Certyneo envelope is voided

    Under review at Make

    Warns that an envelope was cancelled by its sender, with the reason.

    Certyneo → Slack

    Trigger · Envelope cancelled

    Open on Make

  • Alert Slack when a Certyneo envelope expires unsigned

    Under review at Make

    Alerts when an envelope expires before everyone has signed, with its previous status.

    Certyneo → Slack

    Trigger · Envelope expired

    Open on Make

Make reviews each template before it appears in its public gallery. Those still under review become available from the Certyneo page on Make as soon as they are approved. See every Certyneo template on Make

Set up the integration

A few minutes are enough to connect Certyneo to your Make scenarios.

  1. 1

    Add Certyneo to your scenario

    In Make, create a scenario, add a module and search for Certyneo, then pick a trigger, the action or a search.

  2. 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. 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. 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.

Ready to automate your signatures?

Create your Certyneo account, generate an API key and connect it to Make in a few minutes.

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?

Yes. It is verified by Make (the "Verified app" badge) and available now in the module search, for all accounts.

Where do I find the Certyneo templates for Make?

In Make's template gallery, searching for Certyneo, or from the Certyneo page on Make. A template installs into your organization in one click; Make then asks for your Certyneo, Google Sheets or Slack connections.

Which signature events are covered?

Eleven lifecycle events: envelope created, sent, viewed by a recipient, signed by a recipient, approved, returned to sender, resubmitted, completed, declined, voided and expired. Each one is an instant trigger delivered by webhook, with no polling.

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.