Actions57
- Objects Actions
- Attributes Actions
- List Attributes
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- POST target/identifier/attributes/attribute/statuses
- Create Attribute
- GET target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Entries Actions
- Records Actions
- Lists Actions
- Meta Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
- Comments Actions
Overview
This node interacts with the Attio API to create a status attribute for a specified target (either a list or an object) identified by a UUID or slug. It allows users to define the status attribute's details such as title, celebration settings, and target time in status. This is useful for managing and updating status attributes dynamically within Attio, for example, tracking progress stages or status changes on lists or objects.
Use Case Examples
- Creating a status attribute on a list to track the progress of tasks with a title 'In Progress' and enabling celebration notifications.
- Updating the status attribute of an object to reflect a new state with specific timing and celebration settings.
Properties
| Name | Meaning |
|---|---|
| Target | Specifies whether the status attribute is applied to a list or an object. Note that company and person objects do not support status attributes currently. |
| Identifier | A UUID or slug that identifies the specific object or list to which the status attribute belongs. |
| Attribute | A UUID or slug that identifies the specific attribute to which the status will be assigned. |
| Data | A JSON object containing the details of the status attribute, such as title, celebration_enabled flag, and target time in status. |
Output
JSON
json- The JSON response from the Attio API representing the created or updated status attribute.
Dependencies
- Requires an API key credential for authenticating requests to the Attio API.
Troubleshooting
- Ensure the 'Target' property is correctly set to either 'lists' or 'objects' as company and person objects do not support status attributes, which may cause errors.
- Verify that the 'Identifier' and 'Attribute' fields contain valid UUIDs or slugs corresponding to existing entities in Attio to avoid not found errors.
- The 'Data' property must be valid JSON; malformed JSON will cause parsing errors.
- API authentication errors may occur if the API key credential is missing or invalid; ensure proper credential configuration.