Download the PHP package php-n8n/client without Composer
On this page you can find all versions of the php package php-n8n/client. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download php-n8n/client
More information about php-n8n/client
Files in php-n8n/client
Package client
Short Description A lightweight, strongly typed PHP client for triggering n8n webhooks and tracking workflow executions.
License MIT
Homepage https://php-n8n.com
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package client
PHP n8n Client
A PSR-compliant PHP client for triggering and tracking n8n webhook executions. php-n8n/client is framework agnostic, immutable by design, and built on PSR-7, PSR-17, and PSR-18.
Full documentation: https://php-n8n.com
The package focuses on webhook execution, execution tracking, and transport abstractions. It intentionally does not attempt to become a full n8n SDK.
Installation
This package depends on PSR interfaces. Install the PSR-18 HTTP client and PSR-17 factories that match your application stack.
Minimal Example
Webhook URLs must be valid absolute http or https URLs with a host.
Execution Tracking
Execution tracking uses the n8n API and requires an API key.
Webhook responses can also expose an execution reference when n8n returns one:
Why This Package Exists
This package exists to provide a lightweight, composable, and standards-oriented way to interact with n8n webhooks from PHP applications.
The ecosystem already contains several wrappers and framework-specific integrations, but many of them are tightly coupled to specific frameworks, HTTP clients, or large abstractions.
php-n8n/client focuses on PSR compliance, framework agnostic architecture, immutable APIs, minimal dependencies, explicit behavior, composability, and predictable integrations.
The goal is to provide a stable foundation that can be integrated into any PHP application or framework.
Design Principles
- PSR-first architecture
- Framework agnostic design
- Immutable value objects
- Explicit APIs over magic behavior
- Composable integrations
- Narrow responsibilities
- Stable public APIs
- Semantic versioning
- Minimal dependencies
The core package intentionally remains small and focused.
Ecosystem
The php-n8n ecosystem is designed as a collection of composable packages.
The core client remains intentionally minimal and framework agnostic. Additional integrations and higher-level tooling are distributed as separate packages.
Planned ecosystem direction:
This structure allows the ecosystem to grow without introducing unnecessary complexity into the core package.
Contributing
Contributions, ideas, bug reports, and improvements are welcome.
If you discover a bug, have a feature suggestion, or want to improve the project, please open an issue before submitting large changes. This helps discuss the direction and avoid duplicated work.
When contributing:
- Follow the existing coding standards
- Include tests when applicable
- Keep changes focused and minimal
- Maintain PSR compliance and framework agnostic design
For bug reports, please include the PHP version, package version, reproduction steps, expected behavior, and actual behavior.
For feature requests, please explain the problem being solved, the proposed API or design, and potential tradeoffs or alternatives.
Run the project checks before submitting changes:
Versioning Policy
This package follows Semantic Versioning.
The first public tag is expected to be v1.0.0, marking the client API as stable from the initial release.
Breaking changes will only be introduced in future major releases.
License
The MIT License. See LICENSE.
All versions of client with dependencies
psr/http-client Version ^1.0
psr/http-factory Version ^1.0
psr/http-message Version ^1.0 || ^2.0