CertSeal for Make.com

The CertSeal app for Make.com (formerly Integromat) brings certificate issuance and a certificate-viewed trigger into your scenarios. It uses the same REST API and API-key authentication as our Zapier app.

Availability. The CertSeal Make app is currently provided as a custom app while we complete the public Make Marketplace listing. To get access, email support@certseal.com. You can also use CertSeal in Make today with the built-in HTTP and webhook modules — see Using CertSeal in Make today.

Before you start

You’ll need:

• A CertSeal account with a certificate batch and design already created.
• A CertSeal API key. In CertSeal, open Settings → API keys and create a key. Copy it immediately — the token (it starts with csk_live_) is shown only once.
• A Make.com account.

Authentication

Create a CertSeal connection in Make and paste your API key. Make verifies it and labels the connection with your workspace username. There’s no OAuth step — the same key authorizes every module.

Modules

Trigger

• Watch Viewed Certificates — an instant trigger that runs the moment a recipient opens their certificate for the first time. Make registers a webhook with CertSeal, so scenarios run as the event happens.

Action

• Issue Certificate — create one recipient in a batch, with an option to send the certificate email immediately. Fields include the target Batch, Name, Email, an optional Certificate ID, Issue/Expiry Date, a Send toggle, and a Data object of template variables. A batch dropdown lets you pick a batch without copying its ID.

Using CertSeal in Make today

While the public listing is pending, you can wire CertSeal into Make right now:

• HTTP module. Call the CertSeal REST API directly with Make’s HTTP module — set the Authorization: Bearer header to your API key.
• Custom webhook + subscription. Create a Make Custom webhook, copy its URL, then subscribe it to CertSeal events (see Webhooks). Events arrive instantly with the same signed payload the custom app uses.

Removing the app

• Stop a scenario: turn off or delete the relevant Make scenario. Instant triggers remove their CertSeal webhook subscription automatically when the scenario is turned off.
• Revoke all access: in CertSeal, open Settings → API keys and delete the key your Make connection uses. Any scenario relying on that key stops working immediately.

Certificates already issued remain valid; revoking a key only prevents future issuance.

Support

Need access or help wiring CertSeal into Make? Email support@certseal.com — we typically reply within 1 business day (Monday–Friday, 9:00 AM–6:00 PM SGT). See the support guide for all contact options.