Block 1 - When Executed by Another Workflow
- Type / Role
- n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...
n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.googledocs, n8n-nodes-base.set, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.toolworkflow, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.mcptrigger, @n8n/n8n-nodes-langchain.agent
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Ashby.
Original n8n.io sourceNeed help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?
Open "Edit Fields" → Replace sheet_id with your Google Doc URL.
Update discord_server_id, channel_id, and user_id (for DMs).
Call these from other workflows: save_memory: Log new data. retrieve_memory: Fetch history. send_memories_to_gmail: Discord summaries.
Edit the AI Agent prompt to style Discord messages.
💡 Pro Tip: Pair this with an MCP Server for full issue→memory→action automation!
Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator.. All 100% free?
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 | Team knowledge management with Google Docs, Discord, and AI assistant |
|---|---|
| Complexity | advanced |
| Nodes | 16 |
| Categories | Internal Wiki, AI RAG |
| Author | David Ashby |
| Published | 02 Jul 2025 |
Use the JSON export at /data/workflows/5560/5560.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.
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...
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, AI RAG use case.