GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Overview

The node provides an interface to update the configuration of a messaging platform integration within a specified project. It allows users to modify platform credentials, enable or disable the platform, and toggle test mode for the platform. This is useful in scenarios where you need to update authentication details, change platform availability, or switch between live and test environments without recreating the platform integration.

Practical examples include:

  • Updating API keys or tokens for a Discord or Telegram platform integration.
  • Temporarily disabling a WhatsApp platform integration during maintenance.
  • Enabling test mode to simulate message sending without affecting live data.

Properties

Name Meaning
Project Slug Identifier of the project to which the platform belongs (required).
Id Unique identifier of the platform configuration to update (required).
Updated credentials (JSON object) JSON object containing updated platform credentials; used to change authentication details (optional).
Enable/disable platform Boolean flag to activate (true) or deactivate (false) the platform integration (optional).
Enable/disable test mode Boolean flag to enable (true) or disable (false) test mode for the platform (optional).

Output

The node outputs the response from the platform update API call as JSON. This typically includes the updated platform configuration details such as platform ID, status flags, and possibly updated credential metadata. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the GateKit API.
  • Needs the base URL of the GateKit API configured in the credentials.
  • The project slug and platform ID must correspond to existing entities in the GateKit system.

Troubleshooting

  • Invalid or missing projectSlug or id: The API will fail if the specified project or platform ID does not exist. Verify these identifiers are correct.
  • Malformed credentials JSON: If the credentials property contains invalid JSON, the request will be rejected. Ensure valid JSON format.
  • Permission errors: Insufficient API key permissions may cause authorization failures. Confirm the API key has rights to update platform configurations.
  • Network or API endpoint issues: Connectivity problems or incorrect base URL settings can cause request failures. Check network access and credential configuration.

Links and References

Discussion