{"product_id":"resolve-n8n-orchestrator-errors-data-tables-notion-task-report","title":"Resolve n8n Orchestrator Errors: Data Tables \u0026 Notion Task Report","description":"\u003ch3\u003eTurn Failed n8n Executions Into Actionable Notion Task Reports\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow automatically catches failed executions, finds the related task logs in \u003cstrong\u003en8n Data Tables\u003c\/strong\u003e, and creates a structured \u003cstrong\u003eNotion “Relatórios”\u003c\/strong\u003e report—marking each task as \u003cem\u003eBloqueada\u003c\/em\u003e (blocked) with the error details or \u003cem\u003eFeita\u003c\/em\u003e (done). It also updates the participant status to reflect whether tasks exist to review.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eTriggers on failure:\u003c\/strong\u003e It starts when another workflow execution fails using the \u003cstrong\u003en8n Error Trigger\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLocates the right Notion data source:\u003c\/strong\u003e It searches Notion for available data sources and keeps only those with titles so it can locate the \u003cstrong\u003e“Relatórios”\u003c\/strong\u003e data source.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFetches participant execution data:\u003c\/strong\u003e Using the failed execution ID, it looks up the participant execution record in \u003cstrong\u003en8n Data Tables\u003c\/strong\u003e, then fetches the associated task log entries.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCreates a Notion report per task:\u003c\/strong\u003e For each non-empty task log entry, it retrieves the corresponding Notion task page and creates a report page in \u003cstrong\u003eRelatórios\u003c\/strong\u003e containing the error message and a link to the n8n execution.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eUpdates task state based on error presence:\u003c\/strong\u003e\n    \u003cul\u003e\n      \u003cli\u003eIf the task log indicates an error: updates the Notion task to \u003cstrong\u003e“Bloqueada”\u003c\/strong\u003e, writes the blocker reason with a mention of the report page, and clears the responsible relation.\u003c\/li\u003e\n      \u003cli\u003eIf no error is indicated: updates the task to \u003cstrong\u003e“Feita”\u003c\/strong\u003e and clears the responsible relation.\u003c\/li\u003e\n    \u003c\/ul\u003e\n  \u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eUpdates participant status:\u003c\/strong\u003e After processing tasks, it sets the participant page to \u003cstrong\u003e“Revisando”\u003c\/strong\u003e when tasks exist, or \u003cstrong\u003e“Ativo”\u003c\/strong\u003e when no tasks are found.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eWhen an automation fails, automatically notify your team in \u003cstrong\u003eNotion\u003c\/strong\u003e with per-task error reports.\u003c\/li\u003e\n  \u003cli\u003eUse \u003cstrong\u003en8n Data Tables\u003c\/strong\u003e to correlate failed executions with task history and keep status synchronized.\u003c\/li\u003e\n  \u003cli\u003eOperational review workflows for SaaS teams managing participant\/task pipelines.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eTrigger\/logic:\u003c\/strong\u003e n8n Error Trigger, \u003cem\u003eif\u003c\/em\u003e, \u003cem\u003eset\u003c\/em\u003e, \u003cem\u003eaggregate\u003c\/em\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eData integration:\u003c\/strong\u003e \u003cstrong\u003en8n Data Tables\u003c\/strong\u003e for execution\/task log lookup.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNotion integration:\u003c\/strong\u003e HTTP Request using \u003cstrong\u003eNotion Bearer token (HTTP Bearer Auth)\u003c\/strong\u003e and \u003cstrong\u003eNotion-Version: 2026-03-11\u003c\/strong\u003e to create report pages and update task\/participant statuses.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNodes referenced:\u003c\/strong\u003e if, set, aggregate, data table, sticky note, http request.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eCategory:\u003c\/strong\u003e n8n automation workflow — built for n8n users, automation engineers, and SaaS operators who need reliable error-handling with Notion reporting.\u003c\/p\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46190224867507,"sku":"N8N-20642","price":34.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/aFpHPyjP9gEhH_01UHRDk_NS5ePtZs.png?v=1791450511","url":"https:\/\/buyflowscripts.com\/products\/resolve-n8n-orchestrator-errors-data-tables-notion-task-report","provider":"N8N Commerce","version":"1.0","type":"link"}