xWiki integration
Link a Conduction app to an xWiki instance and your end-users get articles, knowledge-base entries, and runbooks delivered straight inside the app's chat sidebar. The integration runs through OpenConnector, so credentials live in one place and the same source can feed multiple apps.
What it does
- Pulls articles from one or more xWiki spaces and indexes them in Open Register.
- Surfaces matching articles inside the app's chat companion as referenced links.
- Pushes status updates back to xWiki when an article is acted on.
- Tracks read receipts and citation counts in the audit log.
Setup
Open Integrations → Sources → New source, choose xWiki, paste the base URL and an API token. Test the connection.
Per source, choose one or more xWiki spaces. Open Register indexes the articles in those spaces and refreshes on the configured cron schedule.
In the target app (DeskDesk, OpenCatalogi, etc.), open the Integrations tab, toggle xWiki articles on, pick the source you added above.
Open the app's chat sidebar, ask a question that matches an indexed article. The matching article appears in the answer with a deep-link back to xWiki.
Configuration
Open Register side
| Source slug | xwiki |
|---|---|
| Mapping | Article ↦ Schema |
| Refresh | Cron, default */15 * * * * |
| Auth | Bearer token |
xWiki side
| Version | 15.x or later |
|---|---|
| Auth | REST API + personal token |
| Permissions | view on indexed spaces |
| Outbound | HTTPS to Nextcloud webhook |
Personal tokens are user-scoped. For production, create a dedicated service user in xWiki and issue the token from there. Never reuse a developer's personal token in production.
Troubleshooting
- No articles appear — check that the spaces you picked grant view to the token user, and that the cron has run at least once (
occ openregister:sources:refresh xwiki). - Articles show up but the chat link 404s — the xWiki base URL is misconfigured in the source. Update it in Integrations → Sources → xwiki.
- Refresh times out — large spaces should be split. The default page size is 100; tune
page_sizeon the source if needed.
Open Register supports the same integration pattern for n8n workflows, Keycloak identity, and Forum Standaardisatie reference data.