Save flagged Slack messages into a Notion database

One emoji on a message turns it into a Notion row, so the good idea posted at four in the afternoon is still findable next quarter.

Trigger: Reaction added to a message

Action: Create a database item

About 4 minutes to set up

Build this flow

See Slack

How this flow works

Syncline watches Slack for Reaction added to a message. When that happens it runs Create a database item in Notion with the fields you mapped.

Invite Syncline to the channels you want watched and pick the emoji that means save this.
Share the Notion database the rows should land in.
Map the message text onto the title and the author onto the person property.
React to one message, check the row, then tell the team which emoji to use.

Field mapping

From Slack	To Notion	Note
Message text	Title	The message becomes the page title, trimmed at a sentence so the database stays readable.
Author	Assignee	The Slack member is matched to a workspace person by email, so the row arrives owned.
Channel	Tags	The channel name is stored as a tag, which is how you filter a shared database by where the idea came from.
Timestamp	Due date	The message time seeds the date property, with an offset you set when the row needs a deadline.

Why teams run it

Capturing a message costs one click, not a form
The channel and the author travel with the text
A decision made in chat becomes something you can count

Who uses it

A support lead who wants recurring complaints written down instead of remembered.

About the two apps

Slack

Slack is where a team notices things, which makes it the best place to put an alert and the worst place to store one. Syncline sends messages into channels when something happens elsewhere, and turns the replies worth keeping into records.

All Slack flows

Notion

Notion holds the pages and databases most teams treat as their second brain. Syncline reads those databases on a schedule and writes rows back, so a page never has to be retyped somewhere else.

All Notion flows