Peliqan icon

Peliqan

Get data from Peliqan
Join our community

Actions8

Overview

The node named "Peliqan" is designed to interact with the Peliqan service, which appears to be a data platform accessible via API. Specifically, for the Resource "Query" and Operation "Create SQL Query," this node allows users to create new SQL queries within the Peliqan environment. This can be useful in scenarios where you want to programmatically define and store SQL queries for later execution or integration into data pipelines.

Practical examples include:

  • Automating the creation of reusable SQL queries in Peliqan as part of a data workflow.
  • Managing query definitions centrally through n8n workflows.
  • Integrating SQL query creation with other automated tasks such as data ingestion or transformation.

Properties

Name Meaning
Query Name The name to assign to the new SQL query being created.
SQL Query (View) The actual SQL statement text that defines the query, e.g., SELECT * FROM my_table;.

Output

The node outputs JSON data representing the result of the query creation operation in Peliqan. This typically includes metadata about the newly created query such as its identifier, name, and possibly status or timestamps. The exact structure depends on the Peliqan API response but generally confirms successful creation and provides details for further use.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Peliqan service.
  • The node communicates with the Peliqan API at the base URL: https://app.eu.peliqan.io/.
  • Proper configuration of the API authentication credential in n8n is necessary.
  • The node uses JSON content type headers for requests.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Invalid SQL syntax: The SQL query string must be valid according to Peliqan's SQL dialect; otherwise, the API may reject it.
  • Missing required properties: Both "Query Name" and "SQL Query (View)" are mandatory; omitting them will cause errors.
  • Network issues: Verify connectivity to https://app.eu.peliqan.io/ and that no firewall or proxy blocks the request.

Common error messages might include authentication failures, validation errors from the API regarding the SQL query, or HTTP errors indicating connectivity problems.

Links and References

  • Peliqan Official Website (for general product info)
  • Peliqan API documentation (not provided in source, check official docs for detailed API usage)
  • n8n Documentation on creating custom nodes and using credentials

Note: The provided source code delegates execution logic to a router method and imports resource descriptions, so the detailed internal API call handling is abstracted away. The summary is based on static analysis of the node’s declared properties and structure.

Discussion