Pipedrive
Pipeline-first CRM events from Pipedrive
Pipedrive is the sales CRM that takes the deal pipeline as its organising principle rather than a fancy contact list, and Tiny Command surfaces eight triggers that follow the deal's lifecycle: Deal Added, Deal Updated, Deal Won, Deal Lost, Activity Added (next-touch tracking), Person Added, Person Updated, and Organization Added. Seven actions cover the writes and reads: Create Deal, Update Deal, Create Person, Get Deal, Get Person, List Deals, List Persons. The connection authorizes via Pipedrive OAuth at the user or company level. Deal Won and Deal Lost are the high-value triggers, they fire the moment a deal's state changes, which is the natural hook for revenue recognition workflows (Won fans to billing, ops, and customer-success) and churn-investigation workflows (Lost fans to RevOps for analysis). Pipedrive's pipeline structure (deals belong to stages, stages belong to pipelines) comes through on every payload, so a workflow can branch by pipeline (e.g., Enterprise vs SMB) or by stage.
Workflows start when Pipedrive does.
8 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Fires when a deal is marked as lost in Pipedrive. Common use: log the lost-reason, add the contact to a churn-saver sequence, or trigger a manager review for large lost deals.
Fires whenever any field on a Pipedrive deal changes (stage, value, owner, expected close date, custom fields). Combine with a field filter to react only on specific transitions.
Fires when a deal is marked as won in Pipedrive. The Closed-Won hook: provision customer, generate contract, post to Slack, kick off onboarding.
Fires when a new organization is added in Pipedrive. Use for firmographic enrichment, parent-account matching, or to seed a customer record elsewhere.
Fires when a new person (contact) is added in Pipedrive. Use to enrich them via Clearbit/Apollo, sync to your ESP, or assign to the right rep.
Fires when a person (contact) is updated in Pipedrive. Use to re-enrich, re-sync to your ESP, or kick off a workflow when key custom fields change.
Do anything Pipedrive can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Deal | Creates a new deal in the Pipedrive sales pipeline with title, value, currency, person, organization, stage, expected close date, and owner. The entry point for converting qualified leads into pipeline. |
| Create Person | Creates a new person (contact) in Pipedrive with name, email, phone, organization, owner, and any custom fields. Used to push inbound leads into the CRM. |
| Get Deal | Retrieves a Pipedrive deal by ID with title, value, stage, person, organization, owner, and custom fields. The standard read after a trigger fires with an ID. |
| Get Person | Returns a Pipedrive person by ID with their emails, phones, organization, owner, and custom fields. Used to enrich trigger payloads or render contact UI. |
| List Deals | Lists deals from Pipedrive with filters for owner, stage, status (open/won/lost), and update time. Used for pipeline reports, forecasting, and warehouse exports. |
| List Persons | Lists persons (contacts) from Pipedrive with filters for owner and update time. Used for CRM sync into your ESP or for cohort exports. |
| Update Deal | Updates an existing Pipedrive deal: title, value, stage, status, expected close date, owner, or custom fields. Only the fields you pass are changed. |
Pre-built Pipedrive workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Pipedrive once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Pipedrive field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Pipedrive integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Pipedrive to Tiny Command?
What Pipedrive triggers does Tiny Command support?
What Pipedrive actions can I run from a workflow?
Is the Pipedrive integration real-time?
Do I need to write code to use Pipedrive with Tiny Command?
How much does the Pipedrive integration cost?
More crm & sales apps people connect.
Same category as Pipedrive, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Pipedrive.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
