Update Jira issue context from Apilio state changes
When an Apilio state change affects work already being tracked, refresh the Jira issue context while the details are in front of you.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A ticket can keep outdated device or automation context after an operational state changes.
- Keep related Jira ticket context aligned with incoming state details
- Avoid manually copying state changes into issue descriptions
- Make operational changes easier for ticket readers to understand
Setup
Build it in a few focused steps.
- 1Connect Apilio and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to find the relevant Jira issue and update it with the Apilio state change details included in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test using one real state change and verify the intended issue was updated.
Questions about this workflow
How does Notis know which issue to update?
Include a Jira issue key or enough identifying context in the webhook request or instruction. If no relevant issue can be identified, the automation cannot safely choose one.
Can it use Apilio data that was not sent to the webhook?
The instruction can use data accessible to the connected apps, but any required state detail that is not available must be included in the request or supplied by you.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apilio to Jira. A trigger fires from one place; an action lands in another.
Apilio triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Apilio and Jira, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.