receive schedule events and list database page notion and slack
Configured with Filter, Item Lists, Notion, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Integration
- Messaging
- Transform
- Routing
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Notion | Integration | Notion | databasePage / getAll |
| Slack | Messaging | Slack | See node parameters |
| Item Lists | Transform | Item Lists | summarize |
| Filter | Routing | Filter | See node parameters |
| Code | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
notionApislackApi
Workflow notes
Schedule Trigger
Execute WF on a schedule
Slack
Post message in channel
👋 How to use this template
👋 How to use this template
This template shows how you can create reports on data in an app and share a summary in another app. Here's how to use it:
- Double click the
Slacknode and create a credential by signing in. - Change the channel name in the
Slacknode to a channel you have in Slack. - Click the
Execute Workflowbutton and double click the nodes to see the input and output data
To customize it to you needs, just do the following:
- Enable or exchange the
Notionnode with any service that fits your use case. - Change the
2. Filter and transform your datasection to fit your needs - Adjust the Slack node or exchange it with any node that fits your use case
- Disable or remove the
Mock Datanode
3. Notify the right channel
1. Define a trigger that should start your wofklow
1. Define a trigger that should start your wofklow
We added a Schedule trigger that starts the workflow once a week.
Double click the node to modify when it runs
2. Load your data
2. Load your data
In our example, we're getting all new entries from a Notion Database in which we save new product ideas.
You can replace product ideas with any data that you want to summarize any service you wish, like Jira, Airtable, Google Sheets etc.
2. Filter and transform your data
2. Filter and transform your data
We only want to count the UX ideas of the team. We use the Filter node to filter out all other items, and use the Item Lists node to summarize the data for us.
To edit the nodes, simply drag and drop input data into the fields or change the values directly. n8n comes with a set of powerful transformation and branching tools like Set, ItemList, Code, If and many more.
Filter
Only keep UX ideas
Code
Mock Data
receive schedule events and list database page notion and slack
receive schedule events and list database page notion and slack
Purpose and structure
This folder contains the receive schedule events and list database page notion and slack workflow. Its executable nodes use code, filter, itemLists, notion, scheduleTrigger, slack. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0308_Code_Schedule_Automate_Scheduled.json MIT; preserve source notices.