Block 1 - Google Sheets Trigger
- Type / Role
- n8n-nodes-base.googleSheetsTrigger - googleSheetsTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Description Automatically assigns new tasks from an Excel/Google Sheets source to the best fit employee based on expertise, then creates issues in Jira. Gain fast, consistent routing that reduces m...
n8n-nodes-base.googlesheetstrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatazureopenai, n8n-nodes-base.googlesheetstool, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.jira, n8n-nodes-base.switch, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Rahul Joshi.
Original n8n.io sourceAutomatically assigns new tasks from an Excel/Google Sheets source to the best-fit employee based on expertise, then creates issues in Jira. Gain fast, consistent routing that reduces manual triage and speeds delivery. 🧠📊➡️🗂️
⏱ Save time by automating task assignment from new entries. 🎯 Improve accuracy with expertise-based matching. 📋 Keep clean, structured outputs for downstream systems. 🔁 Seamless handoff from Sheets to Jira with no manual steps.
🧩 IT Support and Ops teams routing incoming work. 🧭 Project managers orchestrating assignments at scale. 🛠 Engineering managers seeking consistent triage. 📈 Business operations teams automating intake to delivery.
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 | Route Jira tasks to experts using Google Sheets and GPT-4o-mini |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | CRM, AI Chatbot |
| Author | Rahul Joshi |
| Published | 15 Oct 2025 |
Use the JSON export at /data/workflows/9682/9682.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.
Description Automatically assigns new tasks from an Excel/Google Sheets source to the best fit employee based on expertise, then creates issues in Jira. Gain fast, consistent routing that reduces m...
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 CRM, AI Chatbot use case.