Create directory members from approved Notion applications
When an application is added to your Notion database, ask Notis to create a Brilliant Directories user for applicants marked approved.
When something happens in Notion, 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
Fires when a new comment is created in the accessible workspace.
Do this · Action
Creates a Brilliant Directories user or member account with a password and membership plan.
When an application is added to your Notion database, ask Notis to create a Brilliant Directories user for applicants marked approved.
Use a Notion profile status change as the signal for Notis to create a Brilliant Directories user account.
When you create a Notion page requesting the current user-field reference, ask Notis to retrieve Brilliant Directories user fields for your setup notes.
When a Notion data source schema changes, ask Notis to retrieve current Brilliant Directories user fields for comparison during your integration review.
A new Notion launch plan can prompt Notis to retrieve Brilliant Directories data categories for planning member or listing organization.
When you create a Notion campaign brief, ask Notis to retrieve Brilliant Directories lead-field metadata to inform follow-up planning.
A content update to a Notion feedback plan can prompt Notis to retrieve Brilliant Directories review-field metadata for your review process.
When a member's onboarding subpage is added under a Notion cohort page, ask Notis to create a Brilliant Directories account for the approved member.
Use a Notion comment that clearly approves an applicant as a cue for Notis to create their Brilliant Directories user account.
Notis builds workflows that link Notion to Brilliant Directories. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Creates a Brilliant Directories user or member account with a password and membership plan.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Adds a photo entry to a user’s portfolio album.
Fires when a new comment is created in the accessible workspace.
Deletes a Brilliant Directories user and related data, optionally including uploaded image files.
Fires when a new database container is created.
Creates a data category for a content type on the website.
Fires when a new data source is created in the workspace.
Creates a single-image post in the website database.
Fires when a data source’s columns are added, removed, or renamed.
Returns a fixed list of lead field definitions after checking API connectivity.
Fires when the body content of an accessible page is updated.
Creates a lead from a visitor inquiry or contact request.
Fires when a new page is created in the accessible workspace.
Returns a fixed set of review field definitions without making an API call.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Brilliant Directories, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Brilliant Directories.