MsgCore icon

MsgCore

Universal messaging gateway - send messages across multiple platforms

Actions52

Overview

The node provides integration with a universal messaging gateway platform, allowing users to manage and interact with multiple messaging platforms through a single interface. Specifically, the "Platforms" resource with the "Get" operation retrieves detailed configuration information about a specific platform integration within a project.

This node is beneficial when you want to programmatically access the configuration details of a messaging platform (such as Discord, Telegram, or WhatsApp) that has been set up in your project. For example, you might use it to verify platform settings before sending messages or to audit platform configurations.

Practical example:

  • Retrieve the configuration details of a Telegram platform integration by specifying its Platform ID and the project it belongs to.

Properties

Name Meaning
Platform ID The unique identifier of the platform configuration to retrieve.
Project The identifier of the project under which the platform is configured.
Id Alias for Platform ID; used as an identifier parameter for the request.

Output

The output contains a JSON object representing the detailed configuration of the specified platform integration. This includes all relevant platform settings such as platform type, credentials, status flags (active/test mode), and descriptive metadata.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication to the messaging gateway service.
  • The node makes HTTP requests to the messaging gateway API endpoint configured via credentials.
  • The user must have appropriate permissions to access platform configurations within the specified project.

Troubleshooting

  • Common issues:

    • Invalid or missing Platform ID: The node will fail if the provided Platform ID does not exist or is empty.
    • Incorrect project identifier: If the project name is incorrect or the user lacks access, the request will be denied.
    • Authentication errors: Missing or invalid API key credential will cause authorization failures.

  • Error messages:

    • "404 Not Found": The specified platform configuration does not exist in the project.
    • "401 Unauthorized": Authentication failed due to invalid or missing API key.
    • "400 Bad Request": Required parameters are missing or malformed.

  • Resolutions:

    • Verify the Platform ID and project name are correct.
    • Ensure the API key credential is properly configured and has sufficient permissions.
    • Check network connectivity to the messaging gateway API.

Links and References

Discussion