Make important Jira issue updates harder to miss
When a Jira issue changes, let a voice agent bring the update to someone's attention without another manual chase.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Make a phone call from agent
Initiate calls
Why this helps
Status and assignment changes can disappear in a stream of work, leaving the next person unaware that action is needed.
- Bring a changed issue to someone's attention quickly.
- Make status and assignee changes easier to follow up on.
- Use one instruction to describe which updates merit a call.
Setup
Build it in a few focused steps.
- 1Connect Jira and Bolna once in the Notis portal.
- 2Create an automation and describe the call outcome in one instruction.
- 3Pick Jira Updated Issue as the trigger.
- 4Choose where run reports should go, then test with one real updated issue.
Questions about this workflow
What changes can start this workflow?
Jira's Updated Issue event fires when an existing issue in the configured project changes, including status, assignee, or another issue field.
Does it run when someone comments?
No. The supplied event details say comment activity does not fire this trigger.
Can I limit calls to certain changes?
Tell Notis in your instruction which issue changes should matter. The trigger itself is the Jira Updated Issue event, and no filters are configured in setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bolna. A trigger fires from one place; an action lands in another.
Jira triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Fetch all batches by agent id
List all batches for agent
New Project
Triggered when a new project is added in Jira
Get all agents
List all agents
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Get all phone numbers
List all phone numbers for your account
Get execution by id
Retrieve specific execution by `execution id`
Make a phone call from agent
Initiate calls
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
Jira and Bolna, 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 Bolna.