These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Knowledge Base Builder
- Integrations
Integrations
Plan service event connections around explicit receipt records.
- Knowledge Base Builder
- Event provider
- Service source
- Reader channel
Systems to connect
- Event provider. Connect an approved provider when external events need to be recorded. The receipt stores the provider, external event ID, received date, payload hash and processing status.
- Service source. Agree which existing service and asset records the team will bring into the app so support cases refer to the right operating context.
- Reader channel. If people will read articles outside the app, choose the delivery channel and its access policy as part of implementation.
How connections are governed
Name an owner for each connection and agree how a received event is matched to its source. Review receipts marked Rejected or Failed with the provider’s own evidence before retrying. Keep provider identifiers and dates intact so the team can explain what arrived and when. An article owner remains responsible for published instructions even when a connected system supplies case information.
Set up Knowledge Base Builder your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.