Automations
Use Automations when one Notion or Discord event should start a custom sequence of work across both products.
| Use | Best when |
|---|---|
| Notifications | A Notion change should send one standard NotiCord card to Discord |
| Scheduled Summaries | A channel needs a current Notion snapshot on a daily, weekly, or hourly schedule |
| Automations | A Notion or Discord event should run custom, ordered actions |
Before you start
An owner or admin can manage Automations. Connect at least one Notion workspace and one Discord server first. Share every Notion page or database the workflow will use, and make sure the NotiCord bot has the permissions required by its Discord actions.
- If a Notion source or destination is missing, use Give NotiCord Access in Notion.
- Before creating channels, threads, or messages, check Discord channel permissions.
Build a Notion-to-Discord workflow
This example creates or reuses one Discord thread for each new Notion item, then posts the item details in that thread.
- Open Automations and click Create automation.
- Give the workflow a name that will make sense in recent runs, such as New launch item to Discord.
- In Event, choose Notion, the connected workspace, Database items, the database, and the created-item event.
- In Additional conditions, optionally require a field such as Status to match the value your team uses for ready work.
- In Actions, add Create or reuse Discord channel or thread. Choose Thread, select its parent channel, and use the variable picker to insert the Notion item title in the thread name.
- Add Send plain Discord message after it. Target the thread from the earlier action, then use the variable picker to add the Notion title and page link. You can also insert the earlier action's thread name or link.
- Click Create automation. Make one fresh matching Notion item, then return to the Automations list to check the run.
Actions run from top to bottom. An action can use values from the Event or from an earlier Action, so keep anything that creates a destination before the steps that use it. Use the variable picker instead of typing placeholder syntax yourself.
Need to stop before the workflow is valid? Save draft keeps a new Automation from running. A saved draft still uses an Automation slot and does not appear in recent runs or the public API. Create automation validates and turns on a new Automation. For an existing Automation, Save changes preserves its current on or off state.
Choose an Event
| Product | Supported event families |
|---|---|
| Notion | Pages or database items created, updated, or deleted; comments created |
| Discord | Messages created in one channel or thread; threads created under one channel; channels created under one category |
Notion Events can watch all shared pages, one database, or one selected page tree. A database update Event can also run only when selected properties change.
Discord message Events can use Additional conditions for author, member, role, text, attachment, link, or mention. Additional conditions are optional and are checked before any Action runs.
Choose ordered Actions
| Action family | What it does |
|---|---|
| Create or reuse a Discord channel or thread | Creates one destination for the source item, or reuses what that Action created on an earlier run |
| Add people or roles | Updates access to a fixed channel or thread, or one produced by an earlier Action |
| Create a Notion page | Creates a page under a selected page or database and can map available values |
| Add a Discord embed to a Notion page | Adds a read-only channel or thread view to a fixed, triggered, or earlier-created Notion page |
| Send a plain Discord message | Sends custom text and selected mentions to a fixed, triggered, or earlier-created Discord destination |
Plain message Actions run for every matching Event after its Additional conditions pass. Each message counts toward monthly notification usage. The other four Action families do not.
How reuse and loop protection work
Resource Actions remember what they created for each source item and Action. If NotiCord handles the same source item again, it reuses that Discord channel, thread, or Notion page instead of creating a duplicate. It also skips adding the same Discord embed to the same Notion page twice.
An Automation does not react to Events it created itself. This prevents a workflow that writes back to Notion or Discord from starting its own loop.
Read an Automation card
The Automations list summarizes each workflow as a When → Then flow. Its steps show every connected Notion workspace and Discord server by name.
Fixed Discord channels, threads, categories, and selected create-or-reuse parent resources link directly to Discord. Dynamic destinations, including resources that an Action creates at run time, stay unlinked until a stable destination exists. Unavailable saved resources remain visible so you can identify and repair the affected step.
Each card keeps recent run timing separate from the flow and uses these health states:
| Health state | Meaning |
|---|---|
| Healthy | Recent matching work completed without an unresolved problem |
| Waiting for first run | The Automation is on but has not processed a matching Event yet |
| Needs attention | A saved resource, permission, or Action needs to be repaired |
| Off | The Automation is not running |
If a card needs attention, open Edit, restore the missing Notion or Discord access, reselect an unavailable resource when needed, and save again.
Limits and monthly usage
Solo includes 1 Automation, Team includes 3, and Pro includes 10. Drafts use the same slots as running Automations. Plain Discord messages sent by Automations use monthly notification volume; resource creation, access, Notion page, and embed Actions do not.
See Plans & Billing for the complete limits and usage-counting rules.