Orchestrate sequential Notion task execution for participants with webhooks
Ready for 3.0What this workflow does
This workflow has 53 nodes and runs when an HTTP POST request hits its webhook URL (plus 3 other triggers). It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 3 other triggers).
- Notion - Buscar fontes de dados para agendamento (HTTP Request): calls an HTTP API (POST)
- Filtrar tarefas com responsável (Filter): keeps only the items that match a condition
- Filtrar responsável revisando (Filter): keeps only the items that match a condition
- Notion - Buscar fontes de dados para execução (HTTP Request): calls an HTTP API (POST)
- Selecionar fontes com título para agendamento (Edit Fields (Set)): sets 1 field: data_sources
- Notion - Buscar responsável pela tarefa (HTTP Request): calls an HTTP API
- Iniciar execução do participante em revisão (Execute Sub-workflow): calls another n8n workflow
- Selecionar fontes com título para execução (Edit Fields (Set)): sets 1 field: data_sources
- Notion - Buscar taxonomia de execução agendada (HTTP Request): calls an HTTP API (POST)
- Filtrar responsável ativo (Filter): keeps only the items that match a condition
…plus 39 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (12)
- Data table
n8n-nodes-base.dataTable - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Split Out
n8n-nodes-base.splitOut - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Webhook
n8n-nodes-base.webhook - Filter
n8n-nodes-base.filter
From the author
Quick overview This workflow retrieves all child blocks from a Notion page or block ID, handling Notion API pagination by recursively calling itself until all content is collected. How it works 1. Receives an input containing the Notion page or block ID (and…