Connect Verifycate to Zapier

Zapier is the fastest way to connect certificate activity to the rest of an operations stack without writing code.

What you can automate

Certificate work, next to the tools you already use

Use a Verifycate event as the trigger, or call a Verifycate action from a Zap that starts somewhere else.

Setup

Connect a workspace in a few minutes

1. 01

   Create a scoped API key

   In Verifycate, open Workspace → API Keys and create a key with certificates:read and certificates:write. The key identifies the workspace.

2. 02

   Add the Verifycate app

   In Zapier, add Verifycate to the Zap and paste the API key when asked. Zapier validates the key against the workspace.

3. 03

   Choose a trigger or action

   Pick a Verifycate trigger such as Certificate Issued, or an action such as Add Recipient to Certificate. Map the certificate and recipient fields.

4. 04

   Test and turn on

   Run a test with a real certificate in a test workspace, confirm the fields map correctly, then publish the Zap.

Common questions

What can the Verifycate Zapier app do?

It provides instant triggers for certificate lifecycle and engagement events, and actions to add a recipient, revoke a certificate and replace a revoked certificate. You can also search for a certificate or recipient before an action.

Which API key scopes does Zapier need?

Certificate reads and triggers need certificates:read. Adding, revoking or replacing certificates also needs certificates:write. Create the key under Workspace → API Keys.

Does a Zap run twice for the same certificate?

Verifycate may deliver the same event more than once because failed deliveries are retried. Add a filter or a storage step on the event id when the receiving app is not idempotent.

Is Zapier included on every plan?

Yes. The Zapier connection, webhooks and the REST API are included on every plan. Issuing a certificate uses one credit.