Connect Adrapid to Brilliant directories

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

View example

Turn an Adrapid campaign brief into a Brilliant Directories article

Use an Adrapid webhook payload containing a finished campaign brief and approved copy to create a Brilliant Directories content post.

View example

Refresh a Brilliant Directories post from an Adrapid revision

Apply a supplied Adrapid revision to an existing Brilliant Directories post when the payload includes its post ID and updated content.

View example

Add an Adrapid creative to a member album

Create an album photo in Brilliant Directories from a supplied Adrapid image export and member ID.

View example

Revise a member album image from Adrapid

Update an existing Brilliant Directories album photo when Adrapid sends a corrected title, description, keywords, or status.

View example

Create a Brilliant Directories member from an Adrapid onboarding payload

Create a new directory user when an Adrapid export contains approved member details and subscription information.

View example

Apply an Adrapid member profile revision

Update an existing Brilliant Directories user with approved profile changes from an Adrapid webhook payload.

View example

Import an Adrapid lead export into Brilliant Directories

On a schedule, process a supplied Adrapid lead export and create authorized lead records in Brilliant Directories.

View example

Update a directory lead from Adrapid qualification notes

Apply approved qualification changes to an existing Brilliant Directories lead when the Adrapid payload includes its lead ID.

View example

Process an Adrapid unsubscribe export

On a schedule, create unsubscribe records in Brilliant Directories from a supplied Adrapid suppression export.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Brilliant directories. A trigger fires from one place; an action lands in another.

Adrapid triggers

Brilliant directories actions

Recurring trigger

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

TriggerScheduled

Create User

Creates a new user account on a directory website.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Album Photo

Adds a photo entry to a user’s portfolio album.

ActionInstant

Delete User

Deletes a user record and can also remove the member’s uploaded images.

ActionInstant

Create Data Category

Creates a data category for a content type on the website.

ActionInstant

Create Data Post

Creates a single-image post in the website database.

ActionInstant

Get Lead Fields

Retrieves the available fields for leads.

ActionInstant

Create Lead

Creates a lead from a visitor inquiry or contact request.

ActionInstant

Get Reviews Fields

Retrieves metadata about the available review fields.

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.