Check text broadcast history alongside Jira updates
See the relevant Dialmycalls text broadcast history in a run report when an existing Jira issue changes.
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
List Text Broadcasts
Tool to list all outgoing text broadcasts. use when you need to review past text broadcasts with filters for date, status, and pagination.
Why this helps
Text follow-up can be repeated or missed when broadcast history and issue status are checked separately.
- Bring text broadcast history into issue review
- Reduce duplicate manual lookups
- Use date and status filters when relevant
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, ask Notis to list text broadcasts with the relevant date or status filters and summarize results for the updated issue.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue update and review the report.
Questions about this workflow
Does this send an SMS?
No. The selected action lists past text broadcasts. It does not send an SMS.
Can I narrow the returned broadcast list?
The List Text Broadcasts action supports date, status, and pagination filters. State relevant criteria in your instruction.
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.