TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node operation deletes a single calendar channel by its unique identifier. It is useful in scenarios where you need to programmatically remove calendar channels that are no longer needed or were created by mistake. For example, if you manage multiple calendar integrations and want to clean up unused channels automatically, this operation allows you to specify the exact channel to delete.

Properties

Name Meaning
Id The unique identifier of the calendar channel to delete. This is a required string value representing the object id.

Output

The output JSON will typically contain confirmation details about the deletion operation. This may include status information or metadata confirming that the specified calendar channel was successfully deleted. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the external service providing calendar channel management.
  • The node uses a base URL configured from credentials to send requests to the appropriate API endpoint.

Troubleshooting

  • Common issues:
    • Providing an invalid or non-existent channel Id will likely result in an error indicating the resource could not be found.
    • Missing or incorrect API authentication credentials will cause authorization errors.
  • Error messages:
    • "Object id not found" or similar indicates the provided Id does not correspond to any existing calendar channel.
    • "Unauthorized" or "Authentication failed" suggests problems with the API key or token; verify credentials and permissions.
  • To resolve these, ensure the Id is correct and the API credentials are valid and have sufficient permissions.

Links and References

  • Refer to the external API documentation for calendar channel management for detailed information on the delete operation and required permissions.
  • Consult n8n documentation on setting up API credentials and using HTTP request nodes for additional context on authentication setup.

Discussion