Jupiter Trigger

Overview

The "Jupiter Trigger" node interacts with the Jupiter Trigger API to manage trigger orders related to token swaps or 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.

This node is beneficial in scenarios where automated trading or conditional token swaps are required on the Solana blockchain or similar environments. For example, a user can create an order that triggers a token swap when a certain price condition is met, cancel pending orders if market conditions change, or execute pre-signed transactions programmatically.

Practical examples:

• Automatically swapping tokens when the price of a token crosses above or below a specified threshold.
• Canceling multiple pending orders in bulk to quickly adjust trading strategies.
• Fetching all active or historical trigger orders for monitoring or reporting purposes.

Properties

Additional properties relevant to other operations (not requested but present):

• Operation: The action to perform (e.g., createOrder, cancelOrder, cancelOrders, execute, getTriggerOrders)
• Signed Transaction: Base64 encoded signed transaction (for execute operation)
• Request ID: Request ID from createOrder or cancelOrder response (for execute operation)
• Account: Account address to get orders for (for getTriggerOrders operation)
• Order Type: Type of orders to retrieve - Active or Historical (for getTriggerOrders operation)
• Input Mint: Input token mint address (for createOrder)
• Output Mint: Output token mint address (for createOrder)
• Amount: Amount in smallest unit (lamports/atoms) (for createOrder)
• Trigger Price: Price at which to trigger the order (for createOrder)
• Trigger Condition: Condition for triggering the order - Above or Below (for createOrder)
• Slippage BPS: Slippage in basis points (default 50) (for createOrder)
• Order ID: Specific order ID to cancel (optional, for cancelOrder)

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

• json: The parsed JSON response from the Jupiter Trigger API for the respective operation.
• If the operation fails and "Continue On Fail" is enabled, the output will contain an error message under json.error.

The structure of the JSON depends on the operation performed, e.g.:

• For cancelOrders: likely a confirmation or status object indicating which orders were canceled.
• For createOrder: details of the created order including identifiers.
• For getTriggerOrders: a list of orders matching the query.
• For execute: result of executing the signed transaction.

No binary data output is produced by this node.

Dependencies

• Requires access to the Jupiter Trigger API endpoint (default base URL: https://lite-api.jup.ag/trigger/v1).
• Optionally uses an API key credential for authentication, sent via the x-api-key HTTP header if provided.
• No other external dependencies are required.
• Network connectivity to the API endpoint is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing maker wallet address when required.
  • Incorrectly formatted order IDs string (should be comma-separated without extra spaces).
  • Missing required parameters for specific operations (e.g., missing signed transaction for execute).
  • Network errors or unreachable API endpoint.
  • Unauthorized errors if API key is invalid or missing when required.

• Error messages:

  • "Unknown operation: <operation>": Indicates an unsupported operation was selected; verify the operation name.
  • HTTP request failures will throw errors; enabling "Continue On Fail" allows processing subsequent items.
  • Validation errors from the API may appear in the response JSON; check parameter correctness.

• Resolutions:

  • Ensure all required fields are filled correctly.
  • Verify API key credentials if authentication is needed.
  • Confirm network access to the configured Base URL.
  • Use proper formatting for lists like order IDs.

Links and References

• Jupiter Trigger API Documentation (general reference for API endpoints and usage)
• n8n Documentation for general node usage and error handling guidance