Connect Box to Brilliant directories

When something happens in Box, 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 Box to Brilliant directories

View example

Create a directory member from a signed Box application

When a Box Sign request changes, check whether it is complete and use the signed application to create a Brilliant Directories user when the required account details are present.

View example

Check onboarding packets against directory user fields

When a new file appears in a Box onboarding folder, retrieve Brilliant Directories user fields and report which details the packet appears to contain or leave unclear.

View example

Start directory onboarding when a Box folder collaborator is added

When a new collaboration is created on a Box folder, review available invite details and create a Brilliant Directories user only if required account information is supplied.

View example

Reference directory categories when Box content arrives

When a new item is added to a Box intake folder, retrieve Brilliant Directories data categories and include them as context in a review report for routing the material.

Supported Triggers and Actions

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

Box triggers

Brilliant directories actions

Recurring trigger

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

TriggerScheduled

Create User

This tool creates a new user record in the brilliant directories website database. it supports creating new users with essential details such as email, password, subscriptionid and optional parameters including name, company, contact details, and address information.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete User

This tool deletes an existing user record from the brilliant directories website database. it allows for the complete removal of a user record and, optionally, the deletion of the member's uploaded images.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

Get Data Categories

This tool fetches all data categories in a brilliant directories website. data categories are distinct from top categories and represent the various types of data organization within the system.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Get Lead Fields

This tool retrieves all available fields in the leads table from a brilliant directories website. it returns a json object containing a list of fields and their associated metadata (field name, field type, field label, whether the field is required, and if it is a system field) that can be used to understand the structure and metadata of lead-related fields.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

Get Reviews Fields

This tool retrieves all the available fields in the users reviews table from a brilliant directories website. it is a standalone tool that requires only authentication and provides a comprehensive list of review information such as review text, rating, timestamp, user identification fields, and any custom configured fields in the reviews system.

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

Get User Fields

This tool fetches all available fields from the users data table in your brilliant directories website. it provides a detailed list of available fields for user operations including creation, updating, and retrieval.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

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.