Refresh contact context after Jira follow-up changes
When the owner or status of an issue changes, bring Amcards contact information into the follow-up review.
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 Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
Why this helps
A change in ownership or status can restart follow-up, and the relevant contact details may be buried in another tool.
- Refresh contact context when an issue changes.
- Keep follow-up review connected to the latest Jira issue details.
- Reduce the need to reopen Amcards for an initial contact scan.
Setup
Build it in a few focused steps.
- 1Connect Jira and Amcards once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to retrieve Amcards contacts after an issue changes in Jira and summarize relevant follow-up context based on the updated issue.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real issue update and review the report.
Questions about this workflow
Will adding a Jira comment start this automation?
No. Jira Updated Issue does not fire on comment activity. It fires when an issue field or other issue data changes.
Does Notis send an outreach message based on these contacts?
No. The available Amcards action retrieves contacts. Any outreach decision or sending step would need a separate supported action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Amcards. A trigger fires from one place; an action lands in another.
Jira triggers
Amcards actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
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 Amcards, 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 Amcards.