Issue certificates from Lindy agents

Lindy builds AI employees that run tasks, routines and conversations for your team. Connect the IssueBadge MCP server once and every Lindy you choose can issue verifiable certificates and badges, return the verification link, and manage dynamic QR codes.

  • No code: Lindy adds the server by URL; IssueBadge signs you in with OAuth 2.1, no API key to paste
  • Nine actions appear in Lindy the moment you connect: templates, issuing, QR codes
  • Routines can issue certificates on a schedule or when something happens, with duplicate protection
  • Guardrails: require approval before a certificate is issued, per person or per workspace
Connect in 5 steps About the MCP server

Lindy: "Course completion certificates"

Routine · every Friday 5 pm

TriggerWeekly routine
ActionIssueBadge · issue_badge
RecipientJane Doe (from the completions sheet)
Result✓ Issued & emailed · verification link posted

✓ The Lindy issued the certificate, posted the verification link in the thread, and skipped people who already had one.

What a Lindy can do with IssueBadge

Anything you would do in the IssueBadge dashboard, triggered by chat, a schedule or an event in another connected tool.

Course and workshop completions

A Lindy watches your LMS, form or spreadsheet and issues the completion certificate to each learner, then emails or messages them the link.

Event attendance

After a webinar or meeting, the Lindy takes the attendee list from Zoom, Calendly or a sheet and issues attendance certificates in one pass.

Recognition and onboarding

Ask in chat: "Issue the Employee of the Month badge to Sam Lee". The Lindy confirms the template and recipient, issues it, and shares the verification page.

Connect IssueBadge to Lindy in 5 steps

About three minutes. You need a Lindy workspace and an IssueBadge account with at least one certificate template.

1

Open Integrations and add an MCP server

In Lindy, open Integrations, click + Add and choose MCP. The other option, Integration, is for Lindy's built-in tools; IssueBadge connects as an MCP server.

2

Enter the server URL and a display name

In Connect MCP server, paste the server URL and give it a display name, otherwise the connection only shows the hostname.

Server URL:    https://issuebadge-mcp.issuebadge.workers.dev/mcp
Display name:  IssueBadge
3

Sign in to IssueBadge

Click Connect. The IssueBadge server runs its own sign-in (OAuth 2.1 with PKCE and automatic client registration), so leave Advanced empty: a browser window asks you to sign in to IssueBadge and approve the read and write scopes once.

Prefer a key, or Lindy did not open the sign-in? Open Advanced, choose Authorization as a bearer token, and paste an API key from app.issuebadge.com, Developer, API key. Either way the credential only ever travels to app.issuebadge.com.

4

Check the tools and set guardrails

The connection lists the tools the server reports and the tools available in Lindy; both should show 9. Nine tools arrive: validate_key, get_all_badges, issue_badge, and six dynamic QR code tools (create_qr_code, list_qr_codes, get_qr_code, update_qr_code, get_qr_code_scans, delete_qr_code).

In the Actions card you can disable any tool, for example the QR tools if you only issue certificates. Under Availability choose Your workspace so other Lindies can use it, and under Guardrails set Ask for approval for issue_badge if you want a human to confirm before a certificate is emailed.

5

Give the actions to a Lindy

Open or create a Lindy, add the IssueBadge actions, and try it in chat: "Which certificate templates do I have?" then "Issue the Certificate of Completion to Jane Doe, jane.doe@example.com". The Lindy lists your templates, issues the certificate, and replies with the public verification link.

How to use it well

The MCP server is stateless and the tools are plain, so the quality of the result comes from how you brief the Lindy.

Prompts that work

  • "List my IssueBadge templates" → get_all_badges
  • "Issue the Certificate of Appreciation to Jane Doe, jane.doe@example.com, expiring in two years" → issue_badge with expire_date
  • "Issue the Workshop Attendance certificate to everyone in this sheet" → one issue_badge call per row with an idempotency key per person
  • "Create a QR code that points to our event page, I will change it later" → create_qr_code; update_qr_code retargets it without reprinting

Add this to the Lindy's instructions

When asked to issue a certificate:
1. Call get_all_badges and pick the template whose name matches. If unsure, ask.
2. Confirm the recipient's full name and email before issuing; the email cannot be recalled.
3. Call issue_badge with badge_id, name, email and idempotency_key = badge_id + email + today's date,
   so a rerun never issues a duplicate.
4. Reply with the certificate_url. Never invent template ids or recipient details.

The same guidance is packaged as an installable skill at github.com/issuebadge2026/issuebadge-skills.

Routines and triggers

Put the issuing step in a Routine (every Friday, or when a row is added to a sheet, a form is submitted, or a Zoom meeting ends). Keep the idempotency key rule in the instructions and the routine is safe to rerun. Point a Lindy at the returned certificate_url to post it in Slack, add it to a CRM record, or email it with a personal note.

Frequently asked questions

Do I need an IssueBadge API key for Lindy?

No. Add the server URL with nothing under Advanced and Lindy opens the IssueBadge sign-in. An API key as a bearer token under Advanced is the alternative if you prefer a key.

Which Lindy plan does this need?

Any Lindy workspace that can add MCP servers under Integrations. Issuing certificates needs an active IssueBadge plan; see the pricing page.

Can several Lindies share one connection?

Yes. Set Availability to Your workspace. Guardrails are personal, so each user can still require approval before issue_badge runs.

Will a rerun issue duplicate certificates?

Not if the Lindy sends an idempotency key per recipient. The API returns the existing credential for a repeated key instead of issuing again.

Is anything stored on the MCP server?

No. It forwards each call with your token to app.issuebadge.com and keeps nothing. Disconnecting in Lindy ends access.

Where do recipients see their certificate?

They get an email from IssueBadge, or from your own SMTP server if configured, with the certificate and a public verification page at app.issuebadge.com/v/{id}.

Last updated 10 October 2026. Written by the IssueBadge engineering team, who run the MCP server. Questions: contact us.

Your AI employee, now a credential issuer

Connect once. Every Lindy you choose can issue verifiable certificates from chat, routines and triggers.

Start free with IssueBadge