Automations
Turn one Notion or Discord event into a repeatable workflow across both products.
New launch item
Release tracker
Check the connections once
- An owner or admin is setting up the Automation.
- The Notion workspace and Discord server are connected.
- NotiCord can reach the pages, databases, channels, and threads the workflow will use.
Build a Notion-to-Discord workflow
Create one Discord thread for every ready Notion item, then send the item details into it.
Choose what starts the workflow
Open Automations, select Create automation, and name it. Under Event, choose a new item in your Notion database.
Keep only the items you want
Use Additional conditions only when every matching event should not run. Here, the item must have Status = Ready.
Add actions in the order they run
First add Create thread. Then set the message destination to Thread created in action 1. Use Insert variable instead of typing variable paths.
Create it, then run one real test
Select Create automation. Add one fresh matching Notion item, then return to Automations. The card shows the selected source and any saved conditions under When. It starts at Waiting for first run and becomes Active after successful matching work.
2. Send a message to the thread from action 1
Make one fresh matching item to confirm the full path.
Add a comment to a Notion page
Add Add comment, choose the Notion page, and write the Comment. Use Insert variable to include details from the event or an earlier action. The page can be the event page, an existing page, or a page created by an earlier action.
NotiCord posts a new page comment using its Notion connection. The connection needs Insert comments access. This action does not reply inside an existing discussion. When the event is a new comment, Add comment runs only for comments from people, preventing automated comments from triggering more comments. Other actions can still run.
Keep the workflow predictable
For Create thread or Create channel, later runs for the same Notion page use the resource this action created. NotiCord remembers which one it created; it does not search by name. Changing the name, location, or type affects new resources only. If a saved resource is deleted, a later run fails so you can repair the workflow.
Automated comments cannot trigger another Add comment action. Other actions can still run.
Save draft keeps setup from running. Drafts still use an Automation slot.
Check a run and recover
Select History on an Automation card to see each run, its error, and which Actions succeeded, failed, or did not run. Earlier Actions can finish before a later one fails. Check the run before repeating work by hand.
If a saved Notion or Discord connection, source, or target stops working, the Automation can show Paused with the reason and a link to fix it. Restore access or repair the setup, then save the enabled Automation or turn it on. It will wait for the next matching Event; the failed run is not replayed. An owner warning email follows your warning-email preference when an owner address is available.
A temporary provider failure or a problem limited to one Event can leave the Automation on with Needs attention. Open History for the exact error. NotiCord does not pause the whole Automation for those failures.
Need the full option list?
Events you can start fromNotion and Discord
Notion
Pages or database items created, updated, or deleted, plus new comments. Watch all shared pages, one database, or one selected page tree. Database updates can run only when selected properties change.
Discord
New messages, threads under one channel, or channels under one category. Message conditions can match an author, member, role, text, attachment, link, or mention.
Actions you can addSix action families
- Create thread or Create channel
- Give access to a channel or thread
- Create a Notion page
- Add comment
- Show this conversation in Notion for Discord events, or Show Discord chat in Notion for Notion events
- Send a Discord message
For a Discord Event, Show this conversation in Notion uses the conversation from When. A message shows its channel or thread; a new-thread or new-channel Event shows the newly created conversation. Choose its Notion destination in one page picker, including a page created by an earlier Action. A workspace choice appears when more than one connected workspace is available.
Saved Actions that already show a specific channel, thread, or earlier Action's output keep that source. Notion Events keep their separate Discord source selection.
New action names and text follow the selected Event and source until you edit them. After that, NotiCord keeps your version. Deleted Notion pages and items use a static deleted label because Notion no longer provides their title or link.
Drafts, health, and plan limitsRecovery, slots, and usage
Save draft keeps a new Automation silent and out of recent runs and the public API. Drafts still use an Automation slot. Save changes keeps an existing Automation on or off.
Automation cards show Active, Waiting for first run, Needs attention, Paused, or Off. Use History to inspect each run and follow the reason on a paused card before turning it on again.
Starter includes 1 Automation, Standard includes 3, and Pro includes 10. Plain Discord messages use monthly notification volume. The other five action families do not.