# Automate certificates with Zapier or Make Send a certificate automatically whenever something happens in the tools you already use — a row added to a Google Sheet, an Eventbrite attendee, a form submission. No code. Setup takes about five minutes, and every certificate you send this way is rendered, emailed to the recipient, and given a public verification page, exactly like one sent from the dashboard. ## What you need 1. A CERTPRODUCT account (any plan — the API is included at every tier). 2. An **API key with `issue` scope** (dashboard → API Keys → Create key). Copy it somewhere safe; it is shown only once. Every automation below ends in the same step: an HTTP **POST** to ``` https://YOUR-CERTPRODUCT-DOMAIN/v1/certificates ``` with these headers: ``` Authorization: Bearer YOUR_API_KEY Content-Type: application/json Idempotency-Key: ``` and a JSON body like this (copy, paste, then map your fields into it): ```json { "template": "classic", "recipient_name": "Ada Lovelace", "recipient_email": "ada@example.com", "program_title": "Spring Workshop Series", "issue_date": "2026-11-14", "custom_line": "12 continuing education credit hours" } ``` | Field | Required | Notes | |---|---|---| | `template` | no | One of `classic`, `modern`, `minimal`, `corporate`, `elegant`, `playful`, `midnight`, `appreciation`. Defaults to `classic`. | | `recipient_name` | **yes** | Printed on the certificate. | | `recipient_email` | **yes** | The certificate is emailed here. | | `program_title` | **yes** | The course / workshop / event name printed on the certificate. | | `issue_date` | no | `YYYY-MM-DD`. Defaults to today. | | `custom_line` | no | Optional extra line, e.g. hours or CE credits. | | `issuer_name` | no | Defaults to your account's business name. | | `signature_name` / `signature_title` | no | Signature block on the certificate. | A successful call returns `201` with the certificate, including `verification_url` (the public page the QR code opens) and `delivery.status` (the email's delivery state). Each issued certificate uses **1 credit**. ## Recipe 1 — Google Sheets: new row → certificate Good for: class lists, training rosters, sign-in sheets. 1. In Zapier, create a Zap. Trigger: **Google Sheets → New Spreadsheet Row**. Pick your spreadsheet and worksheet. Your sheet needs columns for at least the recipient's **name** and **email**. 2. Action: **Webhooks by Zapier → POST**. - URL: `https://YOUR-CERTPRODUCT-DOMAIN/v1/certificates` - Payload Type: `Json` - Data: add `recipient_name`, `recipient_email`, `program_title` (type the program name once, or map a column), and any optional fields. Map the name/email values from the trigger row. - Headers: `Authorization` = `Bearer YOUR_API_KEY`, and `Idempotency-Key` = the row's unique value (use the Sheets **Row ID** field from the trigger, e.g. `sheet-{{Row ID}}`). 3. Test the Zap, check the recipient's inbox, then turn the Zap on. ## Recipe 2 — Eventbrite: attendee → certificate Good for: workshops, conferences, ticketed classes. 1. Trigger: **Eventbrite → New Attendee** (or "Attendee Checked In" if you only certify people who actually showed up). 2. (Optional) Filter step: only continue for the event(s) you certify. 3. Action: **Webhooks by Zapier → POST**, same URL and headers as above. Map `recipient_name` ← attendee name, `recipient_email` ← attendee email, type `program_title` as your event's certificate title, and set `Idempotency-Key` to the Eventbrite **Attendee ID** so a re-run never double-issues. ## Recipe 3 — Typeform (or Google Forms): submission → certificate Good for: post-course evaluations, completion forms, quizzes. 1. Trigger: **Typeform → New Entry** (Google Forms: **New Form Response**). 2. Action: **Webhooks by Zapier → POST**, same setup. Map the name and email answers from the form; `Idempotency-Key` ← the form's **Response ID**. ## Make.com variant Create a scenario with your trigger module (Google Sheets "Watch Rows", Eventbrite "Watch Events/Attendees", Typeform "Watch Responses"), then add an **HTTP → Make a request** module: - URL: `https://YOUR-CERTPRODUCT-DOMAIN/v1/certificates` - Method: `POST` - Headers: `Authorization: Bearer YOUR_API_KEY`, `Content-Type: application/json`, `Idempotency-Key: ` - Body type: `Raw` → `JSON`, body = the JSON above with your module's fields mapped in. ## Avoiding duplicates Zapier and Make sometimes re-run steps. The `Idempotency-Key` header makes re-runs safe: send the same key with the same details and you get the original certificate back — no second email, no second credit charged. Use something unique per recipient-event: an attendee ID, a form response ID, or `sheetname-rownumber`. Reusing a key with *different* details returns a `409` error instead of guessing. ## Troubleshooting | Response | Meaning | Fix | |---|---|---| | `201` | Certificate issued and emailed. | — | | `200` | Idempotent replay — this certificate already existed. | — | | `400 validation_error` | A field is missing or malformed; the `message` says which. | Fix the mapping (most often: email column empty). | | `401 unauthorized` | Missing or wrong API key. | Re-copy the key; check the `Bearer ` prefix. | | `402 insufficient_credits` | You're out of certificates for this period. | Upgrade in the dashboard, or wait for the period to reset. Nothing was charged. | | `409 idempotency_conflict` | That Idempotency-Key was used for a different certificate. | Use a fresh unique key per recipient. | ## Prefer a one-off batch? For a one-time list (a whole class at once), skip automations: upload a CSV in the dashboard (Bulk Issue), or `POST /v1/batches` — see the README's API table. Rows that can't be issued come back with plain-language explanations, and you're only charged for the rows that succeed.