GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions51

Overview

The "Sent Messages" operation of the GateKit node allows users to retrieve a list of messages that have been sent within a specified project. This operation is useful for monitoring and auditing message delivery across multiple messaging platforms integrated into the project. Users can filter the results by platform type and message status, control pagination with limit and offset parameters, and specify the project context.

Practical examples include:

  • Fetching all sent messages on Telegram to verify delivery.
  • Listing failed messages on WhatsApp to identify issues.
  • Retrieving a limited number of recent sent messages for reporting purposes.

Properties

Name Meaning
Filter by platform Filter messages by platform type. Options: telegram, discord, whatsapp-evo (string).
Filter by status Filter messages by their sending status. Options: pending, sent, failed (string).
Number of messages to return Limit the number of messages returned in the response (number). Default is 50.
Number of messages to skip Skip a number of messages for pagination (number).
Project Identifier of the project to operate on (string). Required.

Output

The output JSON contains an array of sent message objects corresponding to the query parameters. Each message object typically includes details such as message ID, content, platform information, status, timestamps, and metadata related to the sent message.

If the node supports binary data output for this operation, it would represent any associated media or attachments sent with the messages, but based on the static analysis, this operation primarily returns JSON data about sent messages.

Dependencies

  • Requires an API key credential for authenticating requests to the GateKit API.
  • The node makes HTTP GET requests to the endpoint /api/v1/projects/{project}/messages/sent.
  • The project parameter must be provided to specify the project context.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common Issues:

    • Missing or invalid API key credential will cause authentication failures.
    • Providing an incorrect or non-existent project identifier will result in errors or empty responses.
    • Using unsupported platform values may yield no results.
    • Pagination parameters (limit and offset) should be used carefully to avoid unexpected empty pages.

  • Error Messages:

    • Authentication errors typically indicate missing or invalid API credentials.
    • "Project not found" or similar errors suggest the specified project does not exist or access is denied.
    • Validation errors may occur if parameters like status or platform have invalid values.

To resolve these issues:

  • Ensure the API key credential is correctly configured in n8n.
  • Verify the project identifier exists and the user has access.
  • Use valid values for filters according to the documented options.
  • Adjust pagination parameters to valid ranges.

Links and References

Discussion