--- title: "IssueBadge Integration" description: "Connect AI agents to IssueBadge, the digital badge and certificate platform. Agents create badge templates and issue badges with public verification URLs so recipients get credentials the moment they earn them." url: https://flowrunner.ai/integrations/issuebadge date_modified: 2026-08-12T15:40:33-07:00 --- # IssueBadge [Documents](https://flowrunner.ai/integrations/category/documents-forms) Connect AI agents to IssueBadge, the digital badge and certificate platform. Agents create badge templates and issue badges with public verification URLs so recipients get credentials the moment they earn them. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 4 actions · API key · available [IssueBadge website](https://issuebadge.com/) · [Platform Documentation](https://issuebadge.com/h/developer) · Capability data verified 2026-08-11 1. A learner passes the final assessment in the customer education platform 2. Agent reads the learner name, email, score, and completion date 3. Agent calls List Badges to resolve the badge template that matches the course and level 4. Agent confirms the learner appears on the approved eligibility list for that badge 5. Agent posts the day's eligible recipients to the program owner with the score that qualified each one 6. Program owner confirms the list, and the agent calls Issue Badge for each approved recipient ## What This Integration Enables IssueBadge does one thing and the connector is honest about it: four operations covering badge templates and issuance. An agent can validate its credentials, list the badge templates the organization has defined, create a new template from a logo and a set of custom fields, and issue a badge to a named recipient. Issuance emails the recipient when an email address is supplied and always mints a public verification URL. A four-action surface is a thesis, not a limitation. IssueBadge is for programs where the badge is a public claim rather than an internal reward, and where the value comes from the verification link surviving long after the course platform has been replaced. FlowRunner agents put the badge on the completion event instead of on a monthly batch job, which is where badges actually earn engagement. What they do not do is decide who deserves one when the eligibility signal is ambiguous. That is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) by design, and on this connector it is not optional, for the reason below. ### Without FlowRunner **Badges issued in bulk after the fact**: A coordinator exports completions monthly and works through them by hand **Eligibility checked loosely**: The list comes from a spreadsheet that has been edited by several people **No verifiable proof**: Recipients get a graphic they cannot prove anything with ### With FlowRunner **Issued as work is completed**: The badge follows the completion event rather than a calendar **Eligibility confirmed before issuance**: The recipient list is reviewed by the person accountable for the program **Publicly verifiable**: Each issued badge carries a verification URL anyone can check ## Use Case Scenarios ### Certification on assessment pass A customer education program runs in [LearnWorlds](https://flowrunner.ai/integrations/learnworlds) or [Teachable](https://flowrunner.ai/integrations/teachable). When a learner passes the final assessment, the agent calls List Badges to resolve the right badge for the course, then calls Issue Badge with the recipient's name and email and the assessment score in the metadata object. The recipient gets the notification email and a verification URL. The agent writes the badge ID and verification link back onto the customer record in [HubSpot](https://flowrunner.ai/integrations/hubspot) so the success team can see which accounts have certified users. ### Launching a new badge program A team is standing up a new certification tier. The agent calls Create Badge with the logo image URL, an expiration date matching the recertification cycle, organization branding, and the custom fields the program needs, for example completion date, score, and instructor. It then confirms the template appears in List Badges and posts the new badge ID into the program channel in [Slack](https://flowrunner.ai/integrations/slack) so downstream flows can reference it. The template is built once and reused by every issuance flow afterward. ### Partner tiering with an expiry clock Reseller partners earn a badge when they complete accreditation, and the badge carries an expiration date. The agent issues on accreditation and records the expiry alongside the partner record in [Pipedrive](https://flowrunner.ai/integrations/pipedrive). A separate scheduled flow reads that field, and ninety days out it opens a recertification task and notifies the partner manager. Because IssueBadge exposes no event endpoint, the timing lives in the flow rather than in the badge platform. ## Human-in-Loop Highlight Every other credential connector in the catalog gives an agent a way to take something back. This one does not. The IssueBadge public API exposes badge creation and issuance, and no revoke, no delete, and no update on an issued badge. The moment Issue Badge succeeds, the recipient has an email and a public verification URL that will keep resolving. The idempotency key stops a duplicate issuance; it does nothing about a wrong one. So the gate is placed on the eligibility list rather than on the delivery mechanics, and it sits before the first call rather than after a batch has gone out. When a cohort's completion data comes from a source the agent cannot fully trust, for example a manually edited roster or a course platform where an admin can mark completions by hand, the agent assembles the recipient list, attaches the qualifying evidence for each person, and asks the program owner in Slack: "18 learners qualify for the Advanced Practitioner badge. 3 were marked complete by an admin rather than by an assessment score. Issue all 18, issue the 15 with assessment evidence, or hold the batch?" Then it issues exactly what was approved, because that is the only chance to get it right. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 4 actions ### Connection 1 - **Validate API Key** Checks the configured IssueBadge API key and returns whether it is valid along with the associated user and tenant identifiers. Used as a connection test at the start of a flow or after credentials rotate. ### Badges 3 - **List Badges** Returns the badge templates available to the organization with their IDs and names, up to 100 per request. Used to resolve which badge a course, tier, or achievement maps to before issuing. - **Create Badge** Creates a new badge template from a public logo image URL, with optional expiration dates, organization branding, and custom fields. Used when a new certification or recognition program is stood up, rather than on every issuance. - **Issue Badge** Issues a badge to a recipient, emailing them when an address is provided and creating a public verification URL. Custom field values ride along in the metadata object. This is the irreversible step, and it is where the approval belongs. ## Frequently Asked Questions ### What can FlowRunner do with IssueBadge? FlowRunner agents can run Validate API Key, List Badges, and Create Badge in IssueBadge, plus 1 more action. ### Does connecting IssueBadge to FlowRunner require OAuth? No. IssueBadge connects to FlowRunner with an API key, no OAuth flow required. ### Can IssueBadge trigger a FlowRunner workflow automatically? IssueBadge doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at IssueBadge?** This integration exposes IssueBadge to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/issuebadge. Site index: https://flowrunner.ai/llms.txt