Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to perform various operations on CRM resources, including calendar events. Specifically, for the Calendar Event - Get operation, it retrieves a single calendar event record by its unique ID. This is useful when you want to fetch detailed information about a specific calendar event stored in your CRM system.

Common scenarios include:

• Fetching details of a scheduled meeting or event to display or process further.
• Integrating calendar event data into workflows for notifications or reporting.
• Synchronizing calendar events between Twenty CRM and other systems.

Example: You have an event ID from a previous step or external source, and you want to retrieve all details about that event (such as title, time, participants) to use in your automation.

Properties

Output

The node outputs the retrieved calendar event data as JSON. The structure corresponds to the fields defined by the Twenty CRM API for a calendar event, typically including properties such as event title, start and end times, description, attendees, location, and other metadata.

If multiple items are processed, each output item corresponds to one calendar event record fetched by ID.

No binary data output is produced by this operation.

Dependencies

• Requires connection to the Twenty CRM API via an API key credential configured in n8n.
• The node uses HTTP requests authenticated with this credential to interact with the Twenty CRM REST API endpoint.
• The base URL for the API is obtained from the credential configuration.

Troubleshooting

• Invalid or missing ID: If the provided ID is empty or incorrect, the API will return an error indicating the record was not found. Ensure the ID is valid and exists in the CRM.
• Authentication errors: If the API key credential is invalid or expired, authentication will fail. Verify the credential setup in n8n.
• API rate limits or connectivity issues: Network problems or API throttling can cause request failures. Check network connectivity and API usage limits.
• JSON parsing errors: Although unlikely for the "Get" operation, malformed JSON inputs in other operations can cause errors. For "Get", ensure the ID is a proper string.

Error messages returned by the node typically include the API error message. To resolve, verify input parameters and credentials.

Links and References

• Twenty CRM API Documentation (general reference for resource fields and endpoints)
• n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)

This summary focuses solely on the "Calendar Event" resource and the "Get" operation as requested.