Skip to content

Attio n8n community node

Published with provenancePublished with provenancenpm holds a signed attestation linking this release to the exact source commit and CI run that built it, so you can check what you install was built from the code it claims.What provenance means

@nativeship/n8n-nodes-attio

Use the Attio n8n node to search and update CRM records, manage lists, and work with tasks, notes, meetings, and activities

Install in n8n

Open Settings → Community Nodes → Install and paste this name.

@nativeship/n8n-nodes-attio

n8n Cloud installs only community nodes verified by n8n, so this one needs self-hosted n8n.

What you can do with Attio in n8n

85 operations across 16 resources

Activities

5 operations

  • Delete an activity — Delete an activity by ID or slug, along with its records. Archived activities can also be deleted.
  • List activities — Lists all system-defined and user-defined activities in your workspace. This endpoint is in alpha and may be subject to breaking changes as we gather feedback. Required scopes: `activity_configuration:read`. Supported token levels: `workspace`, `user`.
  • Get an activity — Gets a single activity by its `activity_id` or slug. This endpoint is in alpha and may be subject to breaking changes as we gather feedback. Required scopes: `activity_configuration:read`. Supported token levels: `workspace`, `user`.
  • Update an activity — Update an activity by ID or slug. Its schema extension cannot be changed after creation.
  • Create an activity — Create a custom activity. The workspace must have custom activities enabled; public apps can use the integration activities feature.

Activity records

7 operations

  • Delete an activity record — Delete an activity record by record_id.
  • Get an activity record — Get an activity record by record_id.
  • Update an activity record — Update an activity record by record_id and prepend supplied multi-select values. Use PUT to replace existing values.
  • Create an activity record — Create an activity record, such as a phone call.
  • List activity records — List activity records with optional filters and sorting.
  • Upsert an activity record — Create or update an activity record by matching the specified attribute. A match is updated; otherwise, a record is created. Use the create endpoint to avoid matching.
  • Update an activity record — Update an activity record by record_id. Supplied multi-select values replace existing values; use PATCH to add values without removing existing ones.

Attributes

