How to connect Grok Bot to Notion with a Kanban board and webhook

To connect Grok Bot to Notion, create a webhook in your bot’s Details tab, build a Kanban database in Notion, and add a Notion automation that sends that webhook whenever a card’s Status or Prompt field changes. The bot then reads the card, does the work and leaves a comment on it, so every task you and your bots owe each other lives on one board instead of being buried in chats.

I run a lot of Grok Bots at OneAway. There’s one for marketing, one for growth and outbound, one for the CRM, one for replies, an assistant, and a “chief of AI” that hands work to the others. It starts with one bot. A few weeks later you have a team, and the things they need from you are scattered across a dozen chat threads.

This guide is the written version of the video above: the exact setup I use, step by step, plus the parts of Notion’s webhook feature that aren’t obvious until something breaks.

Why your bots need a board

Once you work with Grok Bot every day, the work splits into two kinds of tasks.

• Type A: work the bot does, with your direction. — The bot can do it alone, but it needs your guidance or sign-off at some point.
• Type B: work the bot needs from you. — A login, an approval, a decision, a file. Sometimes the bot asks for it. Sometimes you remember you owe it something before it can continue.

Chat handles type A well. It handles type B badly. A request from your CRM bot on Monday is ten screens up by Wednesday, and the bot just waits. I kept forgetting things I had to do, and with this many bots it got stressful.

A Kanban board fixes that. Every task is a card with a status, so you see at a glance what’s in progress, what’s blocked on you and what’s done. Grok Bot’s own interface is built around chat and doesn’t have a board view, so Notion fills the gap.

What you need

• Grok Bot — xAI’s app for building named AI agents. You need at least one bot you can open and give a webhook.
• A paid Notion plan — Notion’s help centre says the “Send webhook” action in database automations is only available on paid plans.
• About 10 minutes — Grok Bot can build most of this for you. The only step you have to do by hand is pasting the webhook URL into Notion.

How to connect Grok Bot to Notion in 6 steps

Step 1: Create a webhook in Grok Bot

Open any bot. You’ll see three tabs: Details, Library and Computer. Only Details matters here. Ask the bot to create a webhook and it will. Open the webhook and copy the unique URL it generated.

Treat that URL like a password. Notion’s webhook action sends requests without any authentication, so anyone who has the URL can wake your bot and hand it instructions. That’s why I blur mine in the video.

Step 2: Have Grok Bot build the Kanban board

Ask the same bot to create a Kanban-style board in Notion. It sets up the database with a Status property and the usual columns, such as backlog, in progress and done. You can build it yourself, but there’s no reason to.

Step 3: Add a Notion automation and pick the trigger

On the board, open Automations and create a new one. Name it after the bot, for example “Grok Bot: ops board”.

Grok Bot will suggest triggering when Status changes, so it hears about every card that moves from backlog to in progress or to done. Keep that, and add a second trigger: when the Prompt property is edited. That’s the one that lets you talk to a bot from a card. Step 5 covers the Prompt field.

Step 4: Send a webhook to Grok Bot

Add an action and choose “Send webhook”. A webhook is just one app telling another that something happened. Here, Notion tells Grok Bot that a card changed. Paste the URL from step 1 into the URL field.

Step 5: Pick what to send

Notion asks which properties to include in the request. Select all of them. The bot works better with full context, and there’s nothing to gain from being picky.

Step 6: Turn it on

Enable the automation. From now on, any status change or prompt edit on the board wakes your bot, and it replies with a comment on the card, signed with the bot’s name.

Add a Prompt field to brief a bot from any card

Add a text property to the database and call it Prompt. Whatever you type there is sent to Grok Bot when you finish editing it.

This matters more than it looks. Notion’s webhook action only sends database properties, not the text inside the page. If you write instructions in the body of a card, the bot never receives them. Put them in the Prompt property.

In the video I type “What is the status of this task?” into a card’s Prompt field. A moment later the bot is already working on it and posts the answer as a comment.

Route every card through one “chief of AI” bot

You don’t need a separate webhook for every bot. I point the board at one bot, my chief of AI. Its job is to receive every card, decide whose job it is and wake that bot up. If your account came with Grok Bot’s default general-assistant bot, that bot can play this role.

In the demo, I ask on one card for a video outline for next week that fits what we do at OneAway, based on our channel and our new website. The chief of AI picks it up and comments that it’s studying which formats work best on the channel and reading the new site.

One honest downside: when bots hand work to each other, it’s a bit slow. For tasks that live on a board, that’s fine. For anything that needs an answer in seconds, use chat.

Give each team its own view

Notion lets you save several views of one database. I keep a general board plus one view per team: a sales view for everything my CRM bot handles, and a marketing view for the SEO and content work. Same cards, filtered by who owns them.

Leave fully automated bots off the board. My inbox bot handles cold email replies and books meetings without me, so it has nothing to put on a card. The board is for work where a bot and a person still need each other.

Limits to know before you rely on it

These come from Notion’s help page on webhook actions, checked in November 2026:

• POST only — Webhook actions only send POST requests, which is what Grok Bot’s webhook expects.
• Properties, not page content — Only database properties are sent. That’s why the Prompt field exists.
• No authentication — Requests aren’t authenticated, so keep the URL private. You can add a custom header if your setup checks one.
• Up to 5 webhook actions per automation — Enough to notify several bots or tools from one trigger.
• Failures pause the automation — If a webhook fails, Notion shows a warning and pauses the automation. You have to resume it by hand, so check the board if your bot goes quiet.

Frequently asked questions

Key takeaways

• Bot work comes in two kinds: work the bot does with your direction, and work it needs from you. Chat loses the second kind. A board doesn’t.
• The setup is a Grok Bot webhook, a Notion Kanban database, and one automation that sends the webhook when Status or Prompt changes.
• Put instructions in a Prompt property. Notion’s webhook doesn’t send page content.
• Point the board at one coordinating bot that hands work to the others.
• Keep the webhook URL private, and check for a paused automation if a bot goes quiet.

If you’re still choosing how to run a team of agents, read how Claude Code agent teams coordinate work and the 10-20-70 rule for AI, which explains why the human oversight a board like this gives you matters.