Connect Hubspot to Pipedrive

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

View example

Capture qualified HubSpot contacts as Pipedrive leads

Create a Pipedrive lead when a new HubSpot contact contains the buying signals your team considers qualified.

View example

Create Pipedrive people for sales-ready contacts

Add a person in Pipedrive when a new HubSpot contact is ready for direct relationship management.

View example

Create organizations for new company contacts

Add a Pipedrive organization when a new HubSpot contact introduces a credible company that is not yet in the CRM.

View example

Open deals for contacts requesting a demo

Create a Pipedrive deal when a new HubSpot contact includes a concrete demo or consultation request.

View example

Schedule outreach for high-intent contacts

Add a Pipedrive activity when a new HubSpot contact shows strong intent but still needs a personal first response.

View example

Preserve referral context on Pipedrive contacts

Add a note to the matching Pipedrive person or lead when a new HubSpot contact arrives through a meaningful referral.

View example

Add new decision makers to active deals

Add a newly created HubSpot contact as a participant when their company already has a relevant active deal in Pipedrive.

View example

Open Pipedrive deals at the qualified stage

Create a Pipedrive deal when a HubSpot opportunity reaches the stage your team treats as sales-qualified.

View example

Schedule the next step at proposal stage

Add a Pipedrive follow-up activity when a HubSpot deal enters the proposal stage.

Supported Triggers and Actions

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

Hubspot triggers

Pipedrive actions

Contact Created Trigger

TriggerInstant

Add a call log

Adds a new call log.

ActionInstant

Deal Stage UpdatedTrigger

TriggerInstant

Add a channel

New messaging channel added; registration limited to admins. utilizes getconversations endpoint for data retrieval. requires messengers integration oauth scope and a prepared messaging app extension manifest.

ActionInstant

Add a comment to a note

Adds a new comment to a note.

ActionInstant

Add a deal

Add a new deal to pipedrive with any custom fields, which vary by account and are identified by long hash keys. check dealfields for existing custom fields. for details, visit the tutorial on adding a deal.

ActionInstant

Add a follower to a deal

Adds a follower to a deal.

ActionInstant

Add a follower to an organization

Adds a follower to an organization.

ActionInstant

Add a follower to a person

Adds a follower to a person.

ActionInstant

Add a follower to a product

Adds a follower to a product.

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.