Actions52
- Records Actions
- Comments Actions
- Objects Actions
- Attributes Actions
- List Attributes
- Create Attribute
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- GET target/identifier/attributes/attribute/statuses
- POST target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Lists Actions
- Entries Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
Overview
This node allows you to create a new note in the Attio system. It is useful for adding detailed textual information linked to other objects such as people, companies, or deals within your workspace. Typical use cases include logging meeting summaries, call notes, project updates, or any contextual information that needs to be associated with existing records.
For example, after a sales call, you can use this node to create a note summarizing the discussion points, action items, and next steps, linking it to the relevant contact or deal record.
Properties
| Name | Meaning |
|---|---|
| Data | A JSON object representing the note details. This includes: - parent_object: The type of object the note is linked to (e.g., "people"). - parent_record_id: The unique identifier of the record the note belongs to. - title: The title of the note. - content: The main content of the note, supporting markdown formatting. - created_at: Timestamp indicating when the note was created. |
Output
The node outputs an array of JSON objects, each representing the response from the Attio API after creating a note. Each output item contains:
json: The full JSON response from the API, which typically includes the newly created note's data such as its ID, timestamps, linked parent object info, title, and content.
There is no binary data output by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Attio API.
- The node sends HTTP requests to the Attio API endpoint
https://api.attio.com/v2/notes. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication errors.
- Incorrect
parent_objectorparent_record_idvalues may result in errors or notes not being linked properly. - Malformed JSON in the
Dataproperty can cause parsing errors before sending the request.
Error messages:
"Operation ... not found for resource ...": Indicates a misconfiguration or unsupported operation/resource combination.- API errors returned from Attio (e.g., 400 Bad Request) usually contain descriptive messages about what went wrong; verify the input data accordingly.
Resolutions:
- Ensure the API key credential is valid and has appropriate permissions.
- Double-check the JSON structure and required fields in the
Dataproperty. - Confirm that the referenced parent object and record exist in Attio.
Links and References
- Attio API Documentation (for details on note creation and supported fields)
- Markdown Guide (to format the note content)