Skip to content

Blog

News on integrations, data quality and automation.

Illustration: a Pipedrive app moving from sandbox through review to a Marketplace listing

The Pipedrive Marketplace: how apps get there and what building one costs

How apps get into the Pipedrive Marketplace: private or public, the review, the rules that drive the budget, and where the cost of an app comes from.
Illustration: four numbered routes from Pipedrive deals, from built-in integration and Marketplace app to Zapier, Make, n8n and your own build

Pipedrive integrations: four routes and when to use each

Pipedrive integrations explained: built-in connections, Marketplace apps, Zapier, Make and n8n, or your own API build, and which route fits which job.
Illustration: two invoices side by side, each with a seat counter for the CRM and a contact counter on the marketing module, HubSpot with an extra one-time onboarding fee

Pipedrive vs HubSpot: an honest comparison from a Pipedrive shop

Pipedrive vs HubSpot in 2026: real per-seat prices, HubSpot's required onboarding fees, contact-based billing, API limits, and where each one is the better choice.
Illustration: an app connected to several Xero organizations through one OAuth 2.0 login, with the five developer pricing tiers shown as steps

Xero API for developers: OAuth 2.0, tenants, limits and what the docs skip

The Xero API beyond the getting-started guide: OAuth 2.0 tokens, tenants, granular scopes, rate limits, webhooks and 2026 developer pricing.
Illustration: daily API token budget, the token cost of a record, a list and a search, then a 429

The Pipedrive API: what you can build, and what it costs you

What a Pipedrive API integration can actually do, which OAuth scopes to ask for, and how the daily token budget decides whether it survives.
Illustration: a Pipedrive deal triggering a chain of automation steps that ends at a boundary, with a webhook leading on to outside systems

Pipedrive automation: what the built-in workflows do, and where they stop

Pipedrive automation explained: triggers, conditions, actions and limits per plan, how sequences and Campaigns differ, and where workflows stop.