Connect Acculynx to Brilliant directories

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

View example

Turn Acculynx leads into directory inquiries

Send a new Acculynx lead to Brilliant Directories as an inquiry, keeping the contact and job context together.

View example

Start directory onboarding when an Acculynx job is ready

Use a webhook to create a Brilliant Directories user from an Acculynx job handoff when the request includes the required account details.

View example

Refresh directory lead context from an Acculynx project update

Update an existing Brilliant Directories lead with relevant project details supplied in an Acculynx webhook request.

View example

Update a directory member profile from an Acculynx handoff

Refresh a Brilliant Directories user profile when an Acculynx request supplies a known user ID and changed contact or company details.

View example

Find directory members for pending Acculynx handoffs

On a schedule, search Brilliant Directories for members matching the Acculynx handoff records supplied to Notis.

View example

Review directory content categories for Acculynx job handoffs

Schedule a Brilliant Directories category check to confirm which post types are available before routing supplied Acculynx job content.

View example

Check lead fields before routing Acculynx inquiries

Retrieve Brilliant Directories lead field requirements on a schedule so your team can prepare Acculynx inquiry handoffs with fewer surprises.

View example

Review member transaction context for Acculynx project follow-up

Retrieve transaction history for a known Brilliant Directories member and include the supplied Acculynx project context in a scheduled review.

Supported Triggers and Actions

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

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