Give every GitHub release its own creative workspace
A release is a useful cue to start organizing its visuals. Have Notis create an Abyssale project when release details change.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
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.
Why this helps
Release graphics and launch assets can end up scattered across projects, making it harder to find the right creative work later.
- Keep release creative work grouped in a dedicated project.
- Reduce manual setup when release details change.
- Start organizing launch assets from the release event.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Abyssale once in the Notis portal.
- 2Create a new automation in Automations, or tell Notis what outcome you want from a channel you already use.
- 3In one instruction, ask Notis to create an Abyssale project to organize the creative assets for the changed GitHub release.
- 4Pick the GitHub Release State Changed trigger and choose where run reports should go.
- 5Test the automation with one real release change.
Questions about this workflow
What starts this automation?
A change to the monitored GitHub release, such as an update to its title, notes, publication status, target, or attached assets.
Does this generate release images?
No. The available Abyssale action creates a project to organize creative work. It does not generate images or videos.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Abyssale. A trigger fires from one place; an action lands in another.
GitHub 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 Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Get Designs
Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub 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.