GainiumInstall

Overview

This node interacts with the Gainium API to retrieve and manage various types of trading bots, specifically including combo bots under the "Bots" resource. The "Get User Combo Bots" operation fetches a list of combo bots associated with the user, filtered by status and optionally paginated or returned in full.

Typical use cases include:

• Monitoring all combo bots currently active or archived in a user's Gainium account.
• Integrating bot data into workflows for reporting or further automated decision-making.
• Filtering bots by their operational status (e.g., open, closed, error) to focus on relevant subsets.

For example, a trader might use this node to automatically fetch all open combo bots running in paper trading mode to analyze their performance or adjust strategies accordingly.

Properties

Output

The output JSON contains a data field which holds the retrieved combo bots information. Depending on the API response structure, this can be:

• An object with a result array containing the bots and a totalResults count.
• Or an object with items array and itemsCount count.

Example output structure:

{
  "data": {
    "result": [
      {
        "botId": "string",
        "name": "string",
        "status": "open",
        "otherBotDetails": "..."
      }
    ],
    "totalResults": 10
  }
}

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Gainium API.
• The node uses HMAC SHA-256 signing for request authentication.
• Network access to the Gainium API base URL configured in credentials.
• No additional external dependencies beyond standard n8n HTTP request helpers.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect status filter values may result in empty responses.
  • Pagination parameters misconfiguration can lead to incomplete data retrieval.
  • If the API returns an error status, the node throws an error with the reason message.

• Error messages:

  • "Error: <reason>" — Indicates an API-level error; check the reason for specifics.
  • "HMAC generation failed: Web Crypto API not available" — Occurs if the environment does not support required cryptographic functions.
  • "Invalid JSON in filterModel" — Relevant for other operations using JSON input; ensure valid JSON syntax.

• Resolutions:

  • Verify API credentials and permissions.
  • Use supported status options exactly as listed.
  • Enable "Return All" to avoid manual pagination unless specific pages are needed.
  • Ensure the runtime environment supports Web Crypto API (modern Node.js versions).

Links and References

• Gainium Official API Documentation (user should consult for detailed request/response formats)
• n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)
• Web Crypto API - MDN (for HMAC signing details)