Connect Pipedrive to Documint

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

View example

Review proposal templates when a new deal arrives

List Documint templates and identify the best proposal options for each new Pipedrive deal.

View example

Check a Documint template for every new deal

Retrieve the requested Documint template details when a new Pipedrive deal needs a specific document.

View example

Review related Documint documents for new deals

List Documint documents so the team can check prior proposals or paperwork related to a new Pipedrive deal.

View example

Triage Documint templates from Pipedrive notes

Use a new Pipedrive note to review and categorize the Documint templates relevant to the request.

View example

Inspect a Documint template requested in a note

Retrieve the Documint template named in a new Pipedrive note and summarize its current configuration.

View example

Apply approved Documint template updates from notes

Use an explicit Pipedrive note instruction to update a Documint template after reviewing the requested change.

View example

Remove Documint templates explicitly retired in notes

Delete a Documint template only when a new Pipedrive note clearly identifies it for retirement.

View example

Review templates for each new organization

List Documint templates when a new Pipedrive organization is created and identify relevant document options.

View example

Check the onboarding template for a new organization

Retrieve the selected Documint onboarding template and summarize its current details for a new Pipedrive organization.

Supported Triggers and Actions

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

Pipedrive triggers

Documint actions

Recurring trigger

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

TriggerScheduled

Delete Template

Tool to permanently delete a single template by its id. use when you need to remove an outdated or unused template; ensure the template id is correct before calling.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Template

Tool to retrieve a single template by its id. use when you need to fetch details of a specific template before generating documents.

ActionInstant

New Deal Received Trigger

Triggered when a new deal is created in Pipedrive

TriggerInstant

List Documents

Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.

ActionInstant

New Note Received Trigger

Triggered when a new note is created in Pipedrive

TriggerInstant

List Templates

Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.

ActionInstant

New Organization Received Trigger

Triggered when a new organization is created in Pipedrive

TriggerInstant

Update Template

Tool to update a single template by its id. use when you need to modify an existing template's settings or layout after fetching its current details.

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.