Learning & Training · Integration
KnowBe4
Add KnowBe4 to your product for your customers, and give your AI agents governed access to it.
Embed a KnowBe4 integration so your customers can see who has completed their security awareness training from inside your product instead of a separate console. Access is scoped per tenant and limited to the fields you map, so you read only what your product needs rather than the whole employee record, and every read and write is logged. fastn handles per-customer credentials, pagination and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own KnowBe4 account so your product shows each person's training status.
Read users and groups so your product mirrors how a customer organises their people.
Read training campaign enrolments and completions so a manager sees who is outstanding without another login.
Add a new joiner to the right group so their training starts on day one, with no admin doing it by hand.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks whether someone has completed required training before answering.
An agent reports outstanding enrolments by group so a manager can chase the right people.
An agent adds a user to a group after an approval, with the change audited.
Example prompt
List users in the finance group who have not completed the current training campaign.
Set up KnowBe4 in 4 steps
- 01Open the KnowBe4 connector from your fastn dashboard.
- 02Have each customer authenticate their own KnowBe4 account.
- 03Map the users, groups and training fields your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the KnowBe4 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a KnowBe4 integration without building it. Your customers connect their own KnowBe4 account inside your product and work their learners, training records and credentials there, with no per-customer code on your side.
- Handle the part that actually costs time: completion records get used as compliance evidence, so they have to be accurate and attributable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a KnowBe4 update is not your on-call problem.
- One integration serves your product and your agents. The same governed KnowBe4 connection powers in-product features and gives AI agents scoped, audited access, so you keep training records current without chasing spreadsheets without wiring it twice.
Used by these teams
Works well with
Okta
Workday
BambooHROften used alongside
Tools the same teams tend to run next to KnowBe4, across other categories.
Slack
Notion
Box
DocusignKnowBe4 integration FAQ
How do I add a KnowBe4 integration to my product?
Enable the KnowBe4 connector in your fastn dashboard, then let each customer authenticate their own KnowBe4 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no KnowBe4 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own KnowBe4 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own KnowBe4 account and only ever sees their own learners, training records and credentials. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this KnowBe4 integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks whether someone has completed required training before answering.
Who maintains the KnowBe4 integration?
fastn does. When KnowBe4 changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product enrol a learner or award a credential in KnowBe4 automatically?
Yes. An event in your product can enrol someone, assign a course, add them to a training path, or issue a credential in the customer's own KnowBe4 account, so training and recognition follow what actually happened rather than a manual upload.
Can I read completion and credential records back out of KnowBe4?
Yes, scoped per tenant and audited. Completions and issued credentials are frequently used as compliance evidence, so the read is logged and attributable rather than a bulk export nobody can trace.
What can I build with the KnowBe4 integration?
A common starting point: connect their own KnowBe4 account so your product shows each person's training status. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the KnowBe4 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding KnowBe4 does not change your per-connector cost. You can start free with 3 connected accounts.
Add KnowBe4 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.