Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
The node provides integration with a universal messaging gateway platform, allowing users to manage various resources such as platforms, API keys, identities, members, messages, projects, webhooks, and logs. Specifically, the Platforms - Delete operation enables users to remove a configured platform integration from a specified project. This is useful when you want to decommission or clean up platform configurations that are no longer needed.
Typical use cases include:
- Removing obsolete or unused platform integrations.
- Cleaning up platform configurations during project maintenance.
- Automating platform lifecycle management in workflows.
Example: You have a Telegram platform configured for your project but no longer need it. Using this node's Platforms Delete operation, you can programmatically delete that platform configuration by specifying its ID and project.
Properties
| Name | Meaning |
|---|---|
| Platform ID | The unique identifier of the platform configuration to delete. |
| Project | The project identifier within which the platform exists. Defaults to "default". |
| Id | Alias for Platform ID; the platform configuration's unique identifier (same as Platform ID). |
Note: The properties "Platform ID" and "Id" represent the same value (platform configuration ID) used to identify which platform to delete.
Output
The node outputs the JSON response returned by the platform's API after attempting to delete the specified platform configuration. Typically, this will be a confirmation of deletion or an error message if the deletion failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the GateKit API.
- The node uses the base URL provided by the API credentials to send HTTP DELETE requests.
- The user must specify the project identifier and platform ID to target the correct resource.
Troubleshooting
Common issues:
- Invalid or missing Platform ID: The API will reject the request if the platform ID does not exist or is not provided.
- Incorrect project identifier: If the project does not contain the specified platform, deletion will fail.
- Insufficient permissions: The API key used must have rights to delete platform configurations.
- Network or connectivity issues with the API endpoint.
Error messages:
- "404 Not Found": The platform ID or project was not found. Verify the IDs.
- "401 Unauthorized" or "403 Forbidden": Authentication failure or insufficient permissions. Check API key validity and scopes.
- "400 Bad Request": Missing required parameters or invalid input format.
Resolution tips:
- Double-check the platform ID and project name.
- Ensure the API key credential is correctly configured and has necessary permissions.
- Review API documentation for any additional constraints on deletion.
Links and References
- GateKit API Documentation (general reference for platform management)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls (conceptual)
- GateKit supported platforms info can be retrieved via the node's "Supported" operation under Platforms resource.