# Coda + Risotto: your Coda tables answer questions in Slack and Microsoft Teams

Risotto answers employee questions in Slack and Microsoft Teams from your Coda docs, and cites the page or table it used. Someone asks who owns Loom, and Risotto reads the Owner column of Loom's row in your software table and replies in the thread. Nobody opens the doc to scroll for it.

[Book a demo](/demo)

## Your Coda docs, read the way you built them

- **Tables, row by row.** Risotto reads every table in a doc with its column names and every row, so an answer can come from two columns of one row.
- **Page text.** The text of every page and subpage. Hidden pages stay out.
- **The source cited.** Each answer links the page or table it came from, so anyone can check it.
- **All your docs, or a few.** Connect every doc the token can read, every doc in your Coda organization, or a list of doc URLs. Exclude any doc by its ID.
- **One answer from every source.** Risotto searches Coda with [Notion](/integrations/notion), Confluence, Google Drive and your other sources, and returns one answer. [Knowledge](/product/knowledge)
- **Answers that lead to action.** When the answer is "you need your manager's approval", Risotto takes the request, gets the approval and grants access in the same thread.

## Live in three steps

1. **Create a read-only Coda API token.** In your Coda account settings, generate a token with read-only access. Restrict it to specific docs if you want to.
2. **Add it to Risotto.** Store the token in Risotto's credential vault, name the index, paste the doc URLs if the token is restricted, and choose who it answers.
3. **Employees ask.** In Slack or Teams, and the answer arrives in the thread with the doc cited.

[Read the setup guide](/docs/integrations/knowledge/coda)

## Read-only, and scoped to the people who should see it

Risotto connects to Coda with a token you create as read-only, so it can't change a doc, a table or a formula. The token lives in Risotto's credential vault, where no one can read it back once it's saved.

Each Coda index answers the audience you choose. Give HR's docs to the HR department and IT's to IT, or mark an index "Assistant only" to keep it for IT's investigations and out of employee answers. In Slack, a department can also hold knowledge answers in its agent channel until someone on the team approves them.

> "Risotto is providing immediate answers 24/7, even when IT isn't online. That's a game changer." — Head of IT, Hazel Health

## Frequently asked questions

### What does Risotto read from Coda?

The text of every page and subpage in the docs you connect, and every table, with its column names and all of its rows. Exclude any doc you want kept out.

### How does Risotto keep up with changes in Coda?

Risotto reads your docs when you create the index, and one click on Reindex in the dashboard brings in every edit, new page and new row since.

### Can Risotto change anything in Coda?

No. The token is read-only and Risotto only reads. If you want an automation to add a row to a Coda table, IT can build a custom API tool from Coda's API docs, and put an approval on it like any other tool. [Automations](/product/automations)

### Do employees need a Coda account?

No. Employees ask in Slack or Teams and get the answer there.

### Where is the Coda API token stored?

In Risotto's credential vault. Secrets there are write-only, scoped to a department, and sent only to the hosts you approve.

## Stop pasting Coda links into Slack

[Book a demo](/demo)

Source: https://www.tryrisotto.com/integrations/coda
