Lime CRM Integration
Lime CRM can issue TRUE certificates when a record changes
Lime CRM has a proper webhook system, documented on its own developer site. You subscribe to a change on whichever object matters to you, and Lime sends a signed message when it happens. Point that at TRUE and the person named on the record receives a branded, blockchain secured certificate on your own domain.
TL;DR
Lime's webhooks are not limited to a fixed list of events: a subscription can watch any object type in your Lime, for creation, update, deletion or restore. That means the trigger is whatever your organisation actually uses to mean earned, whether that is an agreement reaching signed, a certification record being created, or a training field changing. Deliveries are signed with a secret key, so TRUE can confirm the message is genuine before issuing anything.
- Nothing to build. Webhooks are part of Lime CRM and documented on its developer site.
- Any object, any change. The subscription follows how your Lime is set up, rather than forcing you into a fixed event list.
- Signed deliveries. Lime signs what it sends, so nothing can be issued by somebody pretending to be you.
How does the Lime CRM certificate integration work?
Lime holds the record and knows when it changes. A webhook subscription tells TRUE about the change you care about, TRUE checks the signature, issues the certificate against the matching design and delivers it to the person named on the record.
1
Decide which object and which change
This is the real decision, and it is yours. Lime lets you subscribe to any object type, so the trigger can be exactly the thing your organisation already treats as earned.
2
Create the subscription
An administrator, or a member of the webhook users group, creates the subscription and points it at the address we provide. Lime signs each delivery with a secret key.
3
Certificates issue themselves
When the change happens, 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. Taken from the Lime record itself, so it matches what your CRM already 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?
The right permission in Lime, a decision about which change means earned, and a certificate design. Lime asks for an administrator or membership of its webhook users group, which is a deliberate control rather than an obstacle.
- Lime administrator access, or membership of the webhook users group.
- The object and the change that mean earned, which follows how your Lime is already set up.
- 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?
Lime sends the record that changed, and we use the fields a certificate needs: a name, an email address and what the credential is for. The delivery is signed with your secret key, so we can prove where it came from.
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 Lime record on its own enough?
It proves the record exists in your CRM, which is enough for your own reporting. What it cannot do is prove anything to the person it is about, or to anybody they show it to.
| Capability | The record on its own | The record 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 |
| Choice of trigger | Not applicable | Any object type in your own Lime setup |
| Analytics | None | Views, shares and verifications tracked |
What do Lime administrators ask about this?
Mostly which events are available, who can create a subscription and how the message is secured. Any object, an administrator or the webhook users group, and a signature.
Does the Lime CRM integration have to be built?
No. Lime has a documented webhook system with subscriptions. Connecting TRUE is creating one subscription and pointing it at the address we give you.
Which events can we use?
A subscription can watch any object type in your Lime, for creation, update, deletion or restore. That means the trigger can be whatever your organisation already treats as earned.
Who can create the subscription?
An administrator, or somebody in the webhook users group. Lime keeps this deliberately restricted.
How do you know the message really came from us?
Lime signs each delivery with a secret key and TRUE checks that signature before issuing anything.
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 switch it on?
We prepare your certificate design and give you the address for the subscription, you choose the object and the change, and the next record that changes issues a verifiable credential.