Turn Jira lead issues into Callingly call requests
Capture a lead call request in Jira and have Notis create the corresponding outbound call record in Callingly.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
Why this helps
A call request can sit in Jira while someone remembers to re-enter it in Callingly.
- Reduce re-entry between Jira and Callingly.
- Keep lead call requests tied to the issue that prompted them.
- Let Notis identify missing call details before creating a call.
Setup
Build it in a few focused steps.
- 1Connect Jira and Callingly once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to create a Callingly outbound call for each new Jira issue that contains a lead call request and the required call and lead details.
- 4Pick Jira New Issue as the trigger.
- 5Choose a report channel, then test with one real Jira lead issue.
Questions about this workflow
Does this run for every Jira issue?
It starts on new issues in the Jira project you configure. The instruction can tell Notis to act only when the issue represents a lead call request and includes the required details.
What if the issue is missing call details?
Tell Notis to report missing information instead of creating an incomplete outbound call record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Callingly. A trigger fires from one place; an action lands in another.
Jira triggers
Callingly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Activate/Deactivate Client Account
Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
New Project
Triggered when a new project is added in Jira
Create Client
Tool to create a new client. use when adding a new client to your callingly account.
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.
Create Team
Tool to create a new team. use when setting up a team configuration before adding agents.
Create Webhook
Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".
Delete Agent
Tool to delete an agent. use when permanently removing an agent after confirming the agent id.
Delete Client
Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.
Connect any two apps with Notis in the middle.
Jira and Callingly, 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 Callingly.