---
title: "Delete a trigger"
method: DELETE
path: "/v1/automations/triggers/{triggerEventId}"
tags: ["Automations"]
---

# Delete a trigger

`DELETE /v1/automations/triggers/{triggerEventId}`

Deletes a custom trigger. Refused with `409 TRIGGER_HAS_DEPENDENT_AUTOMATIONS` while automations still reference it (`details.referencingAutomations` lists each blocker). Idempotent — an already-gone trigger resolves with `deleted: false`.

## Path parameters

- `triggerEventId` string, required — Trigger id returned by `POST /v1/automations/triggers`. Custom triggers use `tri_…` ids; integration triggers use composite ids (e.g. `clerk:org_…:brand_…:user.created`, URL-encode the colons).

## Response `200`

Deleted (or already gone).

- TriggersDeleteResponse
  - `triggerEventId` string, required
  - `deleted` boolean, required

## Other responses

- `401` — The API key was missing, invalid, or revoked.
- `403` — The caller does not have the required `automations` permission.
- `409` — Automations still reference this trigger.
- `422` — Integration-provisioned trigger — cannot be deleted.
- `429` — The request hit the rolling rate limit window.
- `500` — Unexpected internal error.

---

[API](https://skmtc.net/brew/apis/brew-public-api-v1.md) · [All operations](https://skmtc.net/brew/apis/brew-public-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/brew/brew-public-api-v1/versions/db96cfedc6c5/schema)