- How do I install rossjcooper/laravel-hubspot in a Laravel application?
- Install it with Composer using composer require rossjcooper/laravel-hubspot, then publish any package configuration and add your HubSpot credentials through environment variables. Because v6 is a major release built on the newer official HubSpot PHP SDK, check the PHP and Laravel constraints in composer.json and pin the version you intend to deploy. Run a sandbox smoke test before rolling it out to production.
- Which Laravel and PHP versions are supported by laravel-hubspot v6?
- The exact Laravel and PHP constraints are defined in the package's composer.json and may differ from v5 because v6 aligns with the newer official HubSpot PHP SDK. Do not assume your existing v5 constraints will satisfy v6; verify them in CI before starting the upgrade. Also check Guzzle and HTTP client constraints if your application pins them directly.
- Is laravel-hubspot v6 a drop-in replacement for v5?
- No. The package is explicitly non-backward-compatible with prior versions because v6 changes the underlying HubSpot client abstraction. Applications that only use the package facade or helpers may see a limited surface change, but any code that reaches into the old HubSpot SDK should be treated as breaking. Plan a usage audit, a migration branch, and regression testing against a HubSpot sandbox.
- How do I configure HubSpot authentication such as private app tokens or OAuth?
- Configuration is handled through the package configuration and HubSpot client credentials, so store private app tokens in environment variables and never commit them. For OAuth, confirm how the newer HubSpot PHP SDK expects access tokens and refresh tokens to be persisted and refreshed in your application. Audit any custom token handling during the v5 to v6 upgrade because authentication and exception behavior may change with the underlying SDK.
- Can laravel-hubspot create, update, and delete HubSpot CRM contacts, companies, and deals?
- Yes. The package is designed as a Laravel wrapper around the HubSpot API for reading, creating, updating, and deleting CRM objects such as contacts, companies, deals, and other supported records through a fluent PHP interface. Use dependency injection or the package facade where appropriate, and keep HubSpot calls behind an internal service layer if you want easier testing. Validate critical CRM flows against a HubSpot sandbox after upgrading, especially if you use custom objects or associations.
- How can I test Laravel code that uses laravel-hubspot without calling the real HubSpot API?
- Isolate HubSpot calls behind your own adapter or service interface so unit tests can mock your application boundary instead of the package internals. For integration-level tests, use a HubSpot sandbox account and HTTP client mocking where the underlying SDK permits it. Confirm whether the package ships test fakes or helpers in its README and source before relying on them, since v6 changes the underlying client abstraction.
- What breaks when upgrading laravel-hubspot from v5 to v6?
- The biggest breakage risk is any code that uses the old HubSpot PHP SDK directly, because v6 aligns the wrapper with the newer official SDK. Areas to audit include authentication and token handling, exception classes, pagination, rate-limit behavior, batch APIs, custom objects, associations, and response shapes. Apps that only use the package facade may have less surface change, but they still need dependency constraint updates and regression tests against a HubSpot sandbox.
- How should I handle HubSpot API rate limits and retries in production with laravel-hubspot?
- Confirm how the newer HubSpot PHP SDK handles rate limits, retries, and backoff, then wrap critical syncs in queued jobs with sensible throughput controls. Multi-tenant or multi-portal applications need explicit token isolation and per-account throttling. Add observability around HubSpot request latency, error rates, and failed sync jobs so production issues are visible quickly.
- What is the maintenance outlook for laravel-hubspot and how long is v5 supported?
- Moving to the official HubSpot PHP client is a positive long-term maintenance signal, but the v5 to v6 transition creates near-term upgrade work. A fixed v5 support window is not defined in the provided context, so confirm the package release notes and issue tracker before planning. Assign an internal owner for the HubSpot integration and keep a rollback path to your pinned v5 version until v6 is proven in production.
- What are the alternatives to laravel-hubspot for integrating HubSpot with Laravel?
- You can use HubSpot's official PHP SDK directly, but you lose the Laravel conveniences such as facade or helper access, configuration publishing, and dependency-injection-friendly wrapper behavior. Another option is to build a thin internal adapter around the official SDK so your application code is insulated from future SDK changes. Evaluate any other Laravel HubSpot wrappers by checking their maintenance activity and which HubSpot SDK version they target.