Overview
The "Jupiter Recurring" node integrates with the Jupiter Recurring API to manage recurring cryptocurrency orders and transactions. It supports creating, canceling, executing signed transactions, retrieving active or historical recurring orders, and handling price-based deposits and withdrawals.
This node is useful for automating and managing scheduled or conditional crypto trades on the Jupiter platform. For example, users can create recurring buy/sell orders based on time intervals or price triggers, execute signed transactions securely, or query their order history programmatically.
Practical scenarios include:
- Automatically placing recurring token swap orders at fixed time intervals.
- Executing pre-signed transactions as part of a workflow.
- Canceling unwanted recurring orders.
- Depositing or withdrawing funds related to price-based recurring orders.
- Fetching active or past recurring orders for reporting or monitoring.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL endpoint for the Jupiter Recurring API (default: https://lite-api.jup.ag/recurring/v1). |
| Recurring Type | Type of recurring order; options are time (time-based) or price (price-based). |
| Signed Transaction | Base64 encoded signed transaction string to be executed (required for Execute operation). |
| Request ID | Request ID obtained from a previous createOrder or cancelOrder response (required for Execute). |
| Operation | The action to perform: createOrder, cancelOrder, execute, getRecurringOrders, priceDeposit, or priceWithdraw. |
| Input Mint | Token mint address for input token (required for createOrder, cancelOrder, priceDeposit, priceWithdraw). |
| Output Mint | Token mint address for output token (required for createOrder, cancelOrder, priceDeposit, priceWithdraw). |
| Amount | Amount in smallest unit (lamports/atoms) for the order or deposit/withdrawal (required for createOrder, priceDeposit, priceWithdraw). |
| Maker | Wallet address of the maker involved in the order or transaction (required for createOrder, cancelOrder, priceDeposit, priceWithdraw). |
| Slippage BPS | Slippage tolerance in basis points (default 50), used when creating an order. |
| Order ID | Optional order ID for cancel operations. |
| Account | Account address to retrieve recurring orders for (required for getRecurringOrders). |
| Order Type | Type of orders to retrieve: active or historical (used with getRecurringOrders). |
Output
The node outputs JSON data corresponding to the response from the Jupiter Recurring API for the selected operation. The structure varies depending on the operation:
- createOrder: Details of the newly created recurring order.
- cancelOrder: Confirmation or status of the canceled order.
- execute: Result of executing the signed transaction.
- getRecurringOrders: List of active or historical recurring orders for the specified account.
- priceDeposit / priceWithdraw: Details of the deposit or withdrawal transaction created.
Each output item is paired with its input item index for traceability.
The node does not output binary data.
Dependencies
- Requires access to the Jupiter Recurring API endpoint.
- Optionally uses an API key credential for authentication, which should be configured in n8n credentials and passed via the
x-api-keyHTTP header. - No other external dependencies.
Troubleshooting
- Unknown operation error: Occurs if an unsupported operation value is provided. Ensure the operation property is set correctly.
- HTTP request failures: Network issues or invalid API keys may cause request errors. Verify network connectivity and that the API key credential is valid.
- Missing required parameters: Some operations require specific properties (e.g., signedTransaction and requestId for execute). Make sure all required inputs are provided.
- API rate limits or server errors: If the API returns errors, check the API provider's status and usage limits.
To resolve errors, review the error message returned in the node output or thrown exception, verify input parameters, and confirm API credentials.
Links and References
- Jupiter Recurring API Documentation (general Jupiter API docs; specific recurring API docs may be available there)
- n8n HTTP Request Node Documentation (for understanding HTTP requests in n8n)