GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Overview

This node operation "Sent" under the "Messages" resource allows users to list sent messages for a specific project. It is useful for retrieving historical data about messages that have been dispatched through various messaging platforms integrated into the project. Typical use cases include auditing message delivery, monitoring message statuses (such as pending, sent, or failed), and paginating through large sets of sent messages.

For example, a user might want to fetch all sent messages filtered by platform "telegram" and status "sent" to verify successful deliveries or troubleshoot issues with message sending on that platform.

Properties

Name Meaning
Filter by platform Optional filter to restrict results to a specific messaging platform. Options: telegram, discord, whatsapp-evo
Filter by status (pending, sent, failed) Optional filter to restrict results by message status. Options: pending, sent, failed
Number of messages to return Optional limit on how many messages to retrieve in one request. Default is 50.
Number of messages to skip Optional offset to skip a number of messages, useful for pagination.
Project Slug Required identifier of the project whose sent messages are being queried.

Output

The output will be a JSON array containing objects representing sent messages. Each object typically includes details such as message ID, platform, status, timestamps, and other metadata related to the sent message. This allows downstream nodes or workflows to process or analyze the sent message data.

The node does not explicitly handle binary data for this operation; it focuses on JSON structured data representing message records.

Dependencies

  • Requires an API key credential for authentication to the GateKit messaging gateway API.
  • The node makes HTTP GET requests to the endpoint /api/v1/projects/{projectSlug}/messages/sent with optional query parameters based on the input properties.
  • The base URL for the API is configured via credentials (apiUrl).

Troubleshooting

  • Empty results: Ensure the projectSlug is correct and that there are actually sent messages matching the filters.
  • Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
  • Invalid filter values: Use only supported platform names ("telegram", "discord", "whatsapp-evo") and status values ("pending", "sent", "failed").
  • Pagination issues: If using limit and offset, ensure they are within valid ranges and correctly set to avoid missing or duplicate data.

Links and References

Discussion