Jira
Run connic agents on new issues, issue updates and comments in Jira Cloud. Agents comment back or create new issues.
- Modes
- Inbound, Outbound
- Set up in
- Dashboard or connectors/*.yaml
- Documentation
- Jira docs
- Publisher
- By connic
Answer Jira issues and comments
When an issue matches an inbound connector's events and JQL filter, every agent linked to it starts. An outbound connector on the same Connection comments the result on the issue.
- Pick events and a JQL filter
- Choose from jira:issue_created, jira:issue_updated and comment_created. Only issues that match the JQL filter, such as project = SUP, start a run.
- Several connectors per site
- Watch one project with one connector and another project with a second, or use one per environment. Each connector registers its own webhook.
- No loops, no double runs
- Events the Connection's own account causes are ignored, and an event that Jira delivers again doesn't start a second run.
Something happens in Jira
Someone creates an issue, updates one or adds a comment.
jira:issue_createdconnic checks and confirms the event
It verifies the signature with the webhook's secret and answers Jira right away.
X-Hub-SignatureLinked agents start
The run gets the event, the issue key and project, the summary, the description or comment, a link and the author.
comment_createdThe answer lands as a comment
An outbound connector on the same Connection comments on the issue the run started from.
Connect your Jira site with an API token
A Jira Connection holds your site URL, the email of an Atlassian account and its API token. An inbound connector picks events and a JQL filter, and connic registers the webhook on your site.
- Your account, your token
- connic comments and creates issues as the Atlassian account on the Connection. Create its API token without scopes. Jira Cloud only.
- Webhook set up for you
- Saving an inbound connector registers a webhook for its events and JQL filter, signed with a secret connic generates. Deleting the connector removes it. This needs the Administer Jira global permission.
- Replace the token in time
- Atlassian API tokens expire after at most 365 days. Replace the token on the Connection before then, and every connector that uses it picks up the new one.
type: jira
mode: inbound
connection: acme-jira
config:
events:
- jira:issue_created
- comment_created
jql: project = SUP
agents:
- support-triageComment on issues or create new ones
An outbound Jira connector posts the agent's output as plain text, whether the run answers a Jira issue or comes from another connector or a schedule.
- Routing
- An issue_key in the output wins. Without one, a run started from a Jira issue on the same Connection comments there, and any other run creates an issue in the connector's project, as a Task unless you pick another issue type.
- Three ways to send
- Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
- Rate limits handled
- When Jira rate-limits a comment or issue, for example with its per-issue write limits, connic waits and sends it again.
{
"summary": "EUR totals are rounded twice at checkout",
"body": "Orders in EUR are one cent off since release 2.14."
}{
"body": "Reproduced on staging: the total is rounded twice.",
"issue_key": "SUP-142"
}Where Jira fits
Pick a setup to see what reaches the agent and what it posts back to Jira.
A customer reports a problem in the support project, and the agent asks for missing details and names the likely area.
{
"event": "jira:issue_created",
"issue_key": "SUP-418",
"project": "SUP",
"summary": "Refund button does nothing",
"text": "Clicking Refund on an order shows no error and no refund.",
"url": "https://acme.atlassian.net/browse/SUP-418",
"author": "Jana Weber"
}{
"body": "Likely the refunds service. Which order ID and browser?"
}Someone asks a question in a comment, and the agent answers on the same issue.
{
"event": "comment_created",
"issue_key": "SUP-402",
"project": "SUP",
"summary": "CSV export times out",
"text": "Still failing after the update. Is there a workaround?",
"url": "https://acme.atlassian.net/browse/SUP-402?focusedCommentId=10231",
"author": "Sam Lee"
}{
"body": "Until the fix ships, export one month at a time."
}Your helpdesk sends a bug report, and the agent turns it into a Jira issue.
{
"ticket_id": "T-20931",
"customer_id": "C-1042",
"subject": "Invoice PDF shows the wrong VAT rate",
"message": "Since Monday our invoices show 16% instead of 19%."
}{
"summary": "Invoice PDF uses 16% VAT instead of 19%",
"body": "Reported in T-20931: invoices since Monday use 16%."
}Your monitoring reports a new error, and the agent creates an issue with what it knows.
{
"service": "checkout-api",
"error": "Order ord_88412 has no currency",
"first_seen": "2026-11-16T09:12:04Z",
"events_last_hour": 214
}{
"summary": "checkout-api: orders without a currency fail",
"body": "214 errors in the last hour, first seen at 09:12 UTC."
}Jira FAQ
More connectors
Cron Scheduler
Run an agent on any cron expression. connic hosts the scheduler for daily digests, hourly health checks, and weekly audits.
Inbound
Telegram
Power a Telegram bot with an agent. Read user messages, reply in the chat, push alerts to any channel.
Inbound · Outbound
Telnyx Messaging
Receive and send SMS/MMS, WhatsApp, and RCS messages through your Telnyx account. Connect agents to customer conversations and notifications.
Inbound · Outbound
Twilio Voice
Answer and place calls on your Twilio number with a voice agent. Use its tools and knowledge throughout one continuous conversation.
Sync · Outbound
WebSocket
Stream tokens to the browser over a live socket. Build chat UIs that keep session state across turns.
Sync
WhatsApp
Answer WhatsApp messages to your business number with an agent, files included. Reply within 24 hours or reach people with approved templates.
Inbound · Outbound