Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node operation updates an existing list in the Attio system by sending a PATCH request to the Attio API. It allows users to modify properties of a specified list, such as its name, API slug, and access permissions for workspaces and workspace members.

Common scenarios where this node is beneficial include:

  • Renaming or rebranding a list.
  • Changing access levels for collaborators on a list.
  • Updating metadata or configuration related to a list without recreating it.

For example, a sales team might use this node to update the "Enterprise Sales" list's name or adjust which team members have read-and-write access.

Properties

Name Meaning
List A UUID or slug that uniquely identifies the list to update. This tells the node which list to patch.
Data JSON object containing the fields to update on the list. Typical fields include:
- name: The new name of the list.
- api_slug: A unique slug identifier.
- workspace_access: Access level for the workspace (e.g., "read-and-write").
- workspace_member_access: Array specifying individual workspace members' access levels, each with:
- workspace_member_id: UUID of the member.
- level: Access level for that member (e.g., "read-and-write").

Output

The node outputs the updated list object as returned by the Attio API in the json field. This JSON contains all current properties of the list after the update, reflecting any changes made.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends HTTP PATCH requests to the Attio API endpoint corresponding to the specified list.
  • Proper network connectivity to the Attio API service is necessary.

Troubleshooting

  • Invalid List Identifier: If the provided list UUID or slug does not exist, the API will return an error. Verify the list identifier is correct.
  • Malformed JSON in Data: The Data property must be valid JSON. Parsing errors will cause the node to fail. Use proper JSON formatting.
  • Insufficient Permissions: The API key used must have permission to update lists. Authorization errors indicate missing or insufficient credentials.
  • API Rate Limits: Frequent updates may hit rate limits imposed by the Attio API. Consider adding delays or retries if encountering rate limit errors.
  • Network Issues: Connectivity problems can cause request failures. Ensure stable internet connection and that the Attio API is reachable.

Links and References

Discussion