Cook.ai
Documentation Browse

Slack and Discord

If your team already uses Discord

Put Cook in your Discord server, and see what it can do there.

Before you start

You need permission to add a bot to your Discord server. If you do not have it, the person who administers the server can invite the bot, and you can use Cook straight afterwards.

Putting it in your server

  1. At the very bottom of the sidebar there is a small bar that says Add Discord. Press Set up on it. The bar alternates between Slack and Discord, so if it is showing Slack, either wait or press it anyway — the next window offers both.
The bar at the foot of the sidebar. It alternates between Add Slack and Add Discord.
The bar at the foot of the sidebar. It alternates between Add Slack and Add Discord.
  1. A window opens offering Slack and Discord. Press Set up on the Discord row.
The Connect Cook window. Slack and Discord each have their own Set up button.
The Connect Cook window. Slack and Discord each have their own Set up button.
3. Invite the bot to your server and approve it. 4. Prove the server is yours: Cook gives you a short code, and you type `pair ` in a direct message to the bot. 5. Pick the channels Cook should mirror.

Asking it for something

Send the Cook bot a direct message, or write @Cook in a channel it has been added to. Plain English — no slash commands.

Two things tell you it heard you: a chef mark appears on your message, and Cook is typing… shows under the conversation for as long as it is working.

What comes back

  • Numbers arrive as a card built from Discord’s own components: real text, themed to your server, readable on a phone.
  • Documents arrive as real Discord attachments you can forward. Discord caps a bot upload at 10 MB per file; anything larger arrives as a download link instead, so a big file is never lost.
  • Recordings of anything Cook did in its cloud browser come back as a watchable link. It opens in a browser, needs no Cook account, and does not expire.
  • Long research is written up and filed in your Library, with a link in the conversation rather than pages of text.

Approving what it proposes

Anything that spends money or leaves the building arrives as a card with Approve, Request changes and Reject buttons. Press one and it runs exactly as proposed; the request is frozen when the card is created.

When a proposal is a list, the card carries a picker. Untick anything you do not want before approving, and only the rest runs.

Who may press depends on your workspace’s own roles, set in Settings under the approval policy. An owner can run some things without a card; a teammate’s request routes to whoever can sign it off.

Where the request turns up

A card appears where you were talking. Ask in a Discord direct message and the card arrives in that direct message — not in some other app you also connected.

If something does not arrive

  • Cook does not answer in a channel: the bot has not been added to that channel, or the channel is not linked yet. Add it from the Integrations page.
  • A teammate is refused: they have not paired their Discord account. They can send the bot a direct message with their own pairing code from Cook.
  • A button says you are not the person it is routed to: the approval went to someone else under your workspace’s policy. They can press it, or an owner can.

If your team uses Slack instead

Cook works the same way in Slack. See If your team already uses Slack.