GENI in Slack and Notion, where your team already works
Your team talks in Slack and writes in Notion. With both connected, GENI finds answers in your own documents, summarises busy channels and records decisions on the right page.
New to this topic? Start with Connect Your Own Tools: Connectors and MCP in dGENIX
The short answer
With Slack and Notion connected to dGENIX, GENI works in the two places where your team already spends the day. From Notion it pulls answers to questions about your own processes, customers and projects. In Slack it summarises busy channels and lists what was decided. And it can record a decision from a conversation as a page in Notion, so it does not disappear in the chat. You decide per connection what GENI may read and write.
The problem: knowledge in two places
In most small teams it goes like this. Decisions are made in Slack, in a thread that disappears under a hundred other messages after a day. Agreements and processes live in Notion, but nobody remembers exactly where. A new colleague asks in Slack how something works, and someone else looks it up and pastes a link.
That costs a little time every day, and sometimes a lot: when a decision is forgotten, or when two people remember it differently.
What GENI does with Notion
With the Notion connection GENI reads the pages you give it access to. Then you can ask:
"How do we handle a customer who has not paid their invoice after thirty days?"
GENI looks for the answer in your own pages and says where it is. If it is nowhere, it says so instead of making something up.
It can also write:
"Create a page in Notion with the agreements from this afternoon's customer call."
Start with a few pages people consult often: processes, customer information, frequently asked questions. Only then give access to more.
What GENI does with Slack
With the Slack connection GENI reads the channels you choose. Useful questions:
"Summarise the #project-newbuild channel for this week. What was decided and what is still open?"
"Which customer questions came up again in #support this week?"
After a day off or a week of holiday that saves an hour of scrolling. And people who are not in every channel still know what is going on.
The combination: recording decisions
The real gain is in the combination. A decision is made in Slack, and belongs in Notion:
"Put this week's decisions from #project-newbuild on the project page in Notion, with the date and who decided."
That keeps your Notion up to date without anyone having to take minutes. Make it a fixed task on Friday afternoon. How that works is in scheduled tasks explained.
Permissions and safety
An assistant with access to your Slack and Notion sees a lot. Three agreements we recommend:
- Choose the channels and pages. Do not grant access to everything. Start with what GENI needs for the tasks you want.
- Read first, write later. Let GENI only read for the first weeks. Once you see the summaries are right, grant write access for one page or one channel.
- No sensitive channels. HR, salaries and personal conversations do not belong in the connection.
How the consent screen works and what you tick is covered in connecting tools safely. Where your data stays is in where does your data go.
An example from a small agency
A marketing agency of six people works with one Slack channel per client and one Notion page per client. Every Friday the agency has GENI summarise the week per client: what was discussed, what was delivered and what is open. That summary goes onto the client page in Notion. On Monday everyone starts with the same overview, and a colleague who takes over a client reads where things stand in five minutes.
The agency had tried this earlier with a dedicated note-taker. That lasted three weeks.
Teams and Microsoft 365
Do you work in Microsoft Teams and SharePoint instead of Slack and Notion? With the Microsoft 365 connection it works the same way: GENI reads your documents and email within the permissions you grant. An overview of all connections is in connectors and tools.
What it costs
Summarising and searching are light to medium tasks. A weekly summary per channel fits easily in any paid plan. How credits work is explained in credits in dGENIX explained.
Knowledge that can go public
Part of what is in your Notion is also valuable for customers: answers to questions they often ask, explanations of your way of working, tips from your trade. That is material for your website. Ask GENI which internal pages are suitable to publish as an article, rewritten for customers. That makes internal knowledge visible to Google and AI assistants. The AI Content engine helps you plan those articles and write them in your own tone.
Do make sure you publish nothing that should stay internal, such as pricing agreements with certain customers or customer names without their permission. Let GENI make a draft, and read it before it goes online.
Frequently asked questions
Can GENI send messages in Slack on my behalf?
Only if you grant write access. We recommend starting with read-only and having messages prepared as drafts.
Does GENI see private messages?
Only what falls within the permission you give. Choose which channels it may read when you connect.
Does it work with a free Notion account?
The connection uses Notion's official access. You choose in Notion which pages GENI can see.
Where do I start?
dGENIX is in early access. Join the waitlist, or first read connecting tools for a small business.
