Ready-to-use n8n node configurations and complete flows
Ready-to-import n8n workflow templates for integrating with Workflow. Download the JSON files and import them directly into n8n.
For integration concepts, see n8n Workflows. For async patterns, see n8n Async Patterns.
| Template | Description | Download |
|---|---|---|
| Ask Flow | Linear-triggered planning workflow with MCP updates | n8n-ask-flow.json |
| Edit Flow | Implementation workflow with branch/MR creation | n8n-edit-flow.json |
A complete workflow that triggers on Linear events and uses Claude to plan tasks.
Assign Flow: Triggers when an issue is assigned to the bot and moved to "Codespider In Progress"
Comment Flow: Triggers when someone mentions @codespider in a comment
After importing, update these values:
| Field | Location | Description |
|---|---|---|
your-bot@example.com | If nodes | Your bot's email address |
YOUR_WORKSPACE_ID | HTTP Request nodes | Your Workflow workspace ID |
YOUR_TEAM_ID | Linear Trigger nodes | Your Linear team ID |
YOUR_ASSIGNEE_ID | Update Issue node | User ID to reassign to after planning |
YOUR_STATE_ID | Update Issue node | State ID to move issue to after planning |
| Workflow URL | HTTP Request nodes | Your Workflow instance URL |
(Coming soon - drop your edit flow JSON into docs/templates/n8n-edit-flow.json)
Create these credentials in n8n before activating:
Bearer Auth (for Workflow API)
Workflow APILinear API
Linear accountHeader Auth (for Linear GraphQL)
Linear GraphQLAuthorizationBearer YOUR_LINEAR_API_KEYSearch for YOUR_ in the workflow and replace all placeholder values with your actual IDs.
For cleaner workflows, configure these in Settings → Variables:
| Variable | Example | Purpose |
|---|---|---|
workflowBaseUrl | https://workflow.example.com | Your Workflow instance |
defaultWorkspaceId | ws_abc123 | Default workspace ID |
botEmail | bot@example.com | Bot's email for filtering |
The Ask Flow uses prompts that leverage Claude's Linear MCP access:
Assign Flow Prompt:
You have access to a Linear MCP. Open the Linear issue at this URL:
{issue.url}and do the requested research to create a robust plan for the work being requested and update ONLY the issue description in Linear.
Comment Flow Prompt:
You have access to a Linear MCP. Review my latest comment on this issue:
{issue.url}and do the requested research to address my comment and update the issue description with any changes to the plan. When you are done, leave a brief reply to my comment.
This approach means Claude handles the Linear updates directly - your n8n workflow just needs to trigger Claude and optionally reassign the issue afterward.
The templates use neverError: true on HTTP requests so you can handle errors explicitly rather than having the workflow fail.
API requests have a 10-second timeout. For long-running Claude operations, the API returns queued: true immediately - you don't need a long timeout.