Triggers

List trigger types with GET /api/v3/triggers_types. Each has a config schema, such as the repository to watch.

curl -X POST https://www.prompt-tm.com/api/v3/trigger_instances \
  -H "x-api-key: $PROMPT_TM_KEY" -H "content-type: application/json" \
  -d '{ "slug": "GITHUB_ISSUE_EVENT", "user_id": "alice",
        "trigger_config": { "owner": "acme", "repo": "web" } }'

When the type registers upstream (registers_upstream: true), we create the webhook in the user's account with a fresh secret. GitHub needs the admin:repo_hook scope or a token with webhook access for this.

Otherwise the answer's ingest_url is the address to paste into the app.

Events are verified, stored and sent to your project webhook as trigger.message. Switch an instance off with PATCH /api/v3/trigger_instances/{id} { "status": "disable" }. DELETE removes it and the upstream webhook.

Incoming webhook

The webhook toolkit has one trigger, WEBHOOK_INCOMING_REQUEST, that needs no account. Create it and POST anything to its ingest_url.