--- title: "Certifier Integration" description: "Connect AI agents to Certifier, a digital certificate and badge platform. Agents create credentials from templates, issue and send them to recipients, and revoke them when needed so credential delivery follows course completions automatically." url: https://flowrunner.ai/integrations/certifier date_modified: 2026-08-12T15:40:33-07:00 --- # Certifier [Documents](https://flowrunner.ai/integrations/category/documents-forms) Connect AI agents to Certifier, a digital certificate and badge platform. Agents create credentials from templates, issue and send them to recipients, and revoke them when needed so credential delivery follows course completions automatically. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · API key · available [Certifier website](https://certifier.io/) · [Platform Documentation](https://certifier.io) · Capability data verified 2026-08-11 1. A learner is marked complete in the training system 2. Agent reads the recipient name, email, course title, and completion date from the source record 3. Agent calls Get Design to confirm the design's merge fields all have a value to fill them 4. Agent calls Create Credential to draft the certificate inside the correct credential template 5. Agent reads the draft back with Get Credential and compares the rendered attributes to the source record 6. The program owner approves the drafted batch in Slack, and the agent then calls Issue Credentials and Send Credentials ## What This Integration Enables Certifier is built around a draft state, and that is the most useful thing about it for an agent. A credential starts as a draft, becomes issued when it is activated, and only then gets emailed and given a public verification page. FlowRunner agents work that lifecycle end to end: read a design to learn which merge fields it exposes, draft a credential with those fields populated from a source system, correct the draft while correction is still free, then issue, send, and if something later invalidates it, revoke. The draft state matters because a credential is a claim someone else will check. It goes on a resume, a LinkedIn profile, a regulator's file. FlowRunner agents can run the whole pipeline without a person touching it, and the platform default is that they stop before the step that makes the claim public. That is the shape of [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) work: the agent handles the drafting, the lookup, the merge field checks, and the delivery, and a person owns the one decision that cannot be walked back cleanly. ### Without FlowRunner **Certificates issued by hand**: Someone types names into a design one at a time after each cohort closes **Errors surface after delivery**: A misspelled name is discovered when the recipient replies, not before the send **No link to the completion record**: The certificate and the training record live in two systems with nothing tying them together ### With FlowRunner **Drafted from the source record**: Every credential is built from the completion record that justified it **Checked while it is still a draft**: The rendered merge fields are reviewed before the credential exists publicly **Issued on completion**: Delivery follows the training record instead of waiting for a batch day ## Use Case Scenarios ### Course completion to credential A learner finishes a course in [Moodle](https://flowrunner.ai/integrations/moodle) or [Thinkific](https://flowrunner.ai/integrations/thinkific). The agent reads the completion record, calls Get Design to discover which merge field keys that design accepts, and calls Create Credential with the recipient details and the custom attributes that fill those keys. The credential sits in draft. Once the program owner approves the day's batch, the agent calls Issue Credentials and then Send Credentials, and writes the credential ID back onto the learner record so the training system and the credential stay linked. ### Compliance training with an expiry clock Annual safety or privacy training carries an expiry date. The agent sets the issue and expiry dates on the credential at creation time and stores the credential ID alongside the employee record in [BambooHR](https://flowrunner.ai/integrations/bamboohr). Ninety days before expiry, a second flow calls List Credentials filtered to that template, finds everything approaching its expiry date, and opens a re-training task. When an employee leaves the role the certification covered, the agent calls Revoke Credentials so the public verification page reflects reality rather than a stale claim. ### Partner certification at scale A partner enablement team certifies resellers. The agent pulls the newly qualified partners from [HubSpot](https://flowrunner.ai/integrations/hubspot), calls List Credential Templates to resolve the right template for the certification level, and drafts one credential per partner. Where a partner record is missing an email or a required attribute, the agent does not guess and does not skip silently. It collects those into an exception list and puts them in front of the enablement owner, who fills the gaps before anything is issued. The clean records move on to Issue Credentials and Send Credentials in one batch. ## Human-in-Loop Highlight The gate sits exactly where Certifier's own lifecycle puts the point of no return. Update Credential and Delete Credential work only on drafts. Once a credential is issued, the only correction available is Revoke Credentials, which does not remove the credential and does not un-send the email. It leaves the credential in the account flagged as revoked on its public verification page, which is a visible retraction of a document the recipient may already have shared. So when a batch is drafted and the agent finds something it cannot resolve, it stops and posts to the program owner: "38 credentials drafted from the Data Science Practitioner template. On 2 of them the course.name merge field resolved empty, and 1 recipient email bounced validation. Issue and send the 35 clean ones and hold the 3, issue all 38, or cancel the batch?" The owner picks. The agent resumes on that answer, and the three exceptions get fixed while fixing them is still free. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Credentials 9 - **Create Credential** Drafts a single certificate or badge for a recipient inside a credential template, with custom attributes filling the merge fields the design defines. The credential is not issued or delivered by this step, which is what makes it safe to run automatically. - **Create, Issue and Send Credential** Creates, issues, and emails a credential in one call. Use it when the eligibility data is already trustworthy and the recipient email is known, for example a self-serve course where completion is unambiguous. - **List Credentials** Returns credentials with cursor pagination, optionally filtered to one template. Used for expiry sweeps, reconciliation against the source system, and reporting on who holds what. - **Get Credential** Retrieves one credential including its status, recipient, issue and expiry dates, custom attributes, and public sharing details. Used to read a draft back before it is issued. - **Update Credential** Changes the recipient details, dates, or custom attributes on a draft credential. Only drafts can be updated, so this is the correction step that has to happen before issuing. - **Delete Credential** Permanently removes a credential. Used to clear drafts created in error. It is not the tool for an issued credential. - **Issue Credentials** Activates one or more draft credentials and generates the shareable certificate or badge. This is the step that makes the credential real, and it is the natural place to put an approval. - **Send Credentials** Emails issued credentials to their recipients through Certifier's delivery system. Used after issuing, or skipped entirely when the credential is delivered through another channel. - **Revoke Credentials** Marks issued credentials as no longer valid, keeping them on record and flagging them on their public verification page. Used when a certification lapses, a course result is overturned, or a holder leaves the role it covered. ### Credential Templates 2 - **List Credential Templates** Returns the credential templates in the account with cursor pagination. Used to resolve which template a given course or certification level maps to before drafting. - **Get Credential Template** Retrieves a single template with its name, design, and the defaults applied when credentials are created from it. ### Designs 2 - **List Designs** Returns the designs available, each being the visual layout and branding a template renders. - **Get Design** Retrieves a design including the merge fields it exposes. Used before drafting so the agent knows exactly which custom attribute keys the credential will accept, rather than discovering a mismatch after delivery. ## Frequently Asked Questions ### What can FlowRunner do with Certifier? FlowRunner agents can run Create Credential, Create, Issue and Send Credential, and List Credentials in Certifier, plus 10 more actions. ### Does connecting Certifier to FlowRunner require OAuth? No. Certifier connects to FlowRunner with an API key, no OAuth flow required. ### Can Certifier trigger a FlowRunner workflow automatically? Certifier doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Certifier?** This integration exposes Certifier 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/certifier. Site index: https://flowrunner.ai/llms.txt