Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides integration with a universal messaging gateway platform, allowing users to manage various resources such as platforms, messages, identities, projects, and more. 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 within workflows.
For example, if you have integrated Telegram or Discord platforms into your project and want to delete one of these platform configurations programmatically, this operation facilitates that.
Properties
| Name | Meaning |
|---|---|
| Platform ID | The unique identifier of the platform configuration to delete. |
| Project | The project identifier under which the platform configuration exists (default: "default"). |
| Id | Alias for Platform ID; the identifier parameter specifying which platform to delete. |
Note: The properties "Platform ID" and "Id" represent the same required string input identifying the platform to delete.
Output
The output of the delete operation typically contains JSON data confirming the deletion status or details about the removed platform configuration. Since this is a delete operation, the response usually includes success confirmation or error information if the deletion failed.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authentication to the messaging gateway API.
- The node uses the base URL and headers configured via credentials to make HTTP DELETE requests.
- The project identifier must be provided to scope the deletion request correctly.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent Platform ID will result in an error indicating the platform was not found.
- Missing or invalid API authentication credentials will cause authorization failures.
- Incorrect project identifier may lead to inability to locate the platform configuration.
Error messages:
- 404 Not Found: The specified platform ID does not exist in the given project.
- 401 Unauthorized: Authentication failed due to missing or invalid API key.
- 400 Bad Request: Required parameters like Platform ID or Project are missing or malformed.
Resolution tips:
- Verify the Platform ID is correct and exists in the target project.
- Ensure the API key credential is properly configured and has sufficient permissions.
- Double-check the project identifier matches the intended project context.
Links and References
- MsgCore API Documentation (generic reference to the messaging gateway API)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- Messaging platform integration guides (Telegram, Discord, WhatsApp) as applicable for platform setup and management