Actions26
Overview
The "Platform Logs" resource with the "Logs" operation allows users to retrieve platform processing logs related to a specific project and platform configuration. This node is useful for monitoring, debugging, and auditing activities across messaging platforms integrated into a project. It supports filtering logs by platform type (e.g., Telegram, Discord), log level (info, warn, error, debug), category (connection, webhook, message, error, auth, general), date ranges, and pagination controls.
Practical examples include:
- Fetching recent error logs from a Telegram integration to troubleshoot message delivery issues.
- Retrieving all warning-level logs for a Discord platform within a specific time frame.
- Auditing authentication-related logs to verify access events on a given platform.
Properties
| Name | Meaning |
|---|---|
| Slug | Identifier of the project to fetch logs for (required). |
| PlatformId | Identifier of the specific platform configuration within the project (required). |
| Filter by platform | Filter logs by platform type; options: telegram, discord. |
| Filter by log level | Filter logs by severity level; options: info, warn, error, debug. |
| Filter by log category | Filter logs by category; options: connection, webhook, message, error, auth, general. |
| Filter logs after this date | ISO 8601 formatted start date to filter logs occurring after this timestamp. |
| Filter logs before this date | ISO 8601 formatted end date to filter logs occurring before this timestamp. |
| Number of logs to return | Limit the number of logs returned; valid range is 1 to 1000; default is 100. |
| Number of logs to skip | Offset to skip a number of logs for pagination purposes. |
Output
The node outputs JSON data containing an array of log entries matching the specified filters. Each log entry typically includes details such as timestamp, platform, log level, category, message content, and possibly additional metadata relevant to the event logged.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node makes HTTP GET requests to endpoints under
/api/v1/projects/:slug/platforms/:platformId/logs. - Proper project slug and platform ID must be provided to access logs.
- The user must have appropriate permissions to read logs for the specified project and platform.
Troubleshooting
- Missing or invalid slug/platformId: The node requires both the project slug and platform ID. Omitting these or providing incorrect values will result in errors or empty responses.
- API authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid date formats: The
startDateandendDatemust be in ISO 8601 format; otherwise, the API may reject the request. - Limit and offset misuse: Setting limits outside the allowed range (1-1000) or negative offsets may cause errors.
- Empty results: If no logs match the filters, the output will be empty. Adjust filters or verify platform activity.
Links and References
- GateKit API Documentation (for detailed API endpoints and parameters)
- ISO 8601 Date Format (for correct date formatting)