Connect Pipedrive to Dromo

When something happens in Pipedrive, Notis takes the next step in Dromo. 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 Dromo

View example

Reconcile Dromo uploads when a Pipedrive deal is created

Review Dromo uploads as soon as a new Pipedrive deal arrives and report matching or missing import activity.

View example

Check Dromo imports from a new Pipedrive note

Use new Pipedrive notes as a prompt to retrieve relevant Dromo uploads and summarize the latest import status.

View example

Review Dromo upload readiness for a new organization

When a Pipedrive organization is created, retrieve related Dromo uploads and report whether onboarding data is ready.

View example

Upload a deal import file to Dromo from a webhook

Send a signed Dromo upload URL and raw deal import bytes to Notis, then upload the file automatically.

View example

Upload organization onboarding data to Dromo

Use a webhook to upload an organization onboarding dataset to a Dromo headless import with supplied signed URL and bytes.

View example

Upload a file referenced in a Pipedrive note to Dromo

Forward a file and signed Dromo upload URL from a note processing webhook into a headless import.

View example

Review Dromo upload exceptions each morning

Run a daily Dromo upload list review and summarize failed, incomplete, or unexpectedly missing imports for the team.

View example

Summarize weekly Dromo upload activity

Retrieve Dromo uploads on a schedule and produce a concise trend summary for operational planning.

View example

Find the latest Dromo upload for a new deal

When a deal is created, retrieve Dromo uploads and report the most recent relevant dataset and its status.

Supported Triggers and Actions

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

Pipedrive triggers

Dromo actions

Recurring trigger

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

TriggerScheduled

List Uploads

Tool to retrieve a list of all uploads stored by dromo for your organization. use when you need to paginate or filter uploads.

ActionInstant

Webhook trigger

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

TriggerInstant

Upload File To Headless Import

Tool to upload a file to a headless import. use after obtaining a signed upload url from dromo. performs an http put of raw bytes to the provided signed url.

ActionInstant

New Deal Received Trigger

Triggered when a new deal is created in Pipedrive

TriggerInstant

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.