Manage Jira Issues with Natural Language via Telegram and GPT-4 - n8n Workflow | Neura Market
Manage Jira Issues with Natural Language via Telegram and GPT-4
## Manage Jira Issues with Natural Language via Telegram and GPT-4
## Overview
The Jira Agent is an AI-powered assistant that allows users to interact with Jira directly through the messaging platform Telegram. It leverages OpenAI's GPT-4 model to interpret natural language commands and perform various Jira-related actions. On Telegram, it enables users to create Jira stories by triggering a guided form when prompted with "create story". Additionally, it provides more extensive functionality, including creating, updating, searching, and transitioning Jira issues through natural language commands.
## How it works
**Normal interaction**
Using messages such as "Please give me all my issues."
**Standardized process of creating stories:**
1. Message: create story
2. Open the Form that Telegram responds back to you
3. Fill in the essential story information in the form
4. The story automatically gets created in your backlog.
## Required Connections
To use the Jira Agent effectively, users need access to:
- A Telegram account, Telegram setup involves deploying the bot and starting a chat; story creation is triggered with a simple text command.
- A connected Jira workspace
- Permissions to create and modify Jira issues
- Access to GPT-4 API-key
Detailed configuration instructions are provided in the workflow.
## Setup Time
<15 minutes
## Customizing this workflow
- Try adding more details to the form for more complete Jira ticket creation.
- Try connecting a Google Calendar node to plan your work.
Platform
n8n
Category
AI
Price
Free
Creator
Humble Turtle
if
set
function
jiraTool
telegram
stickyNote
agent
telegramTrigger
lmChatOpenAi
How to import this workflow into n8n
1Purchase or download the workflow to get the n8n workflow JSON file.
2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
3Open each node marked with a credential warning and connect your own accounts and API keys.
4Run the workflow once manually to verify the data flow, then toggle it to Active.