Refresh caller context when an issue changes
A changed issue can be a cue to review the number again. Get the returned caller details with the updated Jira context in one report.
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
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Why this helps
A phone number assessment can be overlooked when the Jira issue changes status or ownership.
- Recheck numbers when an issue is updated.
- Include the updated issue context with the lookup result.
- Avoid manual navigation between Jira and a phone lookup.
Setup
Build it in a few focused steps.
- 1Connect Jira and Callerapi once in the Notis portal.
- 2Create an automation in Automations, then choose a name and report channel.
- 3Tell Notis to look up the E.164 phone number on each updated issue and summarize the returned Callerapi details with the issue context.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue update that contains an E.164 phone number.
Questions about this workflow
Will this run when someone comments on an issue?
The listed Jira Updated Issue trigger does not fire on comment activity. It fires when an existing issue in the configured project is changed.
Does Callerapi determine what action our team should take?
Callerapi returns phone number information. You can ask Notis to summarize that information against review guidance you provide, but the workflow should not assume an unprovided policy.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Callerapi. A trigger fires from one place; an action lands in another.
Jira triggers
Callerapi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
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.
Connect any two apps with Notis in the middle.
Jira and Callerapi, 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 Callerapi.