Recheck available fonts when Jira requirements change
A change to an issue can change its typography needs too. Retrieve current Abyssale font options alongside the updated Jira request.
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 Fonts
Tool to list all available fonts, including custom and google fonts. use when you need to fetch font options before generating or editing designs.
Why this helps
Updated creative requirements can make an earlier font lookup irrelevant, but repeating it depends on someone remembering.
- Revisit font availability after relevant issue changes.
- Keep typography review close to evolving Jira requirements.
- Make font lookup a repeatable response to an updated request.
Setup
Build it in a few focused steps.
- 1Connect Jira and Abyssale once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create it.
- 3Describe the outcome in one instruction: when an existing Jira issue is updated, retrieve Abyssale fonts for review against the updated request details.
- 4Pick Jira Updated Issue as the trigger.
- 5Choose a report channel, then test with one real issue update that changes typography needs.
Questions about this workflow
Will every update be relevant to typography?
The trigger fires for changes to an existing issue, including status, assignee, or other fields. Instruct Notis to retrieve fonts when the updated details make typography review useful.
Can the action apply a font to a design?
No. The listed Abyssale action retrieves available font options; applying a font is not among the available actions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Abyssale. A trigger fires from one place; an action lands in another.
Jira triggers
Abyssale actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Test Abyssale Authentication
Tool to test api authentication via the /ready endpoint. use after configuring your api key to ensure credentials are valid before other requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Abyssale Project
Tool to create a new project to organize designs and images. use after deciding on a project name to group your templates and assets.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Designs
Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.
New Project
Triggered when a new project is added in Jira
Get Fonts
Tool to list all available fonts, including custom and google fonts. use when you need to fetch font options before generating or editing designs.
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 Abyssale, 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 Abyssale.