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 custom object schema in the Attio platform via its API. It is useful when you want to define new data structures (objects) such as "Person", "Company", or any other entity type that your workspace will manage. For example, you can create an object representing "People" with specific singular and plural names and an API slug for referencing it programmatically.
Typical use cases include:
- Automating the creation of new data models in Attio as part of a workflow.
- Dynamically defining objects based on external input or integration needs.
- Setting up custom CRM entities or other structured data types without manual UI interaction.
Properties
| Name | Meaning |
|---|---|
| Data | JSON object defining the new object's schema. It includes fields like api_slug (a unique identifier used in API calls), singular_noun (the singular name of the object, e.g., "Person"), and plural_noun (the plural form, e.g., "People"). The value must be valid JSON. |
Example of the Data property default value:
{
"api_slug": "people",
"singular_noun": "Person",
"plural_noun": "People"
}
Output
The node outputs the JSON response from the Attio API after creating the object. This typically contains details about the newly created object, including its ID, names, and other metadata returned by the API.
The output structure is:
json: An object representing the created object resource as returned by the API.
No binary data output 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/objectsendpoint. - The API key must have permissions to create objects in the target Attio workspace.
Troubleshooting
- Invalid JSON in Data: If the
Dataproperty contains malformed JSON, the node will fail parsing it. Ensure the JSON is valid. - Authentication errors: If the API key is missing, invalid, or expired, the request will fail with authorization errors. Verify the API key credential configuration.
- API errors: If the object slug already exists or required fields are missing, the API may return validation errors. Check the error message for details.
- Network issues: Connectivity problems to the Attio API endpoint will cause request failures.
Common error messages:
"Operation POST -v2-objects not found for resource Objects": Indicates misconfiguration or unsupported operation."Operation configuration not found for POST -v2-objects": Internal config issue; ensure node version and properties are correct.
Links and References
- Attio API Documentation — Official API reference for creating objects.
- n8n HTTP Request Node — General info on how HTTP requests work in n8n nodes.