Connect 0CodeKit to Abyssale

When something happens in 0CodeKit, Notis takes the next step in Abyssale. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from 0CodeKit to Abyssale

View example

Validate Abyssale credentials before an asset run

Check Abyssale API access from an incoming request and report whether the connection is ready for creative automation.

View example

Schedule a weekly Abyssale connection check

Run a recurring Abyssale authentication test and send a short status report before planned design work.

View example

Open an Abyssale project for an incoming campaign brief

Create a named Abyssale project whenever a campaign brief arrives by webhook, keeping new creative work grouped from the start.

View example

Create a monthly content project shell

Create a fresh Abyssale project on a recurring schedule so each content cycle has a dedicated workspace.

View example

Retrieve designs for a requested campaign type

Use an incoming request to fetch Abyssale designs filtered by the campaign category or type supplied by the requester.

View example

Send a weekly design library digest

Retrieve Abyssale designs on a schedule and send a concise digest of available templates for the team.

View example

Find brand font options for a design request

Look up available Abyssale fonts when a request arrives, then return options the requester can use for the next design decision.

View example

Run a monthly font inventory review

Retrieve the current Abyssale font inventory on a schedule and report additions or notable options for the team.

View example

Triage template options for an urgent request

Return a concise shortlist of Abyssale designs for an urgent incoming request, based on the category or type provided.

Supported Triggers and Actions

Notis builds workflows that link 0CodeKit to Abyssale. A trigger fires from one place; an action lands in another.

0CodeKit triggers

Abyssale actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Get Designs

Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.

ActionInstant

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.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.