Slack to Notion.
In one forward.

Nock is the Slack bot we built for ourselves. Forward any message — from a CEO's DM, a #client-marketing channel, or a #relayer-dev thread — and Nock files it as a Notion task in the right database, with title, assignee, and deadline pre-filled.

Get one built Read the story →

Forward. File. Done.

#tasks · today·3 forwarded

Alim09:14

Forwarded from Yassir, Chatbase

“Need the onboarding video updated by Friday — focus on the new agent flow.”

Nockparsing…

Update onboarding video — new agent flow

ChatbaseDue Fri@mahroos

Live preview · simplified

Why we built it.

Every internal tool starts with a complaint. Ours was simple: too many Slack messages were turning into tasks, and tasks meant a copy-paste loop into Notion. We were doing it dozens of times a day, across two dozen clients. By the end of a week it was a real number of hours we'd never get back.

Nock was a Friday-afternoon idea that kept growing. The first version did one thing — take a forwarded message and file it as a task. Today it does a lot more, but the original principle hasn't moved: the bot should disappear into the background and just do the right thing.

We were copy-pasting tasks from Slack into 26 Notion boards every day, by hand — until we weren't.

What's inside.

01Forward a message. Get a task.

Paste, forward, or @mention. Nock pulls a clean title, description, due date, assignee, and status from a single paragraph — no template, no command syntax, no friction. It adapts to whatever properties your Notion DB happens to use.

Reply in thread to adjust any field — “actually due Friday, not Thursday” — and Claude turns natural language into structured updates. No buttons.

Claude · parsing·0 / 5

“Need the onboarding video updated by Friday — focus on the new agent flow.”

— Yassir, Chatbase

titleUpdate onboarding video — new agent flow

clientChatbase

deadlineFriday, Apr 25

assignee@mahroos

statusOpen

02Notion is the source of truth.

Nock scans Notion every 24 hours, fuzzy-matches database names to Slack channels, and rebuilds its routing table from scratch. Rename a DB, add a new client, archive an old project — Nock notices and asks for clarification only on genuine ambiguity.

Routing is token-overlap matching with a completeness tiebreaker. @nock rescan triggers a fresh check on demand.

Notion → Slack·0 matched

Chatbase Tasks#chatbase-marketing98%

Relayer Backend#relayer-dev96%

AutoAssist Goodwill#aa-goodwill92%

AdPrompt UI#adprompt-frontend88%

Mountainside Roofing#mountainside100%

03Learn once. Route forever.

When the CEO of a client DMs you and you forward to Nock, the first time you tell Nock which client this is — and from then on, every forward from that person auto-routes silently. Mapping persists across redeploys on a Railway volume. Re-pick to update.

04Delete the source. The reply goes too.

Slack threads accumulate orphaned bot replies when source messages get deleted. Nock listens for delete events and removes its own task card or confirmation — so the channel stays clean. The Notion task itself isn't touched; only the Slack stub goes.

Under the hood.

Six things that took longer than the demo would suggest.

Schema-driven mappingReads any Notion DB's schema at runtime and maps Title / Status / Due / Assignee properties by name patterns — no per-client config.
Cross-workspace channelsRoutes forwards correctly across multiple Slack workspaces using channel ID, not channel name — handles your client's workspace and yours.
Persistent overridesAdmin choices and learned mappings live in a 50 GB Railway volume. Survives redeploys, crashes, and rollbacks.
Admin-only setup chatterMapping prompts post as Slack ephemeral messages visible only to the admin — setup never leaks into the team channel.
Conversational LLM editingReply in thread to adjust any field. Claude turns natural language into structured updates — no buttons required.
Batch task listsDrop a daily standup with bullet points + multiple @mentions, and Nock files each one as a separate task to the right person and client.

client Notion DBs auto-discovered

hardcoded mappings — fully derived

forward to file a task, anywhere

<1k

lines of TypeScript

A few questions.

Anything else: hello@practa.ai.

Both are great for 1:1 workflows. Nock handles 25+ clients with one bot, learns over time, and uses LLMs to parse intent — not just trigger conditions. Zapier would need 25 separate flows, manually maintained.

Within 24 hours, Nock detects the new Notion DB and pings the admin: "new DB X — which channel routes here?" One click. Done. New forwards from that channel start filing tasks to the new DB.

Tasks live in your Notion. Slack stays in Slack. Nock holds a small JSON file (under 10 KB) of channel and person overrides on a Railway-mounted volume. Nothing else is persisted.

Want a Nock for your team? hello@practa.ai — we'll scope it.

More cases