RD Station CRMInstall

Summary

Lists custom field definitions from RD Station CRM (GET /crm/v2/custom_fields), with optional RDQL filters, sorting, and either single-page or fetch-all pagination.

Inputs

• filters — Repeatable conditions, each with Field (name, created_at, updated_at), Operator (eq, neq, match, gt, lt, gte, lte, in, nin) and Value. They are combined into one RDQL filter query string. Conditions with an empty value are skipped. For in/nin, separate values with commas.
• sortField — Sort by name, created_at or updated_at. 'Nenhum' (the default) sends no sort.
• sortDirection — asc or desc (default desc). Only applied when a sort field is chosen.
• fetchAll — If true, requests pages of 100 until there is no next link, up to a 1000-page safety cap. Default false.
• maxResults — Shown only when fetchAll is on. Caps the total records returned; 0 means no limit.
• pagination — Shown only when fetchAll is off. Contains pageNumber (default 1) and pageSize (default 20, max 100).

Output shape

One n8n item per custom field returned by the API (the response data array is split into items).

Without fetchAll, only the requested page is returned. Each input item triggers its own request. On error, the node throws, or with Continue On Fail it emits an item with json.error. The properties don't expose an entity filter, but a filter on entity may not be offered; the filter field list is limited to name and dates.

Examples

Example 1: Get every custom field whose name contains 'cpf', newest first

Filters: Field=Nome, Operator=Contém (match), Value=cpf; Sort by Data de Criação, desc; Buscar Todos os Registros = true

Example 2: Preview the first 50 custom fields alphabetically

Sort by Nome, asc; fetchAll off; Pagination pageNumber=1, pageSize=50

Links

• n8n community nodes installation guide