TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node allows you to delete a single connected account by specifying its unique identifier. It is useful in scenarios where you need to programmatically remove access or revoke permissions for an external service or user account that was previously linked. For example, if you manage multiple integrations and want to clean up unused or expired connections, this operation helps automate that process.

Properties

Name Meaning
Id The unique identifier of the connected account to be deleted. This is a required string value.

Output

The output will typically contain a JSON object indicating the result of the deletion operation. This may include confirmation of successful deletion or details about the removed connected account. No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential to authenticate requests against the external service managing connected accounts.
  • The node uses a base URL configured via credentials to send HTTP requests.
  • The underlying implementation depends on an OpenAPI specification for request construction.

Troubleshooting

  • Missing or invalid Id: If the "Id" property is not provided or incorrect, the node will fail to locate the connected account to delete. Ensure the correct identifier is used.
  • Authentication errors: Failure to provide valid API credentials or token will result in authorization errors. Verify that the API key or authentication token is correctly configured.
  • Network or API errors: Issues such as timeouts, rate limits, or server errors from the external service can cause failures. Check network connectivity and API status.
  • Permission issues: The authenticated user or API key might lack permission to delete connected accounts. Confirm appropriate access rights.

Links and References

  • Refer to the external service’s API documentation for details on connected account management and deletion endpoints.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.

Discussion