iiRecord
Agentic AI Atlas · External Webhook Trigger
definition:trigger-webhooka5c.ai
II.
Definition JSON

definition:trigger-webhook

Structured · live

External Webhook Trigger json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · domain/cicd/cicd-concepts.yamlCluster · domain
Record JSON
{
  "id": "definition:trigger-webhook",
  "_kind": "Definition",
  "_file": "domain/cicd/cicd-concepts.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "External Webhook Trigger",
    "authoredAt": "2026-05-10T00:00:00Z",
    "termId": "term:cicd",
    "text": "A CI trigger that fires when an external service sends an HTTP\nwebhook to the CI system. Used for integrating CI with third-party\ntools: container registry scan completion, infrastructure drift\ndetection, monitoring alert escalation, or external test harness\nresults. Webhook triggers require authentication (shared secrets,\nHMAC signatures) to prevent unauthorised pipeline execution.\nJenkins and GitLab CI have native webhook trigger support; GitHub\nActions uses repository_dispatch as its webhook-equivalent.\n",
    "status": "canonical"
  },
  "outgoingEdges": [
    {
      "from": "definition:trigger-webhook",
      "to": "term:cicd",
      "kind": "defines"
    },
    {
      "from": "definition:trigger-webhook",
      "to": "domain:devops",
      "kind": "applies_to"
    },
    {
      "from": "definition:trigger-webhook",
      "to": "tool:jenkins",
      "kind": "supports"
    },
    {
      "from": "definition:trigger-webhook",
      "to": "tool:gitlab-ci",
      "kind": "supports"
    },
    {
      "from": "definition:trigger-webhook",
      "to": "topic:ci-triggers",
      "kind": "supports"
    }
  ],
  "incomingEdges": []
}