About Guru
Guru is a knowledge base where teams write short articles called cards, group them into collections, and verify them on a schedule. The Serval Guru integration connects to Guru’s API with a Guru API token and gives Serval access to your cards through its authenticated proxy. Authentication: HTTP Basic, with a Guru username and API token. Serval stores the token securely and attaches it to requests itself. The token is only sent to Guru’s API (api.getguru.com/api/v1/), and workflow code never sees it.
Data sync: Guru cards sync into Serval through the Sync Guru Cards to Knowledge workflow, added as a custom knowledge source. Each sync reads the cards in the collections you choose: Serval adds new cards, updates changed ones, and removes cards that were archived or deleted in Guru. The other workflows read from Guru when they run.
What the Guru integration enables
Choose a token
Guru has two kinds of API token. The token decides what Serval can read and do.Get your credentials
Create the token in Guru
Copy the token
Check what the token can read
Connect in Serval
Add a Guru connection
Enter the username and token
Submit and run the health checks
Verifying the connection
Run the integration’s health checks from the integration page:Sync Guru cards into knowledge
Install the sync workflow
Choose what to sync
Add it as a custom knowledge source
getguru.com as the logo, and select Sync Guru Cards to Knowledge. See Building Custom Ingestion Workflows for the other settings.Run the first sync
Workflows
Install these from the Guru integration. They are grouped into three bundles. Knowledge Sync- Sync Guru Cards to Knowledge: Runs as a custom knowledge source, as described above. No approval.
- Search Guru Cards: Takes a search query and returns up to 10 matching cards with title, link, collection, verification status and Markdown content. Long cards are cut at 8,000 characters and marked as truncated. No approval.
- Get Guru Card: Takes a card ID or a link such as
https://app.getguru.com/card/...and returns the full card as Markdown, with its owner and verification dates. No approval. - List Guru Collections: Returns each readable collection’s ID, name and card count. Needs a user token. No approval.
- List Guru Cards Needing Verification: Returns cards marked stale or needing verification, earliest due date first, with each card’s owner. Optionally limit it to one collection ID. No approval.
- Create Guru Card: Takes a title, content (Markdown or HTML) and a collection ID, and creates the card shared with the Guru team. Turn off Share with team to keep it private to its owner. Needs a user token, and asks the installer for approval before each run.
Limits
- Permissions are not mirrored: Serval does not copy Guru’s card or collection permissions. Synced cards follow the visibility of the Serval knowledge base they land in. List only collections that are safe for every reader in
COLLECTION_IDS, or connect with a collection token for a collection that is safe to share. - Full syncs only: Every sync reads all cards the token can see and keeps the chosen ones. A very large Guru account takes longer to sync.
- Verification stays in Guru: Serval reads verification state; owners still verify cards in Guru.
Gotchas and troubleshooting
Get Guru Token Owner fails with an authentication error
Get Guru Token Owner fails with an authentication error
List Guru Collections or Create Guru Card fails
List Guru Collections or Create Guru Card fails
Some cards are missing from Serval
Some cards are missing from Serval
COLLECTION_IDS, SYNC_ALL_COLLECTIONS and INCLUDE_CARDS_NEEDING_VERIFICATION in the sync workflow.Get Guru Card says the link is not a Guru card
Get Guru Card says the link is not a Guru card
https://app.getguru.com/card/...) or a card ID. Collection and board links are not cards.A synced page looks different from the card in Guru
A synced page looks different from the card in Guru
Need help? Contact support@serval.com for assistance with your Guru integration.

