Custom Fields
Custom fields let admins define additional data points for users in the organization. Each user fills in their own values, and workflows can read those values using the Custom Fields node.
Use custom fields when your workflows need per-user context - a user's department, their external account ID, their region, their preferred language, or any other data that varies by person and needs to be available in automations.
Defining Custom Fields (Admin)
Navigate to Organization Settings > Custom Fields to manage field definitions.
Each field has:
| Property | Description |
|---|---|
| Name | The field identifier, used to reference it in the Custom Fields workflow node |
| Type | The data type: string, number, boolean, array, or object |
| Description | Optional explanation shown to users when they fill in their value |
Once created, the field appears in every user's personal settings for them to fill in. Deleting a field removes all stored user values.
Filling in Values (Users)
Users set their own custom field values under User Settings > Custom Fields. Each field defined by the admin appears with an input appropriate for its type.
Values are saved per user and visible only to the user and to workflows running on their behalf.
Using Custom Fields in Workflows
The Custom Fields node in the workflow builder reads custom field values. It supports two operations:
| Operation | Description |
|---|---|
| List field values | Returns all user values for a specific custom field across the organization |
| Get user field value | Returns the value of a specific field for a specific user (by email) |
The returned value becomes a workflow variable available to subsequent nodes.
Example use: A workflow that sends a Slack message to the right channel reads the user's department custom field and routes accordingly. No hardcoding - the workflow adapts to whoever runs it.