Overview
This node integrates with the Jupiter Trigger API to manage trigger orders related to token swaps or trades. It supports operations such as creating a new trigger order, canceling one or multiple existing orders, executing signed transactions, and retrieving active or historical trigger orders.
Typical use cases include:
- Automatically placing conditional token swap orders that execute when a specified price condition is met.
- Canceling pending trigger orders by their IDs.
- Executing pre-signed transactions on demand.
- Querying the status of trigger orders for a given account.
For example, a user might create a trigger order to swap tokens only if the price rises above a certain threshold, then later cancel that order if market conditions change.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL for the Jupiter Trigger API (default: https://lite-api.jup.ag/trigger/v1). |
| Maker | Wallet address of the maker placing or canceling the order. |
| Order ID | Specific order ID to cancel (optional). |
These properties are relevant specifically for the Cancel Order operation.
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output object contains the raw JSON response from the Jupiter Trigger API for the cancel order request.
The structure depends on the API response but generally includes confirmation of the canceled order or error details if cancellation failed.
No binary data is produced by this operation.
Dependencies
- Requires access to the Jupiter Trigger API endpoint.
- Optionally uses an API key credential for authentication, which should be configured in n8n credentials and passed via an HTTP header (
x-api-key). - No other external dependencies.
Troubleshooting
Common issues:
- Invalid or missing maker wallet address will cause the API to reject the request.
- Providing an incorrect or non-existent order ID may result in failure to cancel the order.
- Network or authentication errors if the API key is invalid or missing.
Error messages:
"Unknown operation: cancelOrder"— indicates the operation parameter was not set correctly; ensure "Cancel Order" is selected.- API errors returned in the JSON response will be passed through; check the message for details.
- If the node throws an error about missing parameters, verify all required fields are filled.
To resolve errors, confirm all required inputs are correct, the API key credential is valid, and the network connection to the API endpoint is stable.
Links and References
- Jupiter Trigger API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n.