Certifier Integration Approvals & Automation
Run Certifier on autopilot. Keep the veto.
9 actions
Credentials go out to the wrong recipients before you can spot the mistake. Rills proposes each issue and send, you approve from your phone before anything ships.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential communication action from Certifier arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Send 23 certificates to group 'Summer 2024 Graduates'?
3 recipients missing email addresses
Design: Standard Blue (version 2)
Scheduled delivery tomorrow 9am
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Certifier automation
You schedule a batch of certificates for a course completion, and they land in the wrong inboxes. A colleague's name is misspelled, or a credential goes to someone who never finished. By the time you see the support email, the damage is done.
When Certifier runs unsupervised
A credential send is a one-way door. Once it's out, pulling it back is awkward and damages trust. Here is what happens when issue and send operations fire without a second set of eyes:
- Create and issue credential: A new certificate is issued automatically with the wrong template or missing fields, leading to a retraction request.
- Send a credential: The email goes to a stale address you thought was updated, and the recipient never receives their achievement.
- List email templates: A revised template gets deployed before you've reviewed its placeholder text, so all new credentials carry a broken link.
- Search credentials: An accidental search exposes internal naming conventions or triggers a bulk action you didn't intend.
- List groups: A group membership change goes unnoticed, and the next batch of credentials misses half the intended recipients.
What Rills does inside Certifier
Rills watches over your Certifier account by polling for pending batches, scheduled sends, and template updates. For operations like issuing a credential to a group or sending a single certificate, Rills proposes the action first and waits for your approval. You review the recipient list, the design choice, and the delivery timing on your own terms.
Credentials still go out; you just see each one before it leaves your hands.
Why Certifier has no triggers and how Rills fills the gap
Certifier does not emit webhooks or events when credentials are created, issued, or sent. That means you cannot rely on real-time triggers to catch mistakes. Rills compensates by running scheduled checks and responding to upstream events from other tools. Here is how:
- Polling for pending credentials: Every few minutes, Rills checks for new credentials waiting to be issued and surfaces them for your approval.
- Scheduled batch release: You set a daily or weekly window to review all queued credentials, approve the ones that look right, and delay or reject the others.
- Upstream event from your CRM: A new course completion in your learning platform triggers a credential issue request through Rills. The credential is created but not sent until you approve from your phone.
- Template change detection: Rills periodically lists email templates and designs. If a template was edited outside normal hours, Rills flags it and asks whether to use the new version or keep the old one.
What Rills can do in Certifier
4 of 9 actions across reads, writes, and updates.
- 01
Create, issue, and send credential
Instantly create and deliver a digital credential to a recipient, streamlining the process of issuing certificates, badges, or qualifications in one seamless action.
- 02
List Credentials
Retrieve all stored credentials from your account with pagination support, allowing you to view and manage all authentication details you've saved.
- 03
Search Credentials
Find and retrieve specific credentials from your database using filters like status, recipient, issue date, and other properties. This helps you quickly locate certificates or digital credentials that meet your specific criteria without manually reviewing all records.
- 04
Send a Credential
Distributes a published credential to recipients via email, allowing you to share certifications, badges, or achievements directly with credential holders or stakeholders.
Common questions about Certifier automation
How do I automate sending certificates from my Certifier account?
You set up a Rills workflow that proposes sending credentials. Rills lists your templates and recipients, then waits for you to approve each send from your phone. Nothing goes out until you swipe. Approvals and logic are free; you only pay when the credential actually ships.
Can I get mobile approvals before Certifier issues a credential?
Yes. Rills proposes the issue action with all details. You review and approve from your phone before any credential is created or sent. No AI ships unsupervised. The approval queue is mobile-friendly, so you can veto a batch before it fires.
How do I set up Rills to issue a credential when someone completes a course in another tool?
Rills watches for completion events from your course platform (like Teachable or Thinkific). It proposes a Certifier issue action with the learner's details. You approve on your phone before the credential ships. No automated handoffs without your call.
Can I have Rills search Certifier credentials and notify me of expiring ones without shipping anything automatically?
Yes. Rills can search credentials and send you a notification with the list. No credentials are modified or sent without your approval. The action only proposes what to do next. You decide from the queue on your phone.
How do I automate listing all Certifier designs and selecting one to issue?
Rills fetches your designs and presents them in the approval queue. You pick which design to use, then Rills proposes the issue action with that design. You approve on your phone before the credential goes out. No design is chosen without you.
How is Rills different from Zapier for Certifier automation?
Zapier fires actions the moment a trigger happens. Rills holds every Certifier action in an approval queue first. You review from your phone, swipe to approve or deny. Nothing ships without you. Also, approvals and workflow logic are free; you only pay for executed Certifier calls.
Does Rills support Certifier webhooks to trigger workflows?
Rills does not listen for Certifier webhooks directly. Instead, you connect other tools that fire events (like Stripe or a course platform) to trigger proposals. Those proposals then include Certifier actions like issue or send. You approve each proposal before it runs.
How much does Rills cost for Certifier automation?
Approving actions and building workflow logic are free. You only pay for real Certifier API calls and external operations when they execute. No monthly seat fees for the approval queue. Your wallet stays safe unless you approve a credential to ship.