ChatGPTSoftwareShipping codeAI score · PendingAI-assisted edit · no obvious prompt-injection riskn8n.io

n8n Automated Jira Ticket Responses with GPT-4 and Pinecone

Scheduled trigger → query assigned Jira issues → retrieve from Pinecone knowledge base → AI generates reply → auto-post Jira comment

ExperiencedStepsWorkflowPromptTip
Who
Technical teams needing automated initial responses for assigned Jira tickets
You get
Assigned tickets automatically receive AI-generated comments based on historical knowledge base at set intervals
You need
n8n · jira · pinecone

Constraints

Prerequisites: n8n instance; Jira API access (API token + email); Pinecone account (API key + environment); OpenAI API key. A pre-indexed knowledge base must exist in Pinecone. The workflow runs on Schedule Trigger at defined intervals, not via real-time webhook.

What they did

Template author yusan25c created an n8n workflow that uses Schedule Trigger to periodically query Jira for issues assigned to a specific user, extracts issue title, description, and comment history, then passes them to an AI Agent with Pinecone vector database retrieval to generate a reply, which is automatically posted as a Jira comment with optional reassignment.

How it went

Author reports the template enables knowledge-base-grounded automated ticket replies (author_report). Actual effectiveness depends on Pinecone knowledge base quality and coverage.

Worth knowing

The Pinecone knowledge base must be pre-built and maintained; the source does not provide specific construction methods. The workflow JQL and Pinecone Index contain Japanese placeholders that must be replaced with actual values. Schedule trigger frequency should be configured carefully to respect API rate limits. AI-generated comments should retain a human review mechanism before direct publication. This site has not tested the workflow (reproduction=not_tested).

n8n workflow template

Structure checked · Not run-tested

Use “Import from File” in n8n, or copy the JSON and paste it into the editor. Connect your own accounts, then try test data. The template is inactive by default.

Setup and test checklist

Credentials to connect

  • After import, connect your own credentials on auth-required nodes; author secrets are not included.

Configuration to replace

  • Source template is n8n public workflow #9087 (~17 nodes). Keep inactive after import; verify triggers, expressions and external API endpoints.
  • Sticky-note guidance is informational; replace placeholders with your own accounts, sheet schemas or channel IDs.

Test input and expected output

  • Manually run the main path once in a test workspace and confirm credentialed nodes authenticate without errors.
  • Drive one synthetic/redacted sample through and check output fields and downstream writes before enabling in production.

Template changes

  • Author credential bindings, webhookId and execution data are removed; the workflow is inactive. Nodes, connections and original prompts are preserved. Not run-tested in n8n.
  • No business-logic edits; verify keys, quotas and privacy compliance before use.

Template retrieved: 2026-10-24

Steps

  1. Configure Jira credentials and schedule trigger

    Create Jira credentials in n8n (API token and email). Select the registered Jira account ID in the Jira Issue List node. Add a Schedule Trigger node and set the execution interval (mind API rate limits).

  2. Configure Pinecone vector database

    Register Pinecone credentials in n8n (API key and environment). In the Pinecone Vector Store node, enter your index name (replace placeholder <Pinecone Indexを入力>). Ensure your knowledge base is already indexed in Pinecone.

  3. Query assigned issues and extract content with comments

    Jira Issue List node queries assigned issues using JQL 'assignee = <accountId>'. Loop Over Items processes each issue. Code1 node extracts issue id, summary, and description. Jira Issue Detail node fetches latest comments. Code2 node concatenates comments into text and extracts updateAuthor.accountId. check accountId node filters out placeholder accountId (continues when not equal to '<アカウントIDを入力してください>').

    Execution prompt · Source text。Code1 node JS Code field

    return {
      'id': $input.first().json.id,
      'summary': $input.first().json.fields.summary,
      'description': $input.first().json.fields.description,
    }

    Execution prompt · Source text。Code2 node JS Code field

    let comments = '';
    let accountId = '';
    for (const item of $input.all()) {
      comments += '## ' + item.json.updated
      comments += '\n'
      comments += item.json.body.content[0].content[0].text
      comments += '\n'
      comments += '\n'
    
      accountId = item.json.updateAuthor.accountId
    }
    
    return {
      'comments': comments,
      'accountId': accountId
    };
  4. Configure and run AI Agent for retrieval and response generation

    AI Agent node receives title and description from Code1 and comment history from Code2. OpenAI Chat Model sub-node is configured with API key; model options include gpt-4.1-mini, gpt-4.1, or gpt-4. Pinecone Vector Store sub-node provides 'jira情報' retrieval tool in retrieve-as-tool mode; Embeddings OpenAI provides 1536-dimension vectors. AI Agent generates response based on systemMessage role and user prompt.

    Execution prompt · Source text。AI Agent node Text / User Message field (promptType=define)

    =# タイトル
    {{ $('Code1').first().json.summary }}
    
    # 説明
    {{ $('Code1').first().json.description }}
    
    # コメント履歴
    {{ $json.comments }}

    Execution prompt · Source text。AI Agent node Options > System Message field

    あなたはプロジェクトの開発者です。タスクがアサインされました。過去の知見を利用して対応をしてください。outputの内容をそのままJiraのコメント欄に記載します。また関連する過去の知見はIDも合わせて回答してください。
  5. Post comment and optionally reassign

    Jira Add Comment node posts the AI Agent output as a comment on the original issue. Jira Assign node reassigns the issue to the accountId extracted during comment retrieval (if different from placeholder). Loop Over Items then proceeds to the next issue.

Prompt you can copy

Setup guidance · Editorial suggestion。Give to setup assistant to confirm inputs and permissions first

This block is the prompt. Ads are never placed here.

You are setting up an n8n workflow to automatically generate AI replies for assigned Jira tickets using a Pinecone knowledge base. First confirm you have: Jira API token, Pinecone API key and index name, OpenAI API key, and a pre-indexed Pinecone knowledge base. Then import the workflow JSON or configure nodes manually following the steps.

Replace all placeholders before running: Jira accountId, Pinecone Index name, API credentials. Test with a single ticket and adjust schedule frequency.

Source

Automated Jira ticket responses with GPT-4 and Pinecone knowledge base · yusan25c · n8n.io · 2025-09-29

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related