Factuarea APIDevelopers

Retrieve the evaluable fields of a trigger

List the fields you can write conditions against for a single trigger: where to read each one inside the triggering event, its type, the translated label of that type and the operators it accepts.

  • It is the companion of the catalog, split into its own operation because serving the fields of every trigger at once would weigh hundreds of kilobytes per call.
  • A trigger outside the catalog visible to your company returns 404 — whether the name does not exist, its module is not in your plan, or it is admin-only — so this endpoint cannot be used to probe what an account has contracted.
  • A visible trigger whose event type publishes no evaluable fields returns 422.
GET
/automations/catalog/triggers/{trigger}/fields
AuthorizationBearer <token>

In: header

Path Parameters

trigger*string

Headers

Factuarea-Version?string

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Formatdate
X-Active-Profile?string

Operate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json