Key takeaways
- A bare link rarely gets read; a summary tells people whether the page concerns them.
- Lead with what changed, then decisions, open questions and the ask.
- The assistant reaches only shared Notion pages and the channels the Pebbles bot was added to.
- Keep a rhythm: pick a fixed moment in the week and ask for the update then.
Why does sharing a Notion page in Slack rarely work on its own
Sharing a Notion page in Slack as a bare link rarely works, because nobody can tell from the link whether the page concerns them. A launch page can run to several screens of goals, dates, owners and open questions.
In Slack, people decide in a glance whether to click. A summary that names what changed, who it affects and what you need hands them that decision without opening the page.
What makes a good Notion summary in Slack
A good Notion summary in Slack says what changed since the last update, what is decided, what is still open and who must act, in that order. Write it for the person who reads only the first two lines: if they stop there, they should still know whether they have work to do.
- One line on what changed.
- Decisions made, a few words each.
- Open questions, each with the person who owns it.
- The ask: what you need from whom, and by when.
- The link to the full page.
Which Notion pages and Slack channels can the assistant reach
The assistant reaches only the Notion pages shared with the workspace's Notion connection and only the Slack channels the Pebbles bot was added to. An admin connects Notion and chooses which pages to share, and adds the bot to the channels you pick; everything else stays out of reach.
You ask for the update in Pebbles Ai. The bot gives the assistants a way to read and post in its channels, but it does not take requests from inside Slack.
How do you post Notion updates to Slack on a regular rhythm
Post Notion updates on a rhythm by asking for them at the same point every week, so readers learn when to expect them. Pick a moment, such as Friday afternoon during a launch, and ask the assistant then.
Keep these chats in the launch project, so Project memory carries what the team already agreed, such as which channel gets the update and how long it should be. In Manual mode the post waits on an approval card; in Plan it joins the queued actions; in Auto it goes straight to the channel.
How to turn a Notion page into a Slack update, step by step
The first two steps happen once; after that each update is a short chat.
- Ask an admin to connect Notion with the page shared, and to add the Pebbles bot to the Slack channel.
- Ask the Marketing or Strategy assistant to read the Notion page and draft a short update for that channel.
- Edit in chat until the draft says what changed, what is decided and what you need from whom.
- Ask the assistant to post it to the channel with a link to the page.
- Approve the post if you work in Manual mode, or leave it queued in Plan until you are ready.
Where Pebbles Ai fits
- FoundationIntegrationsAn admin connects Notion and the Pebbles bot for Slack. The assistants read only shared pages and post only in the bot's channels, each write following your execution mode.
- CapabilityAI workspaceKeep the update chats in the project for that piece of work, so each new chat starts from the decisions you stated there.
Common questions
Can the assistant also write back to Notion?
Yes, on pages shared with the connection. Each Notion write follows your execution mode, like a Slack post.
Does the Slack post replace the Notion page?
No. The post is the summary and the page stays the record, so always include the link and keep decisions on the page itself.
Who can connect Notion?
An admin connects Notion for the workspace and chooses which pages the assistants may read.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
