Jira
Connects to Jira Cloud via REST API using email + API token authentication. Provides full issue lifecycle management: create, get, update, delete, and search issues with JQL. Supports comments (add/list), file attachments, workflow transitions (get available transitions, execute transitions with optional comments), and project operations (list/get). All nodes accept either a Client ID from Connect node or direct credentials, making the Connect node optional. Search supports JQL queries with pagination.
| Namespace | Robomotion.Jira |
| Version | 1.1.0 |
| Category | Project Management, Dev Tools |
| Nodes | 15 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Jira and returns a Client ID. |
| Disconnect | Closes a Jira connection. |
| Create Issue | Creates an issue in Jira. |
| Get Issue | Gets an issue in Jira. |
| Update Issue | Updates an issue in Jira. |
| Delete Issue | Deletes an issue in Jira. |
| Search Issues | Searches issues in Jira. |
| Get Transitions | Gets transitions in Jira. |
| Do Transition | Do Transition — see the properties below. |
| Add Comment | Adds a comment in Jira. |
| List Comments | Lists comments in Jira. |
| List Projects | Lists projects in Jira. |
| Get Project | Gets a project in Jira. |
| Add Attachment | Adds an attachment in Jira. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
14 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Create Issue, Get Issue, Update Issue, Delete Issue, Search Issues, Get Transitions, Do Transition, Add Comment, List Comments, List Projects, Get Project, Add Attachment.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.