GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Members Actions
Projects Actions
- Create
- Update
Platforms Actions
Messages Actions
- List
- Stats
- Get
- Cleanup
- Send
- Status
- Retry
- Sent
ApiKeys Actions
Platform Logs Actions
- Logs

Overview

This node provides integration with the GateKit messaging gateway API, allowing users to manage various resources such as members, projects, platforms, messages, API keys, and platform logs. Specifically, for the Platforms resource with the Delete operation, the node enables the removal of a configured platform integration from a specified project.

Use cases include:

Removing obsolete or unused platform integrations from your messaging projects.
Cleaning up platform configurations when migrating or decommissioning services.
Managing project resources programmatically within an automation workflow.

For example, if you have integrated Telegram and Discord platforms into a project but no longer need the Discord integration, this node can delete that platform configuration by specifying the project slug and platform ID.

Properties

Name	Meaning
Platform ID	The unique identifier of the platform configuration to delete.
Project Slug	The identifier (slug) of the project where the platform is configured.
Id	Alias for Platform ID; represents the platform configuration's unique identifier.

Note: The properties "Platform ID" and "Id" both represent the platform configuration ID required to identify which platform to delete.

Output

The node outputs the JSON response returned by the GateKit API after attempting to delete the platform configuration. This typically includes confirmation of deletion or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

Requires an API key credential for authenticating with the GateKit API.
The node uses the base URL provided by the API credentials to send HTTP DELETE requests.
Proper permissions on the API key are necessary to delete platform configurations within the specified project.

Troubleshooting

Common issues:
- Invalid or missing Platform ID or Project Slug will cause the request to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Attempting to delete a non-existent platform configuration will return an error.
Error messages:
- 404 Not Found: The specified platform ID does not exist in the given project.
- 401 Unauthorized: API key is invalid or lacks permission to perform deletion.
- 400 Bad Request: Missing required parameters or malformed request.
Resolution tips:
- Verify that the Platform ID and Project Slug are correct and correspond to existing resources.
- Ensure the API key used has the necessary scopes/permissions.
- Check network connectivity and API endpoint correctness.

Links and References

GateKit API Documentation (general reference for API endpoints and authentication)
n8n documentation on HTTP Request Node for understanding how API calls are made
GateKit supported platforms and their credential requirements can be viewed via the "supported" operation on Platforms resource within this node.