10 operations

  • List attributes — List attributes for an object or list in the order shown in the UI.
  • Get an attribute — Gets information about a single attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read`. When `target` is `lists`, the required scopes are `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • List select options — Lists all select options for a particular attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read`. When `target` is `lists`, the required scopes are `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • List statuses — Lists all statuses for a particular status attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read`. When `target` is `lists`, the required scopes are `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • Update an attribute — Updates a single attribute on a given object or list. When `target` is `objects`, the required scopes are `object_configuration:read-write`. When `target` is `lists`, the required scopes are `list_configuration:read-write`. Supported token levels: `workspace`, `user`.
  • Update a select option — Updates a select option on an attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read-write`. When `target` is `lists`, the required scopes are `list_configuration:read-write`. Supported token levels: `workspace`, `user`.
  • Update a status — Update a status on an status attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read-write`. When `target` is `lists`, the required scopes are `list_configuration:read-write`. Supported token levels: `workspace`, `user`.
  • Create an attribute — Create an attribute on an object or list. For record-reference attributes, an optional relationship setting creates a matching reverse attribute.
  • Create a select option — Adds a select option to a select attribute on an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read-write`. When `target` is `lists`, the required scopes are `list_configuration:read-write`. Supported token levels: `workspace`, `user`.
  • Create a status — Add a new status to a status attribute on either an object or a list. When `target` is `objects`, the required scopes are `object_configuration:read-write`. When `target` is `lists`, the required scopes are `list_configuration:read-write`. Supported token levels: `workspace`, `user`.

Call recordings

4 operations

  • Delete call recording — Delete a call recording and all associated data.
  • List call recordings — List all call recordings for a meeting. This endpoint is in beta. We will aim to avoid breaking changes, but small updates may be made as we roll out to more users. Required scopes: `meeting:read`, `call_recording:read`. Supported token levels: `workspace`, `user`.
  • Get call recording — Get a single call recording by ID. This endpoint is in beta. We will aim to avoid breaking changes, but small updates may be made as we roll out to more users. Required scopes: `meeting:read`, `call_recording:read`. Supported token levels: `workspace`, `user`.
  • Create call recording — Create a call recording for a meeting. Supply a transcript for summaries and transcript-derived features; video_url is optional. Limited to one request per second.

Emails

1 operation

  • List emails — List email metadata from connected mailboxes. Email content is never returned; provide at least one supported filter. Multiple filters are combined with OR.

Entries

9 operations

  • Delete a list entry — Deletes a single list entry by its `entry_id`. Required scopes: `list_entry:read-write`, `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • Get a list entry — Gets a single list entry by its `entry_id`. Required scopes: `list_entry:read`, `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • List attribute values for a list entry — Get an attribute's values for a list entry. Set show_historic to include historical values, which are returned oldest first.
  • Update a list entry (append multiselect values) — Update a list entry by entry_id and prepend supplied multi-select values. Use PUT to replace existing values.
  • Create an entry (add record to list) — Adds a record to a list as a new list entry. This endpoint will throw on conflicts of unique attributes. Multiple list entries are allowed for the same parent record Required scopes: `list_entry:read-write`, `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • List entries — Lists entries in a given list, with the option to filter and sort results. Required scopes: `list_entry:read`, `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • Upsert a list entry by parent — Create or update a list entry for a parent record. Multiple matching entries return MULTIPLE_MATCH_RESULTS. Supplied multi-select values replace existing values.
  • Update a list entry (overwrite multiselect values) — Update a list entry by entry_id. Supplied multi-select values replace existing values; use PATCH to add values without removing existing ones.
  • Write list entry attribute values — Replace a list-entry attribute's full value history. Existing values are removed; provide at least one timestamped value. Single-value intervals cannot overlap, and only one may have no end time.

Files

6 operations

  • Delete a file — Delete a file by ID. Deleting a folder also deletes all descendants.
  • List files — List internal and connected files and folders for a record. Use object and record_id to identify it; optionally filter by storage provider or parent folder.
  • Get a file — Get a single file entry by ID. This endpoint is in beta. We will aim to avoid breaking changes, but small updates may be made as we roll out to more users. Required scopes: `file:read`, `object_configuration:read`, `record_permission:read`. Supported token levels: `workspace`, `user`.
  • Download a file — Download a file through a redirect to a signed URL.
  • Create a folder — Create a native folder or a connected file/folder entry on an object record.
  • Upload a file — Upload a file to Attio storage for a record using multipart/form-data with file, object, record_id, and optional parent_folder_id. Maximum file size is 50 MB; limited to one request per second.

Lists

5 operations

  • List all lists — List all lists that your access token has access to. lists are returned in the order that they are sorted in the sidebar. Required scopes: `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • Get a list — Gets a single list in your workspace that your access token has access to. Required scopes: `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • List views for list — Lists saved views for a list. Results are ordered by view ID (`id.view_id` ascending). Required scopes: `list_configuration:read`. Supported token levels: `workspace`, `user`.
  • Update a list — Update a list's access settings. Lists must grant full access to the workspace or at least one member. The parent object cannot be changed through this endpoint.
  • Create a list — Create a list for a parent object and configure workspace or member access. A list must grant full access to the workspace or at least one member.

Meetings

6 operations

  • Delete a meeting — Delete a meeting by ID. Calendar-synced meetings cannot be deleted through the API; delete the calendar event or disconnect the calendar instead.
  • List meetings — List workspace meetings in a deterministic order. When participants and linked_record_id are both supplied, meetings matching either filter are returned.
  • Get a meeting — Get a single meeting by ID. This endpoint is in beta. We will aim to avoid breaking changes, but small updates may be made as we roll out to more users. Required scopes: `meeting:read`, `record_permission:read`. Supported token levels: `workspace`, `user`.
  • Update a meeting (append linked records) — Add records to a meeting's existing links; linked records are ignored. Use PUT to replace links. Attio may link participant companies asynchronously.
  • Create a meeting — Create a meeting. Follow Attio's meeting-sync guidance to avoid duplicate meetings.
  • Update a meeting (overwrite linked records) — Replace a meeting's linked records with the supplied records. Omitted links are removed, including participant-derived links; an empty array clears all links. Use PATCH to add links without removing existing ones.

Meta

1 operation

  • Identify — Inspect an Attio access token to identify its workspace, client, audience, and granted permissions.

Notes

5 operations

  • Delete a note — Delete a single note by ID. Required scopes: `note:read-write`. Supported token levels: `workspace`, `user`.
  • List notes — List notes for all records or for a specific record. This endpoint is temporarily rate limited to 10 requests per second. Required scopes: `note:read`, `object_configuration:read`, `record_permission:read`. Supported token levels: `workspace`, `user`.
  • Get a note — Get a single note by ID. Required scopes: `note:read`, `object_configuration:read`, `record_permission:read`. Supported token levels: `workspace`, `user`.
  • Update a note — Update a note's title or content. Only supplied fields change; content replaces the full note body, and the parent record cannot be changed.
  • Create a note — Creates a new note for a given record. Required scopes: `note:read-write`, `object_configuration:read`, `record_permission:read`. Supported token levels: `workspace`, `user`.

Objects

6 operations

  • Delete an object — Delete a custom object by ID or slug, along with its records. System objects such as people and companies cannot be deleted.
  • List objects — Lists all system-defined and user-defined objects in your workspace. Required scopes: `object_configuration:read`. Supported token levels: `workspace`, `user`.
  • Get an object — Gets a single object by its `object_id` or slug. Required scopes: `object_configuration:read`. Supported token levels: `workspace`, `user`.
  • List views for object — Lists saved views for an object. Results are ordered by view ID (`id.view_id` ascending). Required scopes: `object_configuration:read`. Supported token levels: `workspace`, `user`.
  • Update an object — Updates a single object. The object to be updated is identified by its `object_id`. Required scopes: `object_configuration:read-write`. Supported token levels: `workspace`, `user`.
  • Create an object — Creates a new custom object in your workspace. Required scopes: `object_configuration:read-write`. Supported token levels: `workspace`, `user`.

Records

12 operations

  • Delete a record — Deletes a single record (e.g. a company or person) by ID. Required scopes: `object_configuration:read`, `record_permission:read-write`. Supported token levels: `workspace`, `user`.
  • Get a record — Gets a single person, company or other record by its `record_id`. Required scopes: `record_permission:read`, `object_configuration:read`. Supported token levels: `workspace`, `user`.
  • List record attribute values — Get an attribute's values for a record. Set show_historic to include historical values; this is unsupported for COMINT and enriched attributes. Values can be unavailable when the workspace lacks a required billing feature.
  • List record entries — List entries across all lists for a parent record. The response includes entry, list, and creation metadata but not entry values; retrieve each entry separately for its values.
  • Update a record (append multiselect values) — Update a record by record_id and prepend supplied multi-select values. Use PUT to replace existing values.
  • Create a record — Create a person, company, or other record. Unique-attribute conflicts return an error; use the upsert endpoint to update a matching record.
  • Merge two records — Merge two records of the same object. The primary record wins conflicts; both inputs are marked merged and replaced by a new record. A 202 response means processing is asynchronous; 200 means the result is ready.
  • List records — Lists people, company or other records, with the option to filter and sort results. Required scopes: `record_permission:read`, `object_configuration:read`. Supported token levels: `workspace`, `user`.
  • Search records — Fuzzy-search records across objects by names, domains, emails, phone numbers, social handles, and labels. Results may be eventually consistent; use the record query endpoint for current results.
  • Upsert a record — Create or update a record by matching the specified attribute. A match is updated; otherwise, a record is created. Use the create endpoint to avoid matching.
  • Update a record (overwrite multiselect values) — Update a record by record_id. Supplied multi-select values replace existing values; use PATCH to add values without removing existing ones.
  • Write record attribute values — Replace a record attribute's full value history. Existing values are removed; provide at least one timestamped value. Single-value intervals cannot overlap, and only one may have no end time.

Sequences

1 operation

  • Add emails to the unsubscribe list — Add emails to the workspace's sequence unsubscribe list. These addresses cannot be enrolled, and active sequence runs are exited. Existing entries are ignored, so the request is safe to retry.

Tasks

5 operations

  • Delete a task — Delete a task by ID. Required scopes: `task:read-write`. Supported token levels: `workspace`, `user`.
  • List tasks — List all tasks. Results are sorted by creation date, from oldest to newest. Required scopes: `task:read`, `object_configuration:read`, `record_permission:read`, `user_management:read`. Supported token levels: `workspace`, `user`.
  • Get a task — Get a single task by ID. Required scopes: `task:read`, `object_configuration:read`, `record_permission:read`, `user_management:read`. Supported token levels: `workspace`, `user`.
  • Update a task — Update a task by task_id. Only deadline_at, is_completed, linked_records, and assignees can be changed.
  • Create a task — Creates a new task. At present, tasks can only be created from plaintext without record reference formatting. Required scopes: `task:read-write`, `object_configuration:read`, `record_permission:read`, `user_management:read`. Supported token levels: `workspace`, `user`.

Threads

2 operations

  • List threads — List comment threads on a record or list entry. Each thread includes up to 80 oldest replies; use the thread-comments endpoint to retrieve more.
  • Get a thread and its comments — List a thread's comments oldest first, up to 250 per page. Follow next_cursor to continue. created_after filters comments by creation time; the opening comment appears only when it matches.

About Attio

The Attio n8n node connects your CRM records and lists with n8n. Work with people, companies, deals, and custom records, along with related items such as tasks, notes, meetings, and activities.

Attio node on an n8n workflow canvas

Connect Attio to n8n

  1. Install @nativeship/n8n-nodes-attio from Settings > Community Nodes in n8n.
  2. Create an OAuth app in the Attio developer console and add the redirect URL shown in your n8n credential settings to the app.
  3. In n8n, create an Attio OAuth2 API credential with the app's Client ID and Client Secret, then authorize the Attio workspace.
  4. Add the Attio node and select the resource and action you need.

Attio node details in n8n showing record, list, task, note, meeting, and activity actions

What you can do

Create, search, update, upsert, merge, and delete records in Attio objects. You can also create lists, add or update list entries, and work with tasks, notes, activities, meetings, comments, and files.

Built with NativeShip

NativeShip created and manages this Attio node. NativeShip helps SaaS companies launch and maintain official, verification-ready n8n community nodes in minutes, so customers can use their products directly in n8n.

Want to launch an n8n node for your SaaS? Explore NativeShip.

Attio questions

You can manage records, lists, list entries, tasks, notes, activities, meetings, comments, and files in Attio.

Yes. The node can create and manage objects and records, including records in custom objects.

Yes. Record actions include searching, listing, creating, updating, upserting, merging, and deleting records.

Yes. You can create and update lists, add records as list entries, and retrieve or update list entries.

The node uses an Attio OAuth2 API credential. Create an OAuth app in Attio, enter its Client ID and Client Secret in n8n, and authorize the workspace.

More CRM nodes

All CRM nodes

  • Close

    Published with provenancePublished with provenancenpm holds a signed attestation linking this release to the exact source commit and CI run that built it, so you can check what you install was built from the code it claims.What provenance means

    @nativeship/n8n-nodes-close

    Use the Close n8n node to manage leads, contacts, opportunities, tasks, sales activities, and reports in Close CRM.

    12 downloads last week

Ready to launch your n8n, Make, Zapier or Activepieces integration?

Give your customers another way to use your product.

Get started