Thinkific Integration
Thinkific can issue TRUE certificates when a student reaches the end
Thinkific already sends a webhook when a student finishes a course. Point that webhook at TRUE and every completion issues a branded, blockchain secured certificate on your own domain, with a permanent verification link the student can share. Thinkific has its own certificate feature; this is what to use when the certificate has to prove something to somebody outside your school.
TL;DR
Thinkific supports webhooks out of the box and fires one when a student reaches full completion of a course. An administrator adds the webhook under the platform's own webhook settings and points it at the address we provide. TRUE receives the course and student details, issues the certificate and delivers it. Setup includes one short mapping step so each Thinkific course lines up with the right certificate on our side, and after that it runs on its own.
- Nothing to build. Webhooks are part of Thinkific, so connecting TRUE is a setting rather than a development project.
- Fires on completion. The event runs when a student reaches the end of the course, not when they enrol.
- Stronger than a file. Thinkific's own certificate is a document; this one is a link anyone can verify.
How does the Thinkific certificate integration work?
Thinkific knows when a student has finished, and its webhook system exists precisely so another tool can act on that. TRUE is the tool on the other end. It takes the completion, issues the certificate against the matching design and sends it to the student, with no export and nobody in the middle.
1
Add the webhook in Thinkific
An administrator opens the webhook settings, chooses the completion event and pastes in the address we provide. It is the same screen Thinkific documents for any other integration.
2
Match your courses once
We line each Thinkific course up with the certificate it should issue. It is done once at setup, and it is why the right course name lands on the right certificate.
3
Certificates issue themselves
When a student completes, the certificate is issued and delivered with a permanent verification link. Nobody has to trigger it.
What does the certificate carry?
The student name, the course, your school and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Student name and course. Taken from the Thinkific completion itself, so it matches your course exactly.
- Your organisation. The certificate is branded as yours and lives on your own domain.
- Date of issue, fixed. Written to blockchain at issuance, which is what makes backdating impossible.
- A permanent verification link. An employer confirms it by opening the link or scanning the QR code, without contacting you.
What has to be in place before it can be switched on?
Administrator access in Thinkific and a certificate design. The administrator part is one webhook. The design is either one we build to your graphic profile or one you adapt yourself from a template, and it is the only part that takes any real decision making.
- Thinkific administrator access, which is what adding a webhook needs.
- The courses you want covered, so the mapping step covers the right catalogue from the start.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a student receive?
A branded, animated certificate delivered by email, on your own domain rather than ours. It carries a QR code and a permanent verification URL, so anyone can confirm it without contacting you, and it goes onto a LinkedIn profile in one click.
- Beautifully designed. Animated, branded and interactive rather than a static PDF.
- A shareable link. One URL that works in an email signature, a portfolio or a CV.
- QR code verification. An employer, a client or a regulator confirms the credential instantly.
- LinkedIn ready. Added to a profile in one click, which puts your name in front of their network.
- Blockchain secured. It cannot be edited, forged or backdated after issue.
How is student data handled?
Thinkific passes the student name, email address and the course details to TRUE, which is what a certificate needs to exist. Nothing else is sent, because nothing else is needed.
TRUE is hosted in the EU, and we sign a data processing agreement with you before anything is switched on.
How much has TRUE issued for organisations like yours?
More than 500,000 documents for over 200 organisations in 15 or more countries, and credentials shared by their recipients have produced over 100 million marketing impressions. These are TRUE platform figures, not third party research.
500K+ Documents issued
200+ Organisations
15+ Countries
100M+ Marketing impressions
Is a Thinkific certificate on its own enough?
Thinkific can already produce a certificate, and for a student who just wants something to keep, that is fine. What it cannot do is let a stranger check it without asking you, and that is the part TRUE adds.
| Capability | Thinkific certificate on its own | Thinkific with TRUE connected |
|---|---|---|
| Proof outside your organisation | The reader has to take it on trust | A permanent verification link anyone can open |
| Tamper proof | No | Yes, written to blockchain at issue |
| Lives on your domain | No | Yes, branded on your own domain |
| LinkedIn shareable | A file to attach | One click add to LinkedIn |
| Effort per participant | Manual handling for anything formal | None, it issues on completion |
| Format | A file the student downloads | A link that stays live and can be checked |
| Analytics | None | Views, shares and verifications tracked |
What do Thinkific administrators ask about this?
Mostly whether it replaces Thinkific's own certificates, what triggers it and whether it needs a developer. It can, full completion, and no.
Does the Thinkific integration have to be built?
No. Thinkific supports webhooks as standard. Connecting TRUE is adding one webhook and pointing it at the address we give you.
Does this replace Thinkific's own certificates?
It can, and most schools let it. Thinkific's certificate is a file the student downloads. A TRUE certificate is a link anyone can open and verify, on your own domain.
What exactly triggers it?
Full completion of the course. A student part way through does not trigger anything.
Do we need a developer?
No. Adding a webhook is an administrator setting. The one technical step, matching courses to certificates, is done by us at setup.
Do participants need a TRUE account?
No. The certificate arrives by email with a unique link. No login, no account and no app.
Can the certificate carry our own design?
Yes. We build the design to your graphic profile, or you adapt one from an existing template. The certificate is branded as yours and lives on your own domain.
Can we issue certificates for courses that already finished?
Yes. Earlier completions can be issued as a batch, so a backlog does not have to be handled by hand.
What does a recipient do with the certificate?
Share it. It is a link rather than a file, so it goes on a LinkedIn profile in one click and into an email signature or CV, and every share points back to a verification page carrying your name.
Ready to switch it on?
We prepare your certificate design and give you the address for the webhook, and the next student who finishes receives a verifiable credential.