Actions25
- Batch Actions
- Company Actions
- Core Schema Actions
- Note Actions
- Person Actions
Batch → Create Notes
AI-generatedOverview
This node interacts with the Twenty API to create notes in batch mode. It allows users to send multiple note records in a single batch request to the Twenty workspace REST API. This is useful for efficiently creating many notes at once, such as importing notes from another system or automating note creation based on workflow data.
Use Case Examples
- Importing a list of notes from a CRM system into Twenty by sending them as a batch JSON array.
- Automating note creation for multiple contacts or companies in Twenty by preparing note data in the workflow and sending it in one batch request.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL for the Twenty workspace REST API, including the /rest suffix. |
| Records (JSON) | Raw JSON array containing the note records to send in the batch request. If left empty, the node uses the incoming item data as the batch records. |
| Depth | Controls whether related records are expanded in the response. Options are 'Primary Record Only' or 'Include Direct Relations'. |
| Upsert Strategy | Controls whether existing records are updated when matching criteria is met. Options are 'Create Only' (skip existing matches) or 'Create or Update' (upsert). |
| Request Options | Additional request options such as batching controls, SSL certificate validation, proxy settings, and request timeout. |
Output
JSON
id- The unique identifier of the created note record.content- The content or body of the created note.createdAt- Timestamp when the note was created.updatedAt- Timestamp when the note was last updated.relatedRecords- Any related records included in the response if depth option is set to include relations.
Dependencies
- Requires an API key credential for authenticating with the Twenty workspace REST API.
Troubleshooting
- Ensure the Base URL is correctly set to your Twenty workspace REST API endpoint including the /rest suffix.
- If using upsert strategy, verify that matching criteria are correctly defined to avoid unintended skips or updates.
- Batching settings should be adjusted according to API rate limits to prevent throttling or request failures.
- If SSL certificate validation fails, enabling 'Ignore SSL Issues' may help but use with caution due to security risks.
- Proxy settings must be correctly formatted if used, including authentication if required.
- Timeout should be set sufficiently high to allow the server to respond, especially for large batch requests.