Jira
Everyday Jira REST operations — create, search, transition, comment, link, log work, attach — against Jira Cloud and Server/Data Center.
- SDK
- Go
- Protocol
inflowv1- Actions
- 14
- Version
- v0.1.0
- Author
- mehdi-shokohi
- Runs on
- Any
inflowv1host - Categories
- DevOps and infrastructureIssue tracking
Reach for it when
Jira as a participant in the process rather than the place work gets copied into afterwards.
The use people don't expect
Fourteen actions means a flow can run the whole ticket lifecycle — transition it, log the work, link the duplicate, attach the evidence — so the board stays true without anyone updating it by hand.
A flow that uses it
Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.
The ticket as the flow's own state
Starts withA finding, an alert, a request.
- JIRA
Searches first. If this already exists, link instead of opening a second one.
- JIRA
Creates it, with the evidence attached at creation.
- Human in the Loop
Someone works it; the flow waits on the transition.
- JIRA
Transitions, comments, logs the work.
- POSTGRES
Records the cycle time, so the next quarter's argument has numbers.
What you getThe search-before-create step is the whole difference between automation that helps and automation that floods the board.
The reference, not the pitch
This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.
Near it in the catalog
Read-only GitHub — repositories, activity, and the security surface — without the plugin holding a token.
NUCLEINucleiTemplate-based vulnerability scanning inside a flow, with templates chosen by filter rather than one at a time.
SCRAPLIScrapliNetwork devices over SSH or Telnet — Cisco, Arista, Juniper — with optional TextFSM parsing.