Custom adapters

Custom adapters are meant to bring in CI/CD systems that Prodgator has no built-in adapter for, by mapping their webhook payloads to Prodgator's run format.

Current statusCopy Anchor Link

Custom adapters cannot receive events yet. Today you can:

• Create an adapter on the Adapters & Rules page, Custom Adapters tab (editor and above), with a name, a URL-safe slug and a verification method.
• Edit its field mapping and status map as JSON, and turn it on or off.
• Click Test, paste a sample payload, and see the fields the field mapping extracts. Nothing is stored. The test applies the field mapping only, not the status map.

The page does not show a webhook URL for an adapter. Each adapter card says "Receiving events from custom adapters is not available yet." Prodgator does not accept deliveries for custom adapters yet: there is no per-adapter signing secret Prodgator can check, and the endpoint cannot yet tell which organization an adapter belongs to.

Field mappingCopy Anchor Link

The field mapping maps Prodgator run fields to dot-separated paths in the provider's payload:

{
  "providerRunId": "pipeline.id",
  "workflowName": "workflow.name",
  "repository": "project.name",
  "repositoryFullName": "project.slug",
  "branch": "pipeline.vcs.branch",
  "commitSha": "pipeline.vcs.revision",
  "authorUsername": "pipeline.trigger.actor.login",
  "htmlUrl": "workflow.url",
  "startedAt": "workflow.created_at",
  "completedAt": "workflow.stopped_at"
}

Status mapCopy Anchor Link

The status map translates the provider's status values to Prodgator statuses (queued, in_progress, waiting, action_required, success, failure, timed_out, cancelled, skipped):

{
  "running": "in_progress",
  "success": "success",
  "failed": "failure",
  "canceled": "cancelled",
  "on_hold": "action_required",
  "queued": "queued"
}

Verification methodsCopy Anchor Link

An adapter records one of these verification methods: HMAC-SHA256 signature, bearer token, IP allowlist, or none.