Zapier Integration
Connect almost anything to TRUE with Zapier, without writing code
If your platform is not one we have a page for, Zapier is usually the shortest way in. Zapier connects to thousands of apps, and its HTTP action can call TRUE with the details of whoever just finished. That means a completion in almost any system can issue a branded, blockchain secured certificate, and you build it by clicking rather than coding.
TL;DR
Zapier is not a learning platform, it is the wiring between platforms. You build a Zap where the trigger is an event in your system, a course completed, a form submitted, a row added, and the action is an HTTP request to TRUE carrying the person's details mapped from that trigger. Your TRUE token is stored in Zapier as a credential rather than typed into each step. It is the fastest way to test the idea before committing to a deeper connection, and for many organisations it is also the permanent answer.
- Works with what you already have. If your system is one of the thousands Zapier connects to, this route is open to you today.
- No code. The trigger and the mapping are built in Zapier's own editor.
- Good for trying it out. A Zap is quick to build and quick to change, which makes it the right first step when nobody is sure yet what should issue.
How does the Zapier certificate integration work?
Zapier sits between your system and TRUE. It listens for the event you choose, takes the fields it carries, and sends them to TRUE as a request. TRUE issues the certificate against the matching design and delivers it. Nothing is installed anywhere.
1
Pick the trigger in your own system
Whatever means earned: a course completed, a form submitted, a status changed, a row added to a sheet. If Zapier connects to it, it can be a trigger.
2
Add the request to TRUE
Zapier's HTTP action posts to TRUE with the person's details mapped from the trigger. Your TRUE token is stored as a Zapier credential rather than pasted into the step.
3
Certificates issue themselves
When the trigger fires, the person receives a branded, blockchain secured certificate with a permanent verification link.
What does the certificate carry?
The recipient name, what they earned, your organisation and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Recipient name and credential. Mapped from your trigger, so the certificate says what your own system says.
- 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?
A Zapier account, a system Zapier connects to, and a certificate design. There is nothing to install and nothing to deploy.
- A Zapier account on a plan that includes the HTTP action.
- A trigger in your own system, the event that means the credential has been earned.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a recipient 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 personal data handled?
Only the fields you map into the step are sent, which for a certificate is a name, an email address and what the credential is for. Because you build the Zap, you can see exactly what leaves your system, and Zapier itself becomes a processor in that chain, which is worth noting in your own record of processing.
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 Zap the right long term answer?
Often, yes. It is worth being honest about the trade: a Zap is quicker to build and easier to change, and a direct connection is steadier at high volume. Most organisations start with a Zap, and plenty never move off it.
| Capability | A Zap | A direct connection to our API |
|---|---|---|
| Time to first certificate | An afternoon | A short project |
| Who builds it | Anyone comfortable in Zapier | Usually a developer |
| Changing the rule later | Edit the Zap | A change request |
| At high volume | Depends on your Zapier plan | Built for it |
| Cost | Your Zapier plan | Included with TRUE |
| Certificate itself | Identical | Identical |
What do Zapier users ask about this?
Mostly whether there is a TRUE app in Zapier, what the action looks like and whether it is fast enough. There is not, it is an HTTP request, and for most volumes yes.
Is there a TRUE app in the Zapier directory?
Not today. You use Zapier's own HTTP request action and point it at TRUE, which works from any trigger Zapier supports and does not depend on us publishing anything.
Do we need a developer?
No. The HTTP action is configured in Zapier's editor, and mapping the fields is the same drag and drop as any other step.
Is it fast enough?
For the volumes most organisations issue, yes. If you are issuing at a scale where a Zapier plan starts to bite, a direct connection to our API is the better home, and we will say so rather than let you find out.
Can we move off Zapier later?
Yes, and the certificates already issued are unaffected. They live on your domain and stay verifiable regardless of how the next one gets created.
Do recipients 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 records that already closed?
Yes. Earlier records 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 build the first one?
We prepare your certificate design and the exact request the Zap should make, you pick the trigger, and the first certificate can be issued the same afternoon.