MsgCore icon

MsgCore

Universal messaging gateway - send messages across multiple platforms

Actions52

Overview

This node provides access to a universal messaging gateway API, allowing users to manage webhooks within projects. Specifically, the "Get" operation under the "Webhooks" resource retrieves detailed information about a specific webhook, including its delivery statistics. This is useful for monitoring and debugging webhook configurations in messaging platforms.

Common scenarios include:

  • Fetching the configuration and status of a particular webhook.
  • Checking delivery statistics to ensure events are being sent correctly.
  • Integrating webhook management into automated workflows for messaging projects.

Example: A user wants to verify the details and recent activity of a webhook used to receive message notifications in their project. Using this node's "Get Webhook" operation, they can retrieve that data programmatically.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook to retrieve.
Project The identifier of the project where the webhook is configured; defaults to "default".

Note: The provided properties JSON includes some duplicate entries for "webhookId" with slightly different casing or descriptions, but effectively they represent the same required input: the webhook's ID.

Output

The output json field contains the detailed information of the requested webhook, including its configuration and delivery statistics as returned by the API. This typically includes fields such as webhook name, URL, subscribed events, active status, and metrics on delivery attempts.

No binary data output is indicated 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.
  • The "project" parameter must correspond to an existing project in the system.
  • Network connectivity to the API endpoint /api/v1/projects/{project}/webhooks/{webhookId} is necessary.

Troubleshooting

  • Missing or invalid Webhook ID: Ensure the "Webhook ID" property is set correctly and corresponds to an existing webhook.
  • Invalid Project Identifier: Verify the "Project" value matches a valid project accessible with your credentials.
  • Authentication errors: Confirm the API key credential is valid and has permissions to read webhook data.
  • Network issues: Check connectivity to the API server.
  • API errors: If the webhook does not exist or is inaccessible, the API may return 404 or permission errors.

Resolving these usually involves verifying input parameters, credentials, and network access.

Links and References

Discussion