Find ready banners that may fit a Jira creative request
See whether an existing Adrapid banner can help move a changed Jira creative ticket forward.
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 Banners
Tool to list all banners and their statuses. use when you need to retrieve banners after creation or to audit existing banners. ensure you apply filters to narrow down results (e.g., status='ready').
Why this helps
Creative requests can stall while teams search through ad assets in a separate tool.
- Surface potentially relevant ready banners alongside an updated Jira request.
- Reduce manual searching across Jira and Adrapid.
- Give the team a clear report to review before reusing an asset.
Setup
Build it in a few focused steps.
- 1Connect Jira and Adrapid once in the Notis portal.
- 2Create an automation named Jira creative ticket banner check.
- 3Tell Notis: When a Jira issue changes, review its available request details, list Adrapid banners with status ready, identify banners that may fit, and send me the results for review.
- 4Pick the Jira Updated Issue trigger for the project you configure.
- 5Choose where run reports go, then test with one real updated creative issue.
Questions about this workflow
Will this create or edit a banner?
No. The available Adrapid action lists banners. The automation can report potentially relevant ready banners for review.
Which Jira changes start the automation?
Updates to an existing issue in the configured Jira project. Comment activity does not trigger this event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Adrapid. A trigger fires from one place; an action lands in another.
Jira triggers
Adrapid actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get API info
Tool to retrieve api root information. use when you need to discover the api's description and version details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get user and API info
Tool to get user account and api information. use when you need to retrieve authenticated user details and api versions.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Banners
Tool to list all banners and their statuses. use when you need to retrieve banners after creation or to audit existing banners. ensure you apply filters to narrow down results (e.g., status='ready').
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 Adrapid, 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 Adrapid.