swfte
Contact Us

Integration guide

Jira integration for AI agents and workflows

Swfte Studio has a Jira node that can list projects, create an issue and search issues with JQL, according to its shipped data. An agent can draft a ticket, and a named person approves it before the create action runs.

These three actions are the whole list this page relies on. The shipped template’s description also mentions updating an issue, but its nodes do not contain that step, so nothing below depends on it. The catalogue lists Jira under development and productivity.

Built in Swfte Studio, run as a governed workflow, and held to the same rules as any governed agent.

Build with AITalk to our team

Jira at a glance

Catalogue
Development, Productivity
Actions in the shipped data
3 (2 read, 1 write)
Credential type shown
jiraSoftwareCloudApi
MCP server
None in the MCP tool list
Shipped templates that use it
Jira Issue Workflow

What you can do with Jira

Every action below is read from a node in a shipped workflow template. Nothing is listed that the data does not show.

Jira actions in the shipped workflow templates
ActionTypeOperationWhat the data shows
List ProjectsReadproject.getAllLists the projects the credential can see. Use it to let the workflow pick, or confirm, the target project.
Create IssueWriteissue.createCreates an issue in a project with a summary, a type (the template uses Task) and a description.
Search IssuesReadissue.getAllFinds issues with a JQL query. The template matches on project and summary and caps the result at five.

Two reads and one write. Commenting, transitioning and assigning are not in the shipped data, so the designs below leave a person to move tickets along.

The shipped template starts from a manual trigger. A Jira-side event, such as an issue being created or moved, is not in the data: <Jira trigger events - founder to fill>.

Tickets are a shared queue, so duplicates and noise are the real risk

In Jira, an issue is a commitment on someone’s backlog. An agent that files too many, or files near-copies of a ticket that already exists, creates work for the people who have to triage it. The JQL search action is the guard against that: before any create, search the project for a matching summary, and let a person decide when the match is unclear.

The shipped template shows the pattern in miniature. It lists projects, picks one, creates a task with a summary and a description, then searches the project for issues whose summary matches, newest first, and limits the result to five. A production version adds the approval and decides what counts as a duplicate.

How to connect Jira

The shipped template names the credential type jiraSoftwareCloudApi, which is the Jira Software Cloud connection.

  1. 01

    Create the credential

    Add a Jira Software Cloud credential in Studio. Use a service account, so the history in Jira shows the integration and not a colleague.

  2. 02

    Limit the projects

    Give the account access to the projects the workflow serves. The list-projects action returns what the account can see, so a narrow account gives a short list.

  3. 03

    Search before you create

    Add the JQL search first and read its output. The summary match in the shipped template is a starting rule that you will want to refine.

  4. 04

    Gate the write

    Put the approval step between the draft and the create action, addressed to the team’s triage owner.

Three governed Jira workflows to build in Studio

Each has a label. A starting point builds on a shipped template, which is an integration test with no approval step. A design is intent only.

Duplicate-aware ticket intake

Starting point

Builds on the shipped template “Jira Issue Workflow” (6 nodes), which you can find in the template library.

Turn a request from a form or an email into a ticket only after a person has seen the closest existing matches.

  1. An agent node turns the request into a summary and a description.
  2. The search action looks in the project for issues with a similar summary.
  3. A human-input step shows the triage owner the draft and the matches, with approve and reject branches.
  4. On approval, the create action files the issue. If the owner rejects the draft, the run stops with the reason attached.

Where the approval sits. The shipped template creates its issue and then searches. Reversing that order and adding the approval are the changes to make.

Stale-ticket digest for the team lead

Designed

Give a team lead a weekly list of tickets nobody has touched, without writing the JQL by hand each time.

  1. A search action runs a JQL query for open issues that have not been updated for a period you choose.
  2. An LLM node groups the results by project and drafts one line per ticket.
  3. The digest goes to the lead alone through the Slack post-message action.
  4. Nothing is written to Jira.

Where the approval sits. A read-only workflow needs no gate. Limit the audience of the Slack message to people who can already see the tickets.

Incident follow-up tickets

Designed

After an incident channel closes, turn the agreed follow-ups into tickets with one approval for the whole batch.

  1. Read the incident channel with the Slack get-history action, using a limit you set.
  2. An agent proposes follow-up tickets, each with a summary and a suggested project.
  3. The incident commander approves or rejects the list in a human-input step.
  4. For each approved item, the create action files the issue, after a JQL check for an existing ticket.

Where the approval sits. One approval covers the batch and the commander sees the full list at once. If the list is wrong, rejecting it files nothing.

Shipped template
A governed template with its approval step already in it ships in the platform.
Starting point
A shipped template runs the same actions. It is an integration test with no approval step, so you add the gate.
Designed
Design intent. It uses the actions listed above plus generic nodes, and nothing has been built as a template.

Approvals and records for Jira

Jira is where a team’s commitments live, so the controls follow who is allowed to add to a backlog.

Needs a person’s approval

  • Creating an issue in a project owned by another team.
  • Any batch of more than one issue created from a single run.
  • Creating issues from text that came from outside the company, such as a customer email.

Can run without one

  • Listing projects for a picker.
  • Searching a project the run’s own team owns, to build a digest.

What is recorded

  • Each search and each create, in the order they ran.
  • Who approved the draft, and when.
  • A policy decision, such as the redaction of a customer’s name, taken before the summary reached Jira.

A Swfte approval and a Jira workflow approval are different things. The Swfte step pauses the Swfte run before it calls Jira, and Jira’s own statuses and transitions are untouched. Use both where the process needs both.

A policy step in a design below describes the intent. The policy engine acts only on runs that have a policy attached, and a self-serve way to author policies is not something we describe as built.

Swfte’s own security position and any attestations are on the trust page. How approvals, policy and records fit together is on the governed agents page.

Comparing tools for Jira work

These comparison pages are dated and sourced. Each says who should pick the other tool.

  • n8n alternatives

    The n8n comparison covers hosting, approvals and audit differences for ticket automation.

  • Zapier alternatives

    The Zapier comparison covers when a simple trigger-and-action tool is enough for ticket creation.

  • Best automation platforms

    How automation platforms compare on governance, approvals and records, with the method shown.

Jira questions

Can an agent create Jira tickets without anyone approving?

Yes, if you build it that way, because the approval is a step you add. For anything that lands on another team’s backlog we recommend a named triage owner as the approver. The agent proposes and the person decides.

Can Swfte transition or comment on Jira issues?

Not in the shipped data, which has list projects, create issue and search issues. The template description mentions an update, but no node does it. Check the node in Studio before you rely on more.

How do I avoid duplicate tickets?

Search first with JQL, show the matches to the approver, and let them reject the draft. The shipped template searches after it creates, so reverse that order and add the approval.

Is this the same as a Jira approval?

No. Jira has its own workflow statuses and transitions. A Swfte approval pauses the Swfte run before it calls Jira. The two can sit side by side, and a ticket created by a Swfte run can then go through whatever approvals you have set up in Jira.

Which Jira credential does the node use?

The shipped template names jiraSoftwareCloudApi, the Jira Software Cloud credential type. Whether other Jira editions are supported is <Jira editions supported - founder to fill>.

Keep reading

Build a governed Jira workflow

Begin with a read-only workflow on a test account, then add one write with an approval in front of it.

Build with AITalk to our team

Build this in Studio

Describe what you need in plain language. Studio builds the agents and workflows, and you keep every version.

Start building freeLearn more