list_triggers
List Zendesk triggers with pagination, filtering by active status, category, title, or last update. Supports cursor-based pagination and field projection for customized data.
Instructions
Returns triggers as paginated skeletons (id, title, active, updated_at). Default limit: 100; pass cursor to walk pages, fields to project additional columns, filter for active/category/title-contains/updated-since, or verbose: true for full bodies. For "which triggers do X?" questions prefer find_triggers_by_tag / find_triggers_by_field / find_trigger_conflicts, they filter inside conditions and actions server-side and return only the matches with why_matched breadcrumbs. list_triggers without a filter on instances with thousands of triggers can be slow on first call (cold cache); subsequent calls slice from the cache and are near-instant.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items to return. Default 100. The full corpus is fetched and cached server-side; this only limits what the response carries. | |
| cursor | No | Opaque pagination token from a previous response. Slices the next page from the cached corpus. Stale cursors (older than the cache TTL) auto-reset to offset 0 and set cursor_invalidated: true. | |
| fields | No | Whitelist of field names. Overrides the default projection. Use to opt into extra fields (e.g. ["id","title","active","position","category_id","updated_at"]) without going fully verbose. | |
| filter | No | Structured filter applied to the cached corpus before slicing. Supported keys: active (bool), category_id (number/string), title_contains (string, case-insensitive), updated_since (ISO timestamp). Unsupported keys are ignored with a note in the response. | |
| refresh | No | Bypass cache and re-fetch from Zendesk | |
| verbose | No | Return full trigger objects instead of the thin projection | |
| instance | No | Override the sticky instance for this call |