Connect Agenty to Cults

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

View example

Turn Website Research into Cults Model Shortlists

Use Agenty to gather model details from specified websites, then search Cults and return a focused shortlist for the same need.

View example

Review Cults Designer Storefronts on a Schedule

On a recurring schedule, use Agenty to research selected design sites and Cults to check designer storefronts for relevant makers.

View example

Organize Researched Cults Models into Collections

When a research request arrives, use Agenty to gather context and Cults to find models and organize relevant results into collections where supported.

View example

Turn Cults Download History into Follow-up

On a schedule, review available Cults download history and use Agenty to research relevant updates or documentation for downloaded models.

View example

Compare Cults Models Against Your Criteria

Send a comparison brief, use Agenty to gather supporting context, and query Cults for models that meet your stated criteria.

View example

Check Cults for Models from Your Watchlist

Run a scheduled Agenty research pass on watchlist topics and query Cults for relevant models, reporting the current results for review.

View example

Share Approved Site Designs to Cults

Use Agenty to research a selected design file and create a Cults share link for a new creation, after your site is approved by Cults.

View example

Review Approved Origins for Cults Sharing

On a schedule, retrieve approved Cults sharing origins to keep the current allowed domains visible to your team.

View example

Refresh Cults Collections from New Research

Use an incoming research request to have Agenty gather updated context and Cults search for models relevant to an existing collection theme.

Supported Triggers and Actions

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

Agenty triggers

Cults actions

Recurring trigger

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

TriggerScheduled

Get Approved Origins

Checks a creation page for sharing origin information.

ActionInstant

Webhook trigger

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

TriggerInstant

Cults GraphQL POST

Runs a query or mutation to browse or manage marketplace data.

ActionInstant

Share on Create (FR)

Creates a link to share a 3D file on a creation page.

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.