Attio icon

Attio

Interact with Attio API

Overview

This node interacts with the Attio API to create a new status for a specific attribute on either an object or a list within Attio. It is useful when you want to programmatically add or update status attributes that track progress or state, such as "In Progress", "Completed", or custom statuses with additional metadata.

Typical use cases include:

  • Automating workflow states in CRM or project management systems.
  • Adding custom status tracking to lists or objects to reflect business processes.
  • Enabling celebration effects or timing features associated with status changes.

For example, you might use this node to add a status "In Progress" to a task list attribute, enabling celebration animations and setting a target time duration for how long an item should remain in that status.

Properties

Name Meaning
Target Specifies whether the status attribute belongs to a "Lists" or "Objects". Note: company and person objects do not support status attributes currently.
Identifier A UUID or slug identifying the specific object or list to which the status attribute will be added.
Attribute A UUID or slug identifying the attribute under which the status will be created.
Data JSON object containing the status details. Typical fields include:
- title: The name of the status (e.g., "In Progress").
- celebration_enabled: Boolean to enable celebration effects.
- target_time_in_status: ISO 8601 duration string specifying target time in this status (e.g., "P0Y0M1DT0H0M0S" for 1 day).

Output

The node outputs the JSON response from the Attio API after creating the status attribute. This typically includes the newly created status object's details such as its ID, title, configuration flags, timestamps, and any other metadata returned by the API.

If the API supports binary data in responses, it would be summarized here; however, this operation deals with JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends HTTP requests to the Attio API endpoint https://api.attio.com.
  • Proper permissions on the API key are necessary to create or modify attributes and statuses.

Troubleshooting

  • Common issues:

    • Using unsupported targets like company or person objects for status attributes will fail because these do not support status attributes.
    • Invalid UUIDs or slugs for identifiers or attributes will cause API errors.
    • Malformed JSON in the Data property can cause parsing errors before sending the request.
  • Error messages:

    • Operation not found: Indicates the selected operation does not exist for the resource; ensure correct Resource and Operation selections.
    • Operation configuration not found: Internal misconfiguration; verify node version and update if needed.
    • API authentication errors: Check that the API key credential is valid and has required scopes.
    • Validation errors from API: Usually due to invalid or missing fields in the Data JSON; validate JSON structure and required fields.

To resolve errors, verify all input parameters, ensure the API key is valid, and confirm the target supports status attributes.

Links and References

Discussion