Overview
The "Jupiter Trigger" node interacts with the Jupiter Trigger API to manage and execute trigger orders related to token transactions. It supports operations such as creating new trigger orders, canceling single or multiple orders, executing signed transactions, and retrieving active or historical trigger orders for a given account.
This node is beneficial in scenarios where automated trading or conditional token swaps are required on the Solana blockchain ecosystem, allowing users to programmatically manage their trigger orders based on price conditions.
Practical examples:
- Automatically create a trigger order to swap tokens when a certain price threshold is reached.
- Cancel one or more existing trigger orders if market conditions change.
- Execute a pre-signed transaction to finalize an order.
- Retrieve all active or historical trigger orders for monitoring or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the Jupiter Trigger API endpoint (default: https://lite-api.jup.ag/trigger/v1). |
| Signed Transaction | Base64 encoded signed transaction to be executed (required for the Execute operation). |
| Request ID | Request ID obtained from a previous createOrder or cancelOrder response (required for Execute). |
Output
The node outputs JSON data corresponding to the response from the Jupiter Trigger API for the selected operation. The structure varies depending on the operation:
- For Execute operation, the output JSON contains the result of executing the signed transaction, typically including success status or error details.
- For other operations (not requested here), the output would include details about created orders, canceled orders, or retrieved trigger orders.
No binary data output is produced by this node.
Dependencies
- Requires access to the Jupiter Trigger API, which may require an API key credential configured in n8n.
- Optionally uses an API key header (
x-api-key) if provided via credentials. - Network connectivity to the specified Base URL.
Troubleshooting
Common issues:
- Invalid or missing signed transaction or request ID will cause the Execute operation to fail.
- Incorrect Base URL or network issues can lead to connection errors.
- Missing or invalid API key may result in authorization errors.
Error messages:
"Unknown operation": Occurs if an unsupported operation is selected; ensure the operation is set to "Execute".- HTTP errors from the API will be returned as error messages in the node output if "Continue On Fail" is enabled.
Resolutions:
- Verify that the signed transaction is correctly base64 encoded.
- Ensure the request ID matches a valid order previously created or canceled.
- Confirm API key credentials are properly set up if required by the API.
- Check network connectivity and correct Base URL configuration.
Links and References
- Jupiter Aggregator Documentation (for general context on Jupiter services)
- Solana Token Program (for understanding token mint addresses and transactions)