Microsoft Dynamics 365 Integration
Dynamics 365 can issue TRUE certificates from a Power Automate flow
This is the path we know best. A Power Automate flow watches for the change that means somebody has earned a credential, and calls TRUE when it happens. Power Automate is included with most Microsoft 365 plans, the flow is built by clicking rather than coding, and once it runs the certificate issues without anybody opening a spreadsheet.
TL;DR
Dynamics 365 does not need a plugin for this. Power Automate, which most organisations already have with Microsoft 365, can watch a record and make an HTTP call when it changes. You set the condition that means earned, whether that is a training field flipping to complete, a case closing or a status reaching approved, and the flow sends the person's details to TRUE. TRUE issues the certificate carrying your design, on your own domain, written to blockchain at the moment of issue.
- Nothing to build. Power Automate is part of the Microsoft stack you already run, and the flow is built by clicking.
- You choose the moment. The trigger is whatever change in Dynamics means the credential has been earned.
- Then it runs itself. Every record that meets the condition issues a certificate.
How does the Dynamics 365 certificate integration work?
Dynamics holds the record and knows when it changes. Power Automate watches for the change you care about and makes the call. TRUE takes it, issues the certificate against the matching design and delivers it to the person. No code and no export.
1
Decide what earned means
This is the real decision, and it is yours. It might be a training field set to complete, a certification record approved, or a status reaching a value you already use. Everything else follows from it.
2
Build the flow
A record triggered flow in Power Automate, with an HTTP action that posts the person's details to TRUE. Your API token goes in the authorisation header, and the flow is built without writing code.
3
Certificates issue themselves
When a record meets the condition, 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 Dynamics 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?
A Power Automate licence, someone who can build a flow, and a certificate design. Most organisations already have the first, and the second is usually the person who maintains your Dynamics customisations.
- Power Automate, which is included in most Microsoft 365 plans.
- A trigger condition in Dynamics, the change that means the credential has been earned. This is the part worth thinking about before you build anything.
- 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?
The flow sends only the fields you map into it, which for a certificate is a name, an email address and what the credential is for. Because you build the flow, you can see exactly what leaves Dynamics.
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 Dynamics 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 |
| Who can see it | Staff with a Dynamics login | The person it is about, and anyone they show it to |
| Analytics | None | Views, shares and verifications tracked |
What do Dynamics administrators ask about this?
Mostly whether it needs a developer, what the trigger should be and whether Power Automate is included. No, it depends on your process, and usually yes.
Does the Dynamics integration have to be built?
Not in the sense of writing code. A record triggered flow in Power Automate with an HTTP action is built by clicking, and Power Automate is included in most Microsoft 365 plans.
What should the trigger be?
The change that means the credential has been earned in your process. A training field set to complete, an approval, a status reaching a value. We work it out with you, because it is a process question rather than a technical one.
Can one flow cover several credential types?
Yes. The flow can pick the certificate design from a field on the record, so one flow can serve several programmes.
Does this work with Business Central or Customer Service as well as Sales?
The mechanism is the same wherever Power Automate can see the record. What differs is which table you watch, which we confirm against your setup rather than assuming.
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 the exact call the flow should make, you decide the trigger, and the next record that meets it issues a verifiable credential.