Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node integrates with the Attio API to create a new list within the Attio workspace. It allows users to define detailed list properties such as the list name, API slug, parent object type, and access permissions for the workspace and its members.

Common scenarios where this node is beneficial include:

  • Automating the creation of categorized contact or lead lists in Attio based on dynamic data.
  • Organizing workspace data by programmatically generating lists with specific access controls.
  • Integrating Attio list management into broader workflows that require structured segmentation of people or entities.

For example, a sales automation workflow could use this node to create a "Enterprise Sales" list with read-and-write access for certain team members, enabling targeted outreach campaigns.

Properties

Name Meaning
Data JSON object defining the list details. This includes:
- name: The display name of the list (e.g., "Enterprise Sales").
- api_slug: A unique identifier slug for the list (e.g., "enterprise_sales").
- parent_object: The type of object the list relates to (e.g., "people").
- workspace_access: Access level for the entire workspace (e.g., "read-and-write").
- workspace_member_access: Array specifying individual workspace members' access levels, each with workspace_member_id and level (e.g., "read-and-write").

The property expects a JSON string input which will be parsed and sent as the request body to the Attio API.

Output

The node outputs the JSON response from the Attio API after creating the list. This typically contains the newly created list's details, including its ID, name, slug, access settings, and metadata.

The output structure is:

{
  "json": {
    // Newly created list object returned by Attio API
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends HTTP requests to https://api.attio.com/v2/lists endpoint.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Invalid JSON in Data Property: If the JSON string provided in the "Data" property is malformed, the node will fail parsing it. Ensure the JSON is valid and properly escaped.
  • Authentication Errors: Missing or invalid API key credentials will cause authorization failures. Verify that the API key is correctly set up in n8n credentials.
  • Permission Issues: If the specified workspace or member access levels are incorrect or the user lacks permission, the API may reject the request.
  • Operation Not Found Error: This error occurs if the operation or resource parameters are misconfigured or unsupported. Confirm that "Lists" resource and "Create List" operation are selected.
  • Network or API Errors: Temporary network issues or API downtime can cause request failures. Retrying later or checking API status may help.

Links and References

Discussion