Vendaze workspaces can define custom fields to capture data that does not fit in the standard schema: tax IDs, lead sources, business segments, internal scores, and any other information relevant to the sales process.Documentation Index
Fetch the complete documentation index at: https://developers.vendaze.com/llms.txt
Use this file to discover all available pages before exploring further.
How they work
Custom fields are defined per workspace and associated with individual records. Each field has:- Label: human-readable name shown in the UI (e.g., “Lead Source”)
- Key: short identifier for programmatic use (e.g.,
lead_source) - Type: defines valid values and comparison rules
- Visibility: whether it appears on people, companies, and/or deals
Available types
| Type | Description | Example value |
|---|---|---|
text | Single line of text | "Acme Corp" |
long_text | Multi-line text | "Notes about the customer..." |
number | Numeric value | 42 |
date | ISO 8601 date | "2026-05-26" |
select | One option from a predefined list | "hot" |
multi_select | Multiple options | ["hot", "inbound"] |
cpf | Brazilian individual tax ID | "000.000.000-00" |
cnpj | Brazilian company tax ID | "00.000.000/0001-00" |
link | URL | "https://linkedin.com/in/ana" |
address | Physical address | "123 Main St" |
List workspace fields
Read values on a record
When retrieving a record by ID, custom field values are returned in thecustom_fields object:
Filter by custom field
| Type | Comparison |
|---|---|
text, long_text, link, address | Case-insensitive partial match |
cpf, cnpj | Exact |
select | Exact |
multi_select | Contains the value |
number | Exact |
date | Exact |