> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/playbooks/tools/knowledge-management.md).

# Knowledge Management

Knowledge Management Tools let Playbooks read, create, and update collaboration content. Use them when a Playbook needs to pull context from Slack or Google Workspace, create a draft, update a spreadsheet, upload a file, or send a message.

## Tools

### Slack

Read channel history, inspect threads, send messages, create canvases, and work with Slack workspace content.

Use **Slack** when a Playbook needs to gather context from conversations or publish a message after generating output. The Tool can list channels, read channel history, read threads, look up users, search messages, send messages, add reactions, and work with canvases.

### Google Docs

Read and edit Google Docs documents. Use it when a Playbook needs to turn research or generated content into a Google Doc.

Use **Google Docs** when the final deliverable should live in Google Docs. The Playbook can read a document, create a new document, or create a formatted document from HTML.

### Google Drive

Upload, download, list, and manage files in Google Drive.

Use **Google Drive** when the Playbook needs to list files, upload generated assets, place files in a folder, read metadata, or manage Drive files.

### Gmail

Send plain-text or HTML emails through Gmail.

Use **Gmail** when the Playbook should draft and send an email through an authenticated Gmail account. Include approval requirements in the Section if the email should not be sent automatically.

### Google Sheets

Read, update, append, and create Google Sheets spreadsheets.

Use **Google Sheets** when the Playbook needs structured rows, planning tables, reporting outputs, or spreadsheet-backed task lists. It can read ranges, update cells, append rows, and create new spreadsheets.

## How to Configure

1. Open the Playbook editor.
2. Type `/` in the Section where the Playbook should use the collaboration Tool.
3. Select the Tool.
4. Connect the required authentication if prompted.
5. Include the channel, document, file, email recipient, or spreadsheet the Playbook should use.

## Parameters

| Tool              | Required context                                  | Optional guidance                                                                |
| ----------------- | ------------------------------------------------- | -------------------------------------------------------------------------------- |
| **Slack**         | Channel, thread, message, canvas, or user context | Add date range, search query, message format, or posting rules                   |
| **Google Docs**   | Document URL, document ID, or new document title  | Add editing scope, formatting requirements, or export expectations               |
| **Google Drive**  | File ID, folder ID, file path, or upload target   | Add MIME type, folder placement, naming rules, or cleanup instructions           |
| **Gmail**         | Recipient, subject, and body                      | Add CC, BCC, HTML formatting, attachments, send timing, or approval requirements |
| **Google Sheets** | Spreadsheet ID, sheet name, or range              | Add value input mode, append behavior, headers, formulas, or formatting rules    |

## Examples

```markdown
Use **Google Sheets** to append one row per approved topic to the planning spreadsheet. Include topic, target keyword, status, and owner.
```

```markdown
Use **Slack** to read the launch channel from the last 14 days, then summarize open questions before drafting the update.
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.airops.com/actions/playbooks/tools/knowledge-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.