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 updates an existing object definition in the Attio system via its API. It is useful when you want to modify metadata about a specific object type, such as changing its API slug or updating its singular and plural names. For example, if you have a "people" object representing contacts and want to rename it or adjust its properties, this node allows you to send those changes programmatically.
Typical use cases include:
- Renaming an object type in your workspace.
- Adjusting object metadata to better reflect your data model.
- Automating schema updates as part of a larger workflow.
Properties
| Name | Meaning |
|---|---|
| Object | A UUID or slug string identifying the object to update. Example: "people" |
| Data | JSON object containing the fields to update on the object. Common fields include: - api_slug: The new API slug for the object.- singular_noun: The singular name of the object.- plural_noun: The plural name of the object.Example: json<br>{<br> "api_slug": "people",<br> "singular_noun": "Person",<br> "plural_noun": "People"<br>}<br> |
Output
The node outputs the JSON response from the Attio API after updating the object. This typically includes the updated object details reflecting the changes made. The output structure corresponds directly to the API's response schema for an updated object.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node sends authenticated HTTP PATCH requests to the Attio API endpoint for objects.
- The base URL used is
https://api.attio.com. - Proper permissions on the API key are necessary to update objects.
Troubleshooting
Common issues:
- Invalid or missing object identifier (UUID or slug) will cause the API to reject the request.
- Malformed JSON in the Data property can cause parsing errors.
- Insufficient API permissions will result in authorization errors.
- Network connectivity problems may cause request failures.
Error messages:
"Operation configuration not found": Indicates the selected operation is not properly configured; ensure the correct resource and operation are chosen.- API error responses will be passed through; check the message for details like invalid fields or unauthorized access.
Resolutions:
- Verify the object identifier is correct and exists.
- Validate JSON syntax before inputting into the Data field.
- Confirm the API key has update permissions.
- Check network connectivity and proxy settings if applicable.