Actions8
- Endpoint Actions
- Pipeline Actions
- Query Actions
- Script Actions
- Table Actions
Overview
This node, named "Peliqan," is designed to interact with the Peliqan API service. Specifically, when using the Endpoint resource with the Execute operation, it allows users to execute a predefined API endpoint within Peliqan. This is useful for scenarios where you want to trigger or retrieve data from specific API endpoints configured in Peliqan without manually crafting HTTP requests.
Practical examples include:
- Triggering a custom workflow or action defined in Peliqan.
- Fetching data or results from a particular API endpoint managed by Peliqan.
- Integrating Peliqan's API endpoints into an n8n automation flow seamlessly.
Properties
| Name | Meaning |
|---|---|
| API Endpoint Name or ID | Selects which Peliqan API endpoint to execute. You can choose from a list of available endpoints or specify an ID via expression. This determines the exact API call made. |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body with the request. |
| Custom Body | Optional JSON object to include as the request body if "Use Custom Body" is enabled. |
Output
The node outputs the response from the executed Peliqan API endpoint in the json field of the output data. The structure of this JSON depends on the specific endpoint called and the data returned by Peliqan. There is no explicit binary data output indicated.
Dependencies
- Requires an API key credential for authenticating with the Peliqan API.
- The base URL for requests is
https://app.eu.peliqan.io/. - The node expects JSON content type for both requests and responses.
- No additional external dependencies are indicated beyond the Peliqan API access.
Troubleshooting
Common issues:
- Selecting an invalid or non-existent API endpoint name or ID will likely cause errors.
- Providing malformed JSON in the "Custom Body" property may result in request failures.
- Missing or incorrect API authentication credentials will prevent successful API calls.
Error messages:
- Authentication errors typically indicate missing or invalid API keys; ensure credentials are correctly set up.
- Request errors due to invalid endpoint selection or bad request bodies should be resolved by verifying the selected endpoint and JSON syntax.
Links and References
- Peliqan API Documentation (general reference to the API base URL)
- n8n Expressions Documentation (for using expressions in properties)