# Guru integrations: cards, collections and folders

> Create a card, create a collection and create a folder in Guru, and start a workflow when Guru sends “Card created”.

**Canonical page:** https://tray.ai/connectors/guru-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

Guru is a company knowledge base where teams write verified cards, organize them into collections and folders, and search or ask questions across that knowledge. Tray.ai connects to Guru through the HTTP Connector, so your workflows can call the Guru API alongside the rest of your stack.

## Use cases

### Cards

Read, create, update, and delete cards in Guru from any Tray.ai workflow. The Guru API covers calls such as get a card and create a card.

- Get a card
- Create a card
- Update a card

### Collections

Read, create, update, and delete collections in Guru from any Tray.ai workflow. The Guru API covers calls such as list collections and create a collection.

- List collections
- Create a collection
- Update a collection

### Folders

Read, create, update, and delete folders in Guru from any Tray.ai workflow. The Guru API covers calls such as list folders and create a folder.

- List folders
- Create a folder
- Update a folder

### Card comments

Read, create, update, and delete card comments in Guru from any Tray.ai workflow. The Guru API covers calls such as list card comments and create a card comment.

- List card comments
- Create a card comment
- Update a card comment

### Tags

Read, create, and update tags in Guru from any Tray.ai workflow. The Guru API covers calls such as create a tag and update a tag.

- Create a tag
- Update a tag
- List tag categories

### Search

Read search in Guru from any Tray.ai workflow. The Guru API covers calls such as search for cards and search with sources.

- Search for cards
- Search with sources

## Challenges Tray.ai solves

### Keeping Guru credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Guru credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Guru API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Guru API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Guru?

Yes. Tray.ai connects to Guru through the HTTP Connector, which calls the Guru API directly. Any call the Guru API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Guru?

The Guru API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Guru connector?

Guru runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Guru connector from the Guru API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/