FXCM

Overview

This node integrates with the FXCM trading platform to perform various trading and market data operations. Specifically, the "Modify Position" operation allows users to update an existing open position's stop loss and take profit levels. This is useful for traders who want to adjust risk management parameters on their trades without closing and reopening positions.

Common scenarios include:

• Adjusting stop loss or take profit after market conditions change.
• Managing open trades dynamically based on new analysis or strategy updates.

Example: A user has an open EUR/USD position and wants to increase the take profit level to capture more potential upside while tightening the stop loss to reduce risk.

Properties

Note: Only the "Instrument" property was provided explicitly. The code references additional properties like positionId, stopLoss, and takeProfit for the "modifyPosition" operation, which are required to identify and update the position.

Output

The node outputs a JSON object representing the result of the modification request. This typically includes details about the updated position such as its ID, updated stop loss and take profit values, and possibly status information confirming the successful update.

Example output structure (simplified):

{
  "positionId": "123456",
  "stopLoss": 1.1000,
  "takeProfit": 1.1500,
  "status": "modified"
}

No binary data output is involved in this operation.

Dependencies

• Requires an active FXCM API connection authenticated via an API key credential.
• The node depends on the FxcmClient class to communicate with the FXCM API.
• Proper configuration of the FXCM API credentials within n8n is necessary before use.

Troubleshooting

• Common issues:

  • Invalid or expired API credentials will cause authentication failures.
  • Providing an incorrect or non-existent positionId will result in errors when attempting to modify a position.
  • Omitting required parameters like positionId may cause the node to throw errors.

• Error messages:

  • Errors returned from the FXCM API (e.g., "Position not found") should be checked against the input parameters.
  • Network or connectivity issues may cause timeouts or failed requests.

• Resolutions:

  • Verify that the API credentials are correct and have sufficient permissions.
  • Double-check the positionId and ensure it corresponds to an open position.
  • Ensure all required parameters are provided and valid.
  • Use the node's "Continue On Fail" option to handle errors gracefully if desired.

Links and References

• FXCM API Documentation
• n8n Documentation on Creating Custom Nodes