Peliqan icon

Peliqan

Get data from Peliqan
Join our community

Actions8

Overview

This node integrates with the Peliqan platform, allowing users to fetch and manipulate data related to various Peliqan resources such as endpoints, pipelines, queries, scripts, and tables. Specifically, when using the Script resource with the Logs operation, the node retrieves logs associated with a particular script execution identified by an ID.

Common scenarios for this node include:

  • Debugging or monitoring script executions by fetching their logs.
  • Automating workflows that depend on script output or status.
  • Integrating Peliqan script logs into broader data processing pipelines within n8n.

For example, a user might want to automatically retrieve logs from a specific script run to analyze errors or performance metrics and then trigger alerts or further processing based on those logs.

Properties

Name Meaning
ID The unique identifier of the script run whose logs you want to fetch. This is a required string input.

Output

The node outputs JSON data containing the logs fetched for the specified script run ID. The exact structure of the JSON depends on the Peliqan API response but generally includes log entries, timestamps, and possibly metadata about the script execution.

If the node supports binary data output (not indicated in the provided code), it would typically represent raw log files or attachments; however, no binary output is evident here.

Dependencies

  • Requires an active connection to the Peliqan platform via an API key credential.
  • The node uses the base URL https://app.eu.peliqan.io/ for API requests.
  • Proper configuration of the API authentication token in n8n credentials is necessary.
  • No additional external dependencies are indicated beyond the Peliqan API.

Troubleshooting

  • Missing or invalid ID: If the "ID" property is empty or incorrect, the node will fail to fetch logs. Ensure the correct script run ID is provided.
  • Authentication errors: If the API key credential is missing or invalid, the node will not connect to Peliqan. Verify the API key setup.
  • Network issues: Connectivity problems to https://app.eu.peliqan.io/ can cause request failures.
  • API rate limits or permissions: Insufficient permissions or hitting API rate limits may result in errors. Check your Peliqan account settings.

Common error messages might include unauthorized access, resource not found, or timeout errors. Resolving these typically involves verifying credentials, ensuring the script run ID exists, and checking network connectivity.

Links and References

Discussion