Connect Pipedrive to Cults

When something happens in Pipedrive, 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 Pipedrive to Cults

View example

Research Cults models for every new Pipedrive deal

When a Pipedrive deal arrives, search Cults for relevant 3D models and summarize useful matches for the deal.

View example

Plan a Cults collection from a new deal

Use new deal context to propose a focused Cults collection and explain which models belong in it.

View example

Turn Pipedrive notes into a Cults model brief

When a new Pipedrive note is added, search Cults and produce a concise model brief based on the note.

View example

Find Cults designers mentioned in Pipedrive notes

Use new Pipedrive notes to identify relevant Cults designer storefronts and summarize why they fit.

View example

Create a Cults share link from a Pipedrive file note

When a Pipedrive note contains an eligible 3D file reference, generate a Cults one-click share link in French locale.

View example

Research Cults storefronts for a new organization

When a new Pipedrive organization is created, find Cults storefronts that match its stated profile or needs.

View example

Review Cults download history for a new organization

Use a new organization event to retrieve relevant Cults download history and highlight useful prior assets.

View example

Check Cults sharing origins for a new deal

When a new deal includes a sharing need, retrieve approved Cults origins so the next step uses an allowed domain.

View example

Refresh Cults approved origins from a Pipedrive note

Use a new note that mentions sharing or an approved domain to retrieve the current Cults origin list.

Supported Triggers and Actions

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

Pipedrive triggers

Cults actions

Recurring trigger

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

TriggerScheduled

Get Approved Origins

Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.

ActionInstant

Webhook trigger

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

TriggerInstant

Cults GraphQL POST

Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.

ActionInstant

New Deal Received Trigger

Triggered when a new deal is created in Pipedrive

TriggerInstant

Share on Create (FR)

Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.

ActionInstant

New Note Received Trigger

Triggered when a new note is created in Pipedrive

TriggerInstant

New Organization Received Trigger

Triggered when a new organization is created in Pipedrive

TriggerInstant

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.