Download the PHP package nextdeveloper/ipaas without Composer
On this page you can find all versions of the php package nextdeveloper/ipaas. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nextdeveloper/ipaas
More information about nextdeveloper/ipaas
Files in nextdeveloper/ipaas
Package ipaas
Short Description NextDeveloper abstraction library for IPaaS (Integration Platform as a Service) services
License MIT
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 ipaas
NextDeveloper IPaaS Library
This library provides an enterprise-level abstraction layer for Integration Platform as a Service (iPaaS) providers. It gives your application a unified interface to manage, synchronise, and monitor workflow automations across multiple third-party automation platforms through a single, consistent API.
The design goal is simplicity at the integration boundary — you register a provider once and the library handles authentication, data normalisation, periodic sync, and execution tracking for all supported platforms.
Supported Platforms
| Platform | Type | Workflows | Executions | Activate / Deactivate |
|---|---|---|---|---|
| n8n | self-hosted / cloud | ✅ | ✅ | ✅ |
| Make.com | cloud | ✅ (scenarios) | ✅ | ✅ |
| Zapier | cloud | ✅ (zaps) | ❌ (not in public API) | ❌ (not in public API) |
Core Concepts
Providers
A Provider record represents a registered automation platform account. Each provider stores the credentials and base URL needed to reach the platform's API:
| Provider field | n8n | Make.com | Zapier |
|---|---|---|---|
region / base_url |
Instance URL | Regional API base | https://api.zapier.com/v2 |
external_account_id |
N8N API key | Make.com team ID | — |
api_token |
— | Make.com API token | Zapier personal token |
provider_type |
n8n or n8n-cloud |
make |
zapier |
Workflows
A Workflow is the library's unified representation of an automation (n8n workflow, Make scenario, Zapier zap). Workflows are fetched from the platform and stored locally so they can be queried, filtered, and associated with executions without hitting the upstream API on every request.
Workflow Executions
A WorkflowExecution records the outcome of a single workflow run. The library normalises each platform's status vocabulary into a common set: success, error, running, waiting, canceled.
Statistics
The library automatically maintains daily aggregate tables (ipaas_workflow_daily_stats, ipaas_execution_daily_stats) and per-account summaries (ipaas_account_stats) so dashboards can be served without expensive live queries.
Platform Integration Features
- [x] Unified
WapInterface— all platforms implement the same contract - [x]
testConnection()— verify credentials before storing a provider - [x]
listWorkflows()/getWorkflow()— browse automation definitions - [x]
activateWorkflow()/deactivateWorkflow()— control workflow state - [x]
listExecutions()/getExecution()/deleteExecution()— manage execution history - [x]
syncWorkflows()— pull all workflows from the platform and upsert locally - [x]
syncExecutions()— pull execution history within a configurable time window - [ ] Webhook-triggered sync (currently polling only)
- [ ] Workflow creation via API (create automations from within your app)
- [ ] Cross-platform workflow migration
Sync Jobs and Artisan Commands
The library ships with queue jobs and Artisan commands for each platform so syncs can be scheduled, dispatched manually, or run inline for debugging.
Commands
Scheduler
Add the following to your app/Console/Kernel.php to keep data fresh:
Jobs are dispatched to the ipaas-sync queue by default and support automatic retries with backoff.
Authorization
The library uses role-based access control via the IntegrationPlatformUser role. This role restricts users to their own account's providers, workflows, and executions through Eloquent global scopes, so no data leaks across account boundaries.
Perspectives (Read-Only Views)
The library exposes several database views for efficient reporting without application-level joins:
| Perspective | Description |
|---|---|
AccountProviderOverviews |
Per-account summary of registered providers and their health |
PlatformHealthPerspective |
Cross-provider health snapshot for operations dashboards |
WorkflowExecutionsPerspective |
Enriched execution list with workflow and provider context |
Adding a New Platform
- Create an integration class in
src/Integrations/<Platform>/that extendsAbstractWapIntegrationand implementsWapInterface. - Create a corresponding interface in the same directory.
- Add the provider type to
WapIntegrationFactory::make(). - Add sync jobs under
src/Jobs/<Platform>/following the existing pattern. - Add Artisan commands under
src/Console/Commands/.
Commercial Support
Please let us know if you need any commercial support. We will be happy to help you integrate this library into your project.
Want to Contribute?
You are very welcome to contribute. Please send us an email so we can get in touch and discuss the details:
Our Libraries
This library is part of the NextDeveloper / PlusClouds open-source ecosystem. Browse all available libraries and find the right building blocks for your next project:
https://plusclouds.com/us/solutions/libraries
Join the Community
We believe great software is built together. The PlusClouds developer community is a place where engineers share ideas, ask questions, showcase what they have built, and help shape the direction of these libraries. Whether you are integrating a single package or building an entire platform on top of our stack, you are very welcome here.
Come and join us — we would love to see what you build:
