GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Overview

The node provides integration with the GateKit universal messaging gateway API, allowing users to manage and interact with various messaging platforms configured within a project. Specifically, for the Platforms resource with the List operation, this node fetches a list of all platform integrations configured for a specified project.

This is useful in scenarios where you want to retrieve and display all messaging platforms (e.g., Discord, Telegram, WhatsApp) that are set up under a particular project in GateKit. For example, you might use this to audit your current platform configurations or dynamically select a platform for sending messages in subsequent workflow steps.

Properties

Name Meaning
Project The identifier of the project to operate on. This specifies which project's platforms will be listed. Default is "default".

Output

The output JSON contains an array of platform configuration objects representing each platform integrated into the specified project. Each object typically includes details such as platform type, name, description, credentials (not exposed directly), status flags like active or test mode, and unique identifiers.

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 credential's API URL setting.
  • The user must have appropriate permissions to access platform configurations within the specified project.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Specifying a non-existent project identifier will result in errors or empty results.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • "Project not found" or similar errors suggest the project ID is incorrect or the user lacks access.
    • Rate limiting or server errors from the API should be retried after some delay.

Links and References

Discussion