Block 1 - Slack Trigger - :book: Reaction
- Type / Role
- n8n-nodes-base.slackTrigger - slackTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Create FAQ articles from Slack threads to Notion and Zendesk This workflow helps you capture "tribal knowledge" shared in Slack conversations and automatically converts it into structured documenta...
n8n-nodes-base.slacktrigger, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.code, n8n-nodes-base.openai, n8n-nodes-base.notion, n8n-nodes-base.zendesk, n8n-nodes-base.set
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by satoshi.
Original n8n.io sourceThis workflow helps you capture "tribal knowledge" shared in Slack conversations and automatically converts it into structured documentation. By simply adding a specific reaction (default: π) to a message, the workflow aggregates the thread, uses AI to summarize it into a Q&A format, and publishes it to your knowledge base (Notion and Zendesk).
:book:) on a Slack message.Name (Title)Summary (Text/Rich Text)Tags (Multi-select)Source (URL)Channel (Select or Text)slackWorkspaceId: Your Slack Workspace ID (e.g., T01234567).notionDatabaseId: The ID of your Notion database.zendeskSectionId: (Optional) The ID of the section where articles should be created.reactions:read, channels:history, groups:history, chat:write.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Create AI FAQ articles from Slack threads into Notion and Zendesk |
|---|---|
| Complexity | advanced |
| Nodes | 16 |
| Categories | Internal Wiki |
| Author | satoshi |
| Published | 22 Dec 2025 |
Use the JSON export at /data/workflows/12019/12019.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Create FAQ articles from Slack threads to Notion and Zendesk This workflow helps you capture "tribal knowledge" shared in Slack conversations and automatically converts it into structured documenta...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Internal Wiki use case.