[Dokploy] Base

[BILLKISHORE]

Description

Dokploy is an open-source, self-hostable PaaS for deploying applications, databases,
and Docker Compose stacks to your own servers. It is a common self-hosted alternative
to Heroku/Vercel and sits in the same category as Coolify, which SuperPlane already
integrates with.

Adding Dokploy would let workflows deploy applications as part of a canvas, and read
application state to gate later steps.

Link: https://dokploy.com
API docs: https://docs.dokploy.com/docs/api

Suggested Connection Method

API key

• Store the Dokploy instance base URL and an API token in the integration configuration.
• The API authenticates with an x-api-key header.
• Each instance exposes its own OpenAPI spec at /api/openapi.json, generated from
  Dokploy's tRPC routers, so endpoints are dot-named (for example
  POST /api/application.deploy).

Potential Components

• [Dokploy] List Applications: list applications available to the API token, used to
  populate resource pickers.
• [Dokploy] Deploy Application: trigger a deployment for a given application.
• [Dokploy] Control Application: start / stop / restart an application (follow-up).

Note on triggers

Dokploy has a generic webhook notification provider, but its payload is currently only:

{ "title": "...", "message": "...", "timestamp": "..." }

There is no event type, no resource identifier, and no signature or shared-secret
verification. Building a trigger on that would require parsing a human-readable message
string to work out which application changed and whether it succeeded, which would be
unreliable. So I'd suggest starting with actions only, matching the existing Coolify
integration, and adding a trigger if Dokploy's payload gains structured fields.

I use Dokploy in production and would like to implement this. Happy to adjust the
component list if you'd prefer a different starting scope.