Automate Jira issues from InfraNest and respond to Jira events
Connect Jira and InfraNest for two-way automation. Jira webhooks trigger InfraNest rules; automations create issues, add comments, and transition statuses in Jira.
Connect Jira to InfraNest via OAuth or API token to link issue workflows with infrastructure automation. Once connected, you can set up two-way automation:
- Trigger automations from Jira webhooks: When an issue is created, updated, or commented on, InfraNest receives the event (issue type, priority, assignee, actor, previous state) and can trigger any InfraNest automation rule.
- Create issues in Jira: An automation rule can create a new issue in a chosen project and issue type, with fields mapped from the triggering event (like DNS record changes or certificate expiry).
- Comment on issues: Add comments to existing Jira issues from an automation rule, embedding context or status updates from your infrastructure.
- Transition issues: Move an issue to a different status as part of an automation workflow.
- Link issues back to InfraNest: Add a remote link from a Jira issue to the InfraNest resource that triggered it, keeping both systems in sync.
- Live pickers for projects and users: The automation builder looks up your Jira projects, issue types, assignable users, and priority levels in real time, so you pick them from a list rather than typing IDs.
NoteInfraNest does not manage Jira Service Management, sprints, or boards. Jira remains the source of truth for issue creation and status; InfraNest automates responses to Jira events and can update or comment on existing issues.
What it looks like in InfraNest
When this happens
Domain expiring
A domain is approaching its expiry date.
Runs at 09:00 · Europe/Amsterdam · it’s 15:49 there now
Next runs:Sat 19 Sept, 09:00Sun 20 Sept, 09:00Mon 21 Sept, 09:00
This automation only runs when you click “Run now”.
Only if — optional filters
MatchAllAnyNoneof these conditions
Tip: a value can reference another field or the time using a placeholder.
Do this — actions run in order, stop at the first failure
In plain English
When Domain expiring if Days left less or equal 15, then Require approval, Set auto-renew and Send notification.
What you can do
Once Jira is connected, this is what InfraNest can do with it.
- Trigger automations when Jira issues are created or updated
- Create issues in Jira from infrastructure events
- Transition issue statuses automatically
- Add comments to Jira issues from rules
- Link Jira issues to InfraNest resources
- Pick projects and users from live Jira data
Not supported
InfraNest does not import or manage Jira projects as inventory, and does not handle Jira Service Management, sprints, or board operations.
How to connect it
- 1
Authorize with Jira
In InfraNest Settings → Providers → Jira, click Connect. You'll be sent to Atlassian to log in and approve the scopes (read and write access to Jira work items and user data). Alternatively, if your Jira is self-hosted, enter your Jira site URL, Atlassian account email, and an API token.
- 2
Confirm your workspace
After authorization, InfraNest displays your Jira workspace details. Verify it matches the account where you want to create and update issues.
- 3
Set up a Jira webhook (optional)
To trigger InfraNest automations from Jira, go to your Jira project settings → Webhooks and create a new webhook pointing to the URL InfraNest provides (visible in the Jira provider settings). Select the events (issue created, issue updated, comment created) and save.
- 4
Build an automation rule
In InfraNest Automations, create a rule with a Jira webhook as the trigger, or a different trigger that outputs a Jira action (create issue, comment, transition, or add remote link). Use the live pickers to select projects, issue types, and assignees, then map event fields to Jira fields.
That’s it — Jira is connected.
Full setup guideSet up with AI
I use Jira, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: OAuth (one-click Atlassian login) or API token with read:jira-work, write:jira-work, read:jira-user scopes. Walk me through creating that in Jira: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
What syncs
What InfraNest keeps in sync with Jira.
| Jira webhook events | Issue created, updated, or commented on, carrying issue type, priority, assignee, actor, and previous state. |
| Jira projects and issue types | Live lookup of available projects and issue types for use in automation actions. |
| Assignable users and priorities | Real-time picker data for assigning issues and setting priority in automation rules. |
Questions
#Will this change anything in Jira?
No. InfraNest only creates new issues, adds comments, transitions status, and adds remote links when a rule is configured to do so. Jira remains the source of truth; InfraNest responds to events.
#Can I connect multiple Jira instances?
Yes. Add multiple Jira providers in InfraNest Settings, then reference the one you need in each automation rule.
#What happens if I revoke the API token?
Webhooks and automation rules using Jira actions will fail. Reconnect with a new token in Settings → Providers to restore them.
#Do I need to set up webhooks manually?
Yes. InfraNest provides the webhook URL in the Jira provider settings; you create the webhook in your Jira project settings and select the events to send.
Often connected together
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes