---
title: "Retrieve the evaluable fields of a trigger"
method: GET
path: "/companies/{company}/automations/catalog/triggers/{trigger}/fields"
tags: ["Automations"]
---

# Retrieve the evaluable fields of a trigger

`GET /companies/{company}/automations/catalog/triggers/{trigger}/fields`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/automations/catalog/triggers/{trigger}/fields`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

List the fields you can write conditions against for one trigger: location in the event, type, label and accepted operators.
- A trigger outside your visible catalog returns 404, so it cannot be used to probe contracted modules.
- A visible trigger with no evaluable fields returns 422.

## Path parameters

- `company` string, uuid, required
- `trigger` string, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` AutomationTriggerFields, required: The fields of ONE trigger that an automation condition can evaluate, with the operators each field accepts. Served per trigger, not inside the catalogue: with around a hundred visible triggers and dozens of properties each, a single document would be hundreds of kilobytes to end up using the fields of one.
    - `object` 'automation_trigger_fields', required: Always `automation_trigger_fields`.
    - `trigger` string, required: Trigger these fields belong to, in `resource.action` form. It travels in the body as well as in the URL so a cached response stays interpretable on its own.
    - `fields` object[], required: Evaluable fields, in the order the payload contract declares them. This list is never empty: a trigger without a declared payload contract is rejected as such instead of degrading to an empty list.
      - `path` string, required: Path of the field relative to the `data.object` of the event. This is the value you put in the `field` of a condition.
      - `type` 'string' | 'integer' | 'number' | 'boolean' | 'datetime' | 'string_list', required: Type token of the field.
      - `type_label` string, required: Human-readable name of the type, already translated.
      - `operators` string[], required: Operators this field accepts — the row of the operator-by-type matrix that the write validation applies. Pick from here and your condition will not be rejected with a 422.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`). `company_inactive`: the company in the path is deactivated; reactivate it to operate.
- `404`: The requested resource does not exist or belongs to another company. `profile_not_found`: the company in the path does not exist, is not in the API key scope or belongs to the other environment (live or test).
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)