Work With Your Coda Docs and Tables Through Your Muse
Through a Composio custom connector, a muse can list and copy your Coda docs, create pages, add and update rows in Coda tables, and set who a doc is shared with, all from a chat.
What it does
Coda is a document tool where teams keep project trackers, lists, and notes that mix text with tables. Connecting it through Composio gives the muse tools for those docs. It can list the docs you can open, read the pages and tables inside one, and copy a whole doc to start a new tracker from an old one. It can create a new doc or page, and add rows to a table or update rows by a key column you name. It can add a permission so a doc is shared with someone, list who has access, export a page as HTML or Markdown, and trigger an automation built in a doc. Name the doc each time.
How to use it
- Make a Composio account, open its Muse page, and copy your API key. The key starts with ck.
- In a new chat, ask the muse to create a custom connector for the Composio server and open the secure credentials store. Paste the key there, never in the chat.
- Back in the chat, ask the muse to connect Coda. Follow the sign-in link, sign in, and approve the access.
- Start with a read, such as listing your docs or reading the rows of one tracker table, and check the result in Coda.
- Then try a small write, such as copying a tracker doc or adding one row, and open the doc to confirm the change landed.
What you need
- A Muse account that can add custom connectors
- A free Composio account and its API key
- A Coda account with at least one doc in it
What to watch for
- Name the exact doc and table in every request. Similar names are common in a busy workspace, and a row added to the wrong tracker is still added.
- Sharing changes who can see your work. Ask the muse to list current permissions before it adds anyone, and approve each person yourself.
- Copying a doc copies its tables as they are now. Check the copy for old figures before you share it as a fresh start.
- Never paste the API key into a chat. If you do, treat it as exposed: make a new key in the Composio dashboard, delete the old one, and add the new key through the secure store.