Actions26
Overview
The node provides integration with the GateKit messaging gateway platform, specifically allowing users to manage and retrieve information about configured messaging platforms within a project. The "Get" operation under the "Platforms" resource fetches detailed configuration information for a specific platform integration associated with a given project.
This node is beneficial in scenarios where you need to programmatically access platform configuration details such as credentials, status, or settings for platforms like Discord, Telegram, or WhatsApp integrated into your messaging projects. For example, you might use it to verify platform setup before sending messages or to audit platform configurations across multiple projects.
Properties
| Name | Meaning |
|---|---|
| Platform ID | The unique identifier of the platform configuration to retrieve. |
| Project Slug | The identifier (slug) of the project that owns the platform configuration. |
| Id | Alias for Platform ID; the unique identifier parameter for the platform to get details. |
Output
The output JSON contains the detailed configuration data of the requested platform integration within the specified project. This typically includes platform-specific credentials, status flags (e.g., active or test mode), and other metadata related to the platform setup.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node uses the base URL provided by the API credentials to make HTTP GET requests.
- The user must provide valid
projectSlugandidparameters to identify the target platform configuration.
Troubleshooting
Common Issues:
- Invalid or missing Platform ID or Project Slug will result in errors or empty responses.
- Authentication failures if the API key credential is incorrect or expired.
- Network connectivity issues preventing access to the GateKit API endpoint.
Error Messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and has necessary permissions.
- "Platform not found": Verify that the Platform ID and Project Slug are correct and that the platform exists.
- "Bad Request": Ensure all required parameters are provided and properly formatted.
Links and References
- GateKit API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics