Automations

Use Automations when one Notion or Discord event should start a custom sequence of work across both products.

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.

1. Open Automations and click Create automation.
2. Give the workflow a name that will make sense in recent runs, such as New launch item to Discord.
3. In Event, choose Notion, the connected workspace, Database items, the database, and the created-item event.
4. In Additional conditions, optionally require a field such as Status to match the value your team uses for ready work.
5. In Actions, add Create or reuse Discord channel or thread. Choose Thread and select its parent channel. The thread name starts with the Notion item title automatically.
6. Add Send plain Discord message after it. The message starts with New Notion item, the item title, and its Notion link. Target the thread from the earlier Action. Use Insert variable if you also want its thread name or link.
7. 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. Insert variable groups those choices by their source and replaces them with real details when the Automation runs. Variables appear as lowercase dot paths inside curly braces, such as {{notion.page.title}}. A path starting with action.2 comes from the second Action and updates if you reorder the Actions. Use the picker instead of typing these paths yourself.

New message text follows the selected Notion Event and source while it is still untouched. For example, a database source says item, while all shared pages or a selected page tree says page. Deleted-page messages and new Discord destination names use Notion page deleted or Notion item deleted without a title or link because Notion no longer provides them after deletion. Once you edit the text, NotiCord keeps your version when you change the Event or source. Opening a saved Automation never rewrites its text.

For Discord Events, a new Create a Notion page Action starts its title with the message author, thread name, or channel name for the selected Event. This untouched title follows later Event changes too, while an edited title stays exactly as you wrote it.

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

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

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:

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.