Automations
Turn one Notion or Discord event into a repeatable workflow across both products.
Add action offers Discord actions for a Notion event and Notion actions for a Discord event. After Create channel or Create thread in a Notion workflow, it also offers Embed Discord in Notion for the page from When. Deleted-page events cannot use this follow-up. Changing When updates the available choices.
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 page, then send the page details into it.
Choose what starts the workflow
Open Automations, select Create automation, and name it. Under Event, choose a new page in your Notion database.
Keep only the pages you want
Use Additional conditions only when every matching event should not run. Here, the page must have Status = Ready.
Add actions in the order they run
First add Create thread. Then set the message destination to Thread from action 1. Use Insert variable instead of typing variable paths.
Create it, then run one real test
Review When and Then beside the editor, or below the configuration on a narrow screen. The summary updates as you edit, before you save. Select Create automation. Add one fresh matching Notion page, then return to Automations. The card shows the selected source and any saved conditions under When. The card shows On and No runs yet until the first run. Afterward it shows the last run time.
2. Send a message to the thread from action 1
Make one fresh matching page to confirm the full path.
Add a comment to a Notion page
For a Discord event, add Add Notion comment, choose the Notion page, and write the Comment. Use Insert variable to include details from the event or an earlier action. Choose an existing page, a page created by an earlier action, or Page linked to this thread for a Discord thread event.
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. Add Notion comment is unavailable when When is Comment is added. Choose another action or event.
Give people access
Selected people and roles is the default for Give access. Choose Discord members or roles directly. For a thread, selected roles invite their current members; later role changes do not update thread membership. For a channel, the action grants permissions to the selected people and roles. Create-command requester invites the person who submitted the linked create command.
For People from a Notion property, share the database with NotiCord and choose its People property. The editor starts with the event’s database when one is selected. A single People property is selected automatically; multiple properties need your choice. Existing saved selections stay unchanged. Invitees need linked Discord accounts in Members, and previously invited people keep access.
Thread linked to this page uses the existing thread for the page. To use a creation action directly, choose Thread from action N instead. Creating a thread alone does not embed it or connect it to the page.
Connect pages and discussions
Embed Discord in Notion adds a read-only Discord view and remembers the selected page and channel or thread. A create command with a private discussion also records its page, thread and requester automatically.
For Send Discord message, choose Channel or thread embedded in this Notion page to use an existing channel or thread associated with the page that triggered the automation. Pages without an associated channel or thread are skipped. If several match the page, choose an existing channel or thread. Previously saved thread-only message destinations appear as Thread embedded in this Notion page and continue to use threads only.
A newly added message action defaults to the nearest preceding Create channel or Create thread output, such as Channel from action 1. This destination does not require an embed. Existing message destinations stay unchanged.
To embed that channel or thread too, add Embed Discord in Notion after the creation action. It starts with the page from When and nearest preceding channel or thread output. Place it before a message that uses Channel or thread embedded in this Notion page.
Thread linked to this page remains thread-only for access and state actions. Page linked to this thread routes Discord thread events back to their page.
Update page property updates one property per action. Page title needs only a Value. For a database property, choose the database to load its properties and available values, then choose Property and Value. Add another action for another property.
Change thread state closes, locks, unlocks or reopens a thread. Reopen also unlocks it. Thread state changes observes Closed, Reopened, Locked or Unlocked transitions on linked threads. Messages to an embedded thread and linked invitations require an open, unlocked thread; add Reopen or Unlock first when appropriate.
The Automation card's Then step names the saved operation: Close, Close and lock, Reopen, Lock, or Unlock, followed by the selected thread.
For request intake, replies, assignment and resolution, follow the Ticket support guide. It explains comment visibility and the member links needed for invitations.
Keep the workflow predictable
For Create thread or Create channel, later runs for the same Notion page use the resource this action created. Each creation action tracks its own result. 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.
Comment is added cannot use the Add Notion comment action.
Save draft keeps setup from running. Drafts still use an Automation slot. Unsaved changes means edits have not been saved; use Save draft before leaving.
Create Notion page also reuses this action’s recorded result for the same source event or page. It does not create a fresh page on every retry.
Check a run and recover
Select History on an Automation card to see the failed step, its original error, and which actions succeeded or were skipped. Failure details use the action recorded for that run, even if you later edit the Automation. When recorded, they distinguish creating a Discord channel or thread from reusing one created earlier and identify the affected resource. Older runs explain the action’s create-and-reuse behavior without guessing which operation failed. A skipped action may already have the requested value, lack an embedded destination, or be unreached because an earlier action failed. Earlier Actions can finish before a later one fails. Completion pending means the result has not been recorded, not that nothing happened. The run may still be working; if the status persists, check the provider result 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 created, updated, or deleted, plus new comments. Watch all shared pages, one database, or one selected page tree. For Page is updated, choose Content edits, Property changes, or both under Watch for. For a database, Which properties? narrows property changes to selected fields; leave it empty for All properties.
Discord
New messages, threads under one channel, channels under one category, or state changes of linked threads. Message conditions can match an author, member, role, text, attachment, link, or mention.
Actions you can addEight action families
- Create thread or Create channel
- Give access
- Create Notion page
- Add Notion comment
- Update page property
- Change thread state
- Embed Discord in Notion
- Send a Discord message
For a Discord Event, Embed Discord in Notion uses the channel or thread from When. A message shows its channel or thread; a new-thread or new-channel Event shows the new thread or channel. 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.
For an Existing page destination, choose a standalone page, or enable Include pages in databases to choose an individual database page. Search by title or paste a page URL. More results load as you scroll; the page must be shared with NotiCord in the selected workspace.
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 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 On, 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 action families do not.