Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides access to a universal messaging gateway API that allows users to interact with messages across multiple platforms within projects. Specifically, the "Messages" resource with the "Stats" operation retrieves message statistics for a given project. This is useful for monitoring and analyzing messaging activity, such as volume, trends, or performance metrics, across all integrated platforms in a project.
Practical examples include:
- Getting an overview of message traffic in a project to assess engagement.
- Monitoring message delivery success rates or failures.
- Analyzing usage patterns over time for reporting or optimization.
Properties
| Name | Meaning |
|---|---|
| Project | Project identifier to operate on (string). |
This property specifies which project’s message statistics to retrieve.
Output
The output JSON contains the message statistics data returned by the API for the specified project. The exact structure depends on the API response but typically includes aggregated counts, metrics, or summaries related to messages sent, received, failed, etc., within the project.
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 from the configured credentials to make HTTP requests.
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common issues:
- Invalid or missing project identifier will cause the API request to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network connectivity issues preventing access to the API endpoint.
Error messages:
- Unauthorized or 401 errors indicate problems with API credentials.
- 404 Not Found may indicate the project does not exist.
- 400 Bad Request could mean invalid parameters were provided.
Resolutions:
- Verify the project ID is correct and exists.
- Ensure the API key credential is properly configured and has necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Refer to the messaging gateway API documentation for detailed information on message statistics endpoints and response formats.
- Consult n8n documentation on setting up API key credentials and HTTP request nodes for integration details.