Pipedrive Laravel Laravel Package

Product Decisions This Supports

• Build vs. buy for CRM connectivity: This package is a Laravel-side accelerator for integrating with Pipedrive. For teams already on Laravel, it can reduce custom integration work for sales-ops workflows such as contact/deal sync and token-based API access.
• Roadmap risk and timing: The 0.2.0 release is a pre-1.0 maintenance/breaking-change release, not a feature release. It renames Token::apiDomain() to Token::baseUrl() and changes the withToken(...) signature via karim-tao/pipedrive-client ^0.2. PMs should treat CRM integration work that depends on this package as technically viable but not API-stable.
• Architecture and vendor coupling: Because the package is still 0.x and surfaces breaking changes through its public API, product and engineering should avoid leaking package-specific types deep into domain code. Wrapping it behind an internal adapter is a product-risk decision as much as an engineering one.
• Use cases: Appropriate for internal sales tooling, lightweight Pipedrive synchronization, sandbox/custom base URL configurations, and teams that can absorb periodic dependency upgrades. Not appropriate as a foundation for a customer-facing SLA-critical integration without additional hardening.

When to Consider This Package

Consider it when:

• You have a Laravel/PHP application and need a Pipedrive integration faster than building directly against the API.
• Your team accepts pre-1.0 churn and can budget for dependency upgrades.
• You need token handling with configurable base URL support, including non-default or sandbox-style environments.
• The integration is internal, tactical, or can be isolated behind an application-owned interface.

Look elsewhere or defer when:

• You require a stable 1.0+ API contract, long-term support commitments, or vendor-backed SLAs.
• The roadmap includes complex, high-volume, or business-critical two-way CRM synchronization.
• Your team cannot absorb breaking changes such as renamed token methods or changed method signatures.
• You need an officially supported Pipedrive SDK rather than a community Laravel wrapper.
• You are not on Laravel/PHP or do not want package-level abstraction over the underlying Pipedrive client.

How to Pitch It (Stakeholders)

For executives: This package can shorten the path to a Pipedrive integration in our Laravel stack, but it is still pre-1.0 and just introduced breaking API changes. Treat it as a tactical accelerator, not a strategic platform dependency. Approve it only with an explicit maintenance budget and an internal abstraction layer so future upgrades do not become product-level risks.

For engineering: Upgrade the dependency constraint to karim-tao/pipedrive-client ^0.2, replace Token::apiDomain() with Token::baseUrl(), and audit every withToken(...) call for the aligned signature: withToken($accessToken, $expiresAt, $refreshToken = null, $baseUrl = null). Add or update tests around token construction and base URL handling. Keep the package behind an application-owned adapter so the next 0.x breaking change is contained.