- What is davispeixoto/laravel5-salesforce used for?
- It is a Laravel 5 wrapper around the legacy Force.com PHP Toolkit SOAP client for Salesforce. It registers a service provider, facade, and config file so you can call login, query, create, update, and describeSObjects through Laravel's container. It is a convenience wrapper rather than a full abstraction, so Salesforce SDK types leak into your application code. It is best suited to prototypes, read-only SOQL syncs, or small one-way writes.
- How do I install davispeixoto/laravel5-salesforce?
- Install it with Composer using davispeixoto/laravel5-salesforce, then register the service provider and facade manually if package auto-discovery is not present. Publish the config/salesforce.php file and supply your username, password, security token, WSDL path, and SOAP options. You must have the ext-soap PHP extension enabled on every app and worker host. Confirm outbound HTTPS access to login.salesforce.com and your *.my.salesforce.com domains.
- Does laravel5-salesforce support Laravel 10, Laravel 11, or PHP 8?
- No, it is a Laravel 5-era package built around a toolkit that predates PHP 8. The underlying Force.com PHP Toolkit uses deprecated constructs such as each(), create_function, and dynamic properties that can break on modern PHP runtimes. Do not adopt it on Laravel 9+, Laravel 10, Laravel 11, or PHP 8.2+ without verifying compatibility on your actual runtime. For greenfield projects, choose a REST-first package or a custom HTTP-client integration instead.
- Is this package REST or SOAP?
- It is SOAP-based, wrapping the Force.com PHP Toolkit SforcePartnerClient or SforceEnterpriseClient. Some descriptions mention REST, but the package does not provide a REST client, OAuth 2.0 flow, Bulk API 2.0, Composite API, Platform Events, or Change Data Capture. All calls go through the legacy SOAP Partner or Enterprise API surface.
- How does authentication work in laravel5-salesforce?
- Authentication uses the legacy username, password, and security token flow configured in config/salesforce.php. The wrapper calls the toolkit login method and then reuses that SOAP session for subsequent query, create, update, and delete calls. Enterprise security reviews often mandate OAuth 2.0 JWT bearer or Connected App client credentials, which this package does not model. Treat the built-in auth flow as suitable for sandbox testing, not as a production security pattern without additional controls.
- How do I query Salesforce records with laravel5-salesforce?
- You resolve the Salesforce class through the facade or container, call login, and then call query with a SOQL string. Results come back as raw toolkit objects or stdClass rows, so you must map them into your own DTOs or arrays. Keep result sizes within the practical SOAP limit of roughly 2,000 records per call. For larger volumes, plan a Bulk API 2.0 or REST-based approach outside this package.
- Can I create, update, and delete Salesforce records with this package?
- Yes, the wrapper exposes create, update, and delete methods that operate on toolkit SObject types. However, it does not provide idempotency, retry and backoff, an error taxonomy, queue integration, or a repository boundary. You will need to add external-ID-based upserts, retry policies, and DTO mapping yourself if you use it for writes. Anything beyond a simple demo requires an anti-corruption layer that your team owns.
- Is davispeixoto/laravel5-salesforce maintained and production-ready?
- It has around 47 stars, zero dependents, and is effectively a dormant single-maintainer package, so treat it as an unmaintained fork you inherit on day one. It ships no retry policy, no queue integration, no test seam, and no repository or DTO boundary. Production use requires an adapter interface, DTO mapping, idempotency via external IDs, error handling, and tests against a fake client. A stale bundled WSDL is also a common breakage because Salesforce retires API versions on a rolling basis.
- What are alternatives to laravel5-salesforce for Laravel Salesforce integration?
- For greenfield Laravel projects, prefer a REST-first option such as omniphx/forrest with OAuth 2.0, or a hand-rolled integration using Laravel's HTTP client against Salesforce REST APIs. If an iPaaS such as MuleSoft, Workato, or Segment already owns integrations, that may be a better fit than embedding Salesforce calls in the app. This package only makes sense when you are constrained to Laravel 5.x, PHP 7.x, SOAP, and a small read-only or one-way sync.
- How do I test a Salesforce integration built with laravel5-salesforce?
- The package has no test seam, so wrap its client behind your own adapter interface and inject a fake implementation in unit tests. Test your DTO mapping, error taxonomy, idempotency logic, and retry behavior without calling Salesforce. Keep a small number of sandbox integration tests for real SOAP connectivity and WSDL validation. This prevents your test suite from depending on Salesforce session limits, network availability, or API request allocations.