Skip to main content
Just like select attributes, status attributes are a constrained input type, where the user must pick from a predefined list. They are used in the Attio UI to define the different columns on a kanban board, but they can also be used with objects directly. There’s only one predefined status attribute, available on the deal object as stage. The possible values of a status attribute are known as “statuses”, and there are separate APIs for managing them. All status attributes are single-select.

Reading values

Status values have a status property, which is an object describing which status was used:

Writing values

You can find a list of available statuses using the list statuses API. To write status values, pass the title of the status as a string. You can also pass an object with a status property which references either the status_id or the title of the status. If you attempt to write a value where the ID or title cannot be found, you will receive an error rather than create a new status.

Filtering

Status attributes can be filtered by equality, using either the implicit syntax or the explicit one, with either the title or status ID:
You can also filter for multiple possible matching values using the $or syntax:
Status attributes can also be filtered based on when they were modified, using the active_from property. This allows automations based on when the attribute was changed. This filter supports the $lt, $lte, $gt, $gte operators: