Recheck Amazon review analysis requests after Jira changes
When a review analysis ticket changes, refresh the view of the request queue it refers to and make the next step clearer.
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 Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Why this helps
A changed analysis brief can leave people working from an outdated view of the Amazon review requests waiting in a collection.
- Recheck the identified collection after a Jira issue change.
- Summarize the queue alongside the updated brief.
- Flag when the changed issue lacks enough information to identify the collection.
Setup
Build it in a few focused steps.
- 1Connect Jira and Asin data api once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to list the collection requests identified in the updated issue and summarize them against the revised review analysis brief.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real updated review analysis issue that identifies the collection and revised scope.
Questions about this workflow
Will this detect changes to Jira comments?
No. The Jira Updated Issue trigger does not fire on comment activity. It fires when an issue field changes.
Can Notis tell whether the collection changed since the last run?
The listed action returns the current collection requests. A prior snapshot or baseline is not provided by that action, so a before-and-after comparison would need that information supplied separately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Asin data api. A trigger fires from one place; an action lands in another.
Jira triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
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 Asin data api, 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 Asin data api.