TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node operation deletes a single calendar event identified by its unique ID. It is useful in scenarios where you need to programmatically remove an event from a calendar, such as cancelling appointments, removing outdated events, or cleaning up test data.

For example, if you have an automation that manages your calendar and an event is no longer relevant, this node can be used to delete that specific event by providing its ID.

Properties

Name Meaning
Id The unique identifier of the calendar event to delete. This is required to specify which event should be removed.

Output

The output will typically contain JSON data confirming the deletion of the specified calendar event. This may include status information or details about the deleted event depending on the API's response. The node does not output binary data.

Dependencies

  • Requires an API key credential for authentication with the external calendar service.
  • The node depends on the external calendar API endpoint that supports deleting events by ID.
  • Proper configuration of the API base URL and authentication credentials is necessary within n8n.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent event ID will likely result in an error indicating the event could not be found.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity problems can prevent the node from reaching the calendar service.
  • Error messages and resolutions:

    • "Event not found": Verify that the provided event ID is correct and exists in the calendar.
    • "Authentication failed": Check that the API key or authentication token is correctly configured and has sufficient permissions.
    • "Network error" or "Timeout": Ensure that the n8n instance has internet access and the calendar API endpoint is reachable.

Links and References

  • Refer to the calendar service’s official API documentation for details on deleting events by ID.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.

Discussion