Apply caller ID updates from Jira work changes
Use an issue update to cue a specific change to your Dialmycalls caller ID details, with the caller ID id and new value supplied.
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
Update Caller ID
Tool to update an existing caller id by id. use when you need to change its phone number or display name.
Why this helps
Caller ID information can lag behind operational changes when updates rely on someone remembering to maintain it.
- Reduce missed caller ID maintenance
- Keep phone number or display name changes tied to issue work
- Specify exactly which caller ID to update
Setup
Build it in a few focused steps.
- 1Connect Jira and Dialmycalls once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, specify the Jira update condition, caller ID id, and new phone number or display name to apply.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue update that matches the condition.
Questions about this workflow
Can it choose which caller ID to update?
Provide the caller ID id in the instruction or issue context. The action updates an existing caller ID by id.
Will it verify the new caller ID?
This action updates an existing caller ID's phone number or display name. Verification behavior is not specified in the supplied event details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Dialmycalls. A trigger fires from one place; an action lands in another.
Jira triggers
Dialmycalls actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Access Account
Tool to add a new access (sub) account. use when you need to delegate dialing capabilities to another user after setting up your master account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Contact
Tool to add a contact to your contact list. use when you need to store a new contact's phone (and optional name, email, or group) before sending messages.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Add Group
Tool to add a new contact group. use after deciding the group name to organize recipients into groups.
New Project
Triggered when a new project is added in Jira
Delete Access Account
Tool to delete an access (sub) account by id. use when removing a sub account after deprovisioning.
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.
Delete Caller ID
Tool to delete a caller id. use when you need to permanently remove an existing caller id no longer in use.
Delete Contact
Tool to delete a contact by id. use when you need to permanently remove a contact from your list.
Delete Group
Tool to delete a contact group by id. use when you need to remove an existing contact group after confirming its id.
Delete Recording
Tool to delete a recording by id. use when you need to permanently remove a custom recording after confirming its recording id.
Connect any two apps with Notis in the middle.
Jira and Dialmycalls, 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 Dialmycalls.