Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The "Messages - Sent" operation in this node allows users to list sent messages for a specific project. It provides filtering options such as platform type and message status (pending, sent, failed), along with pagination controls like limit and offset. This operation is useful for monitoring outgoing messages across multiple messaging platforms integrated within a project.
Typical use cases include:
- Retrieving a list of all messages sent through various platforms for auditing or reporting.
- Filtering sent messages by their delivery status to identify pending or failed messages.
- Paginating through large sets of sent messages to process or analyze them incrementally.
For example, a user might want to fetch the last 50 successfully sent messages on the Telegram platform for their project to verify delivery performance.
Properties
| Name | Meaning |
|---|---|
| Filter by platform | Filter messages by platform type. Options include platform identifiers like "telegram", "discord", "whatsapp-evo". |
| Filter by status (pending, sent, failed) | Filter messages by their delivery status: "pending", "sent", or "failed". |
| Number of messages to return | Limit the number of messages returned in the response. Defaults to 50. |
| Number of messages to skip | Offset to skip a number of messages, useful for pagination. |
| Project | The identifier of the project to operate on. This is required to specify which project's sent messages to retrieve. |
Output
The output JSON contains an array of sent message objects corresponding to the query parameters provided. Each object represents a sent message with details such as platform, status, timestamps, and message content metadata.
The node does not explicitly mention binary data output for this operation, so the output is purely JSON structured data representing sent messages.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the messaging gateway API.
- The node uses the base URL from the credentials configuration to make HTTP GET requests to the endpoint
/api/v1/projects/{project}/messages/sent. - No additional external dependencies are indicated.
Troubleshooting
- Empty results: If no messages are returned, verify that the project ID is correct and that there are sent messages matching the filter criteria.
- Authentication errors: Ensure the API key credential is valid and has permissions to access message data for the specified project.
- Invalid filter values: Using unsupported platform names or statuses may result in errors or empty responses. Use only supported platform identifiers and status values ("pending", "sent", "failed").
- Pagination issues: When using
limitandoffset, ensure values are within acceptable ranges to avoid unexpected results.
Links and References
- MsgCore API Documentation (replace with actual URL if available)
- n8n documentation on HTTP Request Node for understanding how routing and request defaults work in custom nodes.