Connect Addressfinder to Brex

When something happens in Addressfinder, 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 Addressfinder to Brex

View example

Add verified vendors to Brex

Check a vendor's contact details with Addressfinder, then create the vendor in Brex from a submitted intake request.

View example

Create Brex users from verified contact details

Check a submitted person's email, phone, and address with Addressfinder before creating a Brex user.

View example

Add verified office addresses to Brex

Check an address submitted to Notis with Addressfinder, then create a Brex location when it meets your criteria.

View example

Create vendor cards from verified supplier requests

Check supplier contact details with Addressfinder, then create a Brex vendor card from a submitted request.

View example

Create Brex cards from verified employee requests

Check contact details in an employee card request with Addressfinder, then create a Brex card when the request meets your rules.

View example

Create Brex expenses from verified submissions

Check contact details included in an expense submission with Addressfinder, then create the Brex expense from the supplied expense information.

View example

Process a scheduled batch of verified vendor requests

On a schedule, check a provided batch of vendor details with Addressfinder and create qualifying vendors in Brex.

View example

Process a scheduled batch of office locations

On a schedule, check available office address submissions with Addressfinder and create qualifying Brex locations.

View example

Process a scheduled batch of new user requests

Check available new user contact details with Addressfinder on a schedule before creating Brex users.

Supported Triggers and Actions

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

Addressfinder 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.