Connector: applications, APIs, webhooks, scripts

We are looking for an experienced Laravel developer to develop a custom platform.

The application will be a central admin/control panel that will function as a bridge between different applications, APIs, webhooks, scripts and modules. The goal is to create a stable and scalable system through which we can manage workspaces/projects, connectors, modules, webhooks, mappings, execution jobs, queues, logs, automations and permissions.

We are not asking for a complete Zapier/Make-like system with an advanced visual builder, marketplace and hundreds of ready-made integrations in the first version. However, we want to deliver a fully functional first version of the application, with a clean and scalable architecture, so that in subsequent phases features such as third-party modules, public SDK, marketplace and more complex automation flows can be added. The implementation will be divided into
clear milestones, so that each stage can be reviewed and approved before
moving on to the next.

The application should allow an admin to create and manage
workspaces, connect external applications via connectors, store API credentials
securely, accept data via webhooks, view incoming payloads, map fields, create execution jobs, monitor queues and failed jobs, retry failed executions, view logs/audit trails, and manage users,
roles, and permissions.

The basic technology we recommend is Laravel, with MySQL or PostgreSQL, Laravel Queues,
REST API endpoints, webhook endpoints, role/permission system, and secure storage of
credentials/secrets. The developer can propose a different or improved architecture,
as long as he clearly explains the reasons and advantages of his proposal.

We want the application to be designed with a modular and extensible logic. In the initial MVP, we do not ask for a public SDK, marketplace or a complete module installation system from third-party developers. However, the architecture must be such that in the future a third-party developer can create his own module following specific specifications.

For this reason, modules should not be hardcoded in a rough way, but there should be a basic Module Contract logic, where each module can declare a name, type, actions, input/output schema, execution method, permissions/scopes, health check, status and logs. Collaboration will be done per milestone.

Each milestone should be delivered functional, with migrations, basic UI, demo data where necessary, documentation and a short video or walkthrough showing what has been implemented.

After each milestone, we will check and if any problem is detected, it should be fixed before proceeding to the next stage. Indicatively, the MVP will include core setup, authentication, admin panel, workspaces, users/roles/permissions, connector registry, module registry, webhook intake, payload logs, field mappings, execution jobs, queue/retry system, basic automation flows, audit trail and security hardening.

Not included in the initial MVP are features such as a full Zapier/Make-style visual builder, marketplace, billing/subscriptions, mobile app, AI automation, SSO, public SDK, production-ready integrations for dozens of platforms or a full SaaS commercial version.

These can be considered in a later phase. The developer who will undertake the project must have experience in Laravel, APIs, webhooks, queues/jobs, database design, authentication, roles/permissions and secure credential management. Experience in integration platforms, admin panels, automation systems or custom business tools will be highly appreciated.