Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Custom → Create
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources, including a customizable "Custom" resource. Specifically for the Create operation on the Custom resource, it allows users to create new records by specifying the resource name and providing field values as a JSON object. This flexibility is useful when working with custom or less common data types in Twenty CRM that are not covered by predefined resources.
Practical examples:
- Creating a new custom entity such as "blocklists" or "workflows" by specifying the resource name and fields.
- Automating the creation of specialized records that extend standard CRM functionality without needing additional node development.
Properties
| Name | Meaning |
|---|---|
| Custom Resource Name | The plural name of the custom resource you want to create (e.g., "blocklists", "workflows", "views"). |
| Fields JSON | A JSON object containing the field values for the new record. Must be valid JSON representing the data structure expected by the custom resource. |
Output
The node outputs an array of JSON objects representing the newly created records returned from the Twenty CRM API. Each item corresponds to one input item processed.
- The
jsonoutput contains the full response data for the created custom resource record. - No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Twenty CRM API via an API key credential configured in n8n.
- The node uses the base API URL and authentication details from the provided credentials.
- Proper permissions on the Twenty CRM account to create records in the specified custom resource.
Troubleshooting
- Invalid JSON in Fields: If the
Fields JSONproperty contains malformed JSON, the node will throw an error indicating invalid JSON. To fix, ensure the JSON syntax is correct and matches the expected schema for the custom resource. - API Authentication Errors: If the API key credential is missing, invalid, or lacks permissions, requests will fail. Verify the credential configuration and access rights.
- Resource Not Found or Invalid Resource Name: Providing an incorrect or non-existent custom resource name will cause API errors. Confirm the exact plural resource name as defined in Twenty CRM.
- Network or API Errors: General HTTP errors may occur due to connectivity issues or API limits. Check network status and API usage quotas.
Links and References
- Twenty CRM API Documentation (for detailed API endpoints and data schemas)
- n8n Documentation - Creating Custom Nodes