I just built a new n8n automation templateusing our new Gainium n8n community node integration to help you deploy hedge strategies faster and more reliably. It’s modular, easy to tweak, and includes 3 main components:
1. The Chat
This is your control panel. It lets you:
Start a new strategy for any token by adding the first base order to the base tracker.
Replenish base using the add funds function when your base dips.
Clone long and short templates to start the hedge strategy for that token automatically.
Think of this as your manual trigger zone for one-off or new pair deployments.
2. The Pairs List
This is the automation powerhouse.
Drop in a list of token pairs.
The template will automatically run all 3 actions for each pair: add base, fund, and start hedge.
Useful for scaling across multiple tokens without doing it one by one.
Set it and let it run across the board.
3. The Profit Tracker
This is a scheduled task that:
Queries available (free) USDT daily on both the long and short exchanges.
Tracks your capital allocation and helps measure strategy performance over time.
Great for visibility without needing to log in and check manually.
429 is a rate limit error, we have a limit of 60 requests per minute. In the response headers you should be able to see left requests and timestamp when the limits will reset.
May I ask you how requests are count? is it every action sent to Gainium from an external resource or also those actions performed internally by gainium inside gainium (for example any running bots actions)? thanks
Yes a wait node should be added to avoid rate limits, also it needs a wait of 1 second after adding the pair and starting a deal, as I’ve encountered that without that little delay it may try to open the deal before the bot has finished saving the new pair. I will post an updated version of the workflow soon.
Yes I also added a log report which basically sits at the end of the task before looping - it just tells you what bots have been duplicated and what coins have been bought.
I added this because sometimes it just stops either because you click somewhere or because of the connection breaks - then you can look at the log and restart from where it left