Connect Abyssale to Brex

When something happens in Abyssale, Notis takes the next step in Brex. 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 Abyssale to Brex

View example

Create a Brex budget for an approved Abyssale campaign

Turn an approved creative launch request into a Brex budget using the campaign name, owner, and limit supplied in the request.

View example

Record an Abyssale production purchase as a Brex expense

Create a Brex expense from an actual creative production purchase when a webhook supplies its receipt and transaction details.

View example

Create a Brex card for an approved Abyssale campaign

For an explicitly approved campaign request, create a Brex card assigned to the named user when the request includes the required details.

View example

Set a Brex campaign spend limit from an approved brief

Create a Brex Budget V1 spend limit when an approved creative brief includes the limit and required spending control details.

View example

Review recent Brex transactions for creative production

On a recurring schedule, retrieve Brex transactions and have Notis summarize entries relevant to Abyssale production using supplied campaign context.

View example

Summarize transactions from a Brex campaign budget

On a schedule, retrieve transactions for a specified Brex budget and summarize its activity for the creative campaign.

View example

Prepare a scheduled Brex expense review for production costs

Retrieve Brex expenses for a date range on a schedule and summarize records relevant to creative production for review.

View example

Check Brex budget availability for active creative work

On a schedule, retrieve Brex budgets and available amounts, then highlight specified campaign budgets that may need attention.

Supported Triggers and Actions

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

Abyssale triggers

Brex actions

Recurring trigger

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

TriggerScheduled

Create Budget

Create a budget for a department or project.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Webhook Group Members

Adds valid webhook subscriptions to an existing group; groups are for partner accounts only.

ActionInstant

Create Card

Create a card and assign it to a user.

ActionInstant

Archive Budget

Irreversibly archives a budget, blocking new expenses and transactions and removing it from active lists.

ActionInstant

Create Department

Create a department.

ActionInstant

Archive Spend Limit

Archives a spend limit, hiding it from the UI and preventing it from authorizing future transactions.

ActionInstant

Create Expense

Create an expense.

ActionInstant

Create Location

Create a location.

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.