Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node operation updates the status of a specific attribute on either an object or a list within the Attio platform. It is useful when you want to modify metadata related to attributes, such as changing the title, enabling celebrations, setting target times, or archiving statuses.

Typical use cases include:

  • Updating the progress status of a task or item tracked in a list.
  • Modifying attribute statuses dynamically based on workflow conditions.
  • Archiving or reactivating certain statuses for organizational purposes.

For example, you might update a "Status" attribute on a list entry from "In Progress" to "Completed," enabling celebration animations and adjusting target time settings accordingly.

Properties

Name Meaning
Target Specifies whether the attribute belongs to an "Objects" or "Lists". Note that company and person objects do not support status attributes currently. Options: lists, objects.
Identifier A UUID or slug identifying the specific object or list that contains the status attribute to be updated.
Attribute A UUID or slug identifying the particular attribute whose status is being updated.
Status A UUID or status title identifying the exact status to update on the attribute.
Data JSON object containing the fields to update for the status. Typical fields include:
• title (string): The new title of the status.
• celebration_enabled (boolean): Whether celebration effects are enabled.
• target_time_in_status (string): ISO 8601 duration format specifying target time.
• is_archived (boolean): Whether the status is archived.

Output

The node outputs a JSON object representing the updated status attribute as returned by the Attio API. This includes all details of the status after the patch operation, reflecting changes made via the input data.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends authenticated HTTP PATCH requests to the Attio API endpoint corresponding to the resource path /v2/{target}/{identifier}/attributes/{attribute}/statuses/{status}.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Using unsupported targets like company or person objects for status attributes will fail because these do not support status attributes.
    • Providing invalid UUIDs or slugs for identifiers, attributes, or statuses can cause errors.
    • Malformed JSON in the "Data" property will result in parsing errors.

  • Error messages:

    • "Operation configuration not found": Indicates the selected operation is not properly configured or recognized; verify the operation and resource selections.
    • "Operation ... not found for resource ...": Means the combination of resource and operation is invalid; ensure correct parameters.
    • API authentication errors: Check that the API key credential is valid and has appropriate permissions.
    • JSON parse errors on the "Data" field: Ensure the JSON is well-formed.

To resolve errors, verify all input parameters, confirm the API key validity, and ensure the JSON data is correctly formatted.

Links and References

Discussion