Actions108
- AI Actions
- Transcribe
- Detect Brand
- Extract Contact Information
- Mood Detection
- Detect Adult Content
- Enitity Detection
- Language Detection
- Too Long To Read
- Check Content Policy
- Detect Faces
- Generate Python Code
- Picture Text Recognition
- Detect Color
- Generate Image
- PDF OCR
- Translation
- Detect Email Type
- Generate Javascript Code
- Picture Object Recognition
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Date & Time Actions
- Generate Actions
- Image Actions
- Operator Actions
- PDF Actions
- Storage Actions
- Text Actions
- User Actions
Overview
This node provides a currency conversion utility within the "Convert" resource and the "Convert Currency" operation. It allows users to convert a specified amount from one currency to another, optionally formatting the date of the conversion result.
Common scenarios where this node is beneficial include:
- Financial applications needing real-time or historical currency conversions.
- E-commerce platforms calculating prices in different currencies.
- Reporting tools that require currency normalization for multi-currency data.
For example, converting 100 USD to EUR on a specific date or converting an amount from GBP to JPY dynamically during workflow execution.
Properties
| Name | Meaning |
|---|---|
| Amount | The numeric amount of money to convert. Must be at least 0.01. |
| Source Currency | The currency code of the original amount. Options include standard ISO currency codes like USD, EUR, GBP, JPY, etc. |
| Target Currency | The currency code into which the amount should be converted. Same options as Source Currency. |
| Date Format | Optional string specifying the format in which the conversion date should be returned (e.g., YYYY-MM-DD). |
Additionally, there is a property group called Code Variables allowing users to define variables by name or ID with associated values, which can be used in custom code contexts but is not directly related to the currency conversion operation.
Output
The output is a JSON array containing the conversion result(s). Each item typically includes fields such as the converted amount and possibly metadata about the conversion (e.g., date formatted according to the provided Date Format).
If binary data were involved, it would be summarized here, but this operation deals only with JSON data representing currency conversion results.
Dependencies
- Requires an API key credential for authentication with the external service providing currency conversion rates.
- The node internally calls an API endpoint under the path
convert/currencywith parameters including amount, source currency, target currency, and optional date format. - No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Invalid Currency Codes: Using unsupported or misspelled currency codes will likely cause errors. Ensure currency codes conform to standard ISO codes listed in the properties.
- Amount Validation: Amount must be a positive number greater than or equal to 0.01; otherwise, the request may fail.
- API Authentication Errors: Missing or invalid API credentials will prevent successful requests.
- Date Format Issues: Providing an incorrect date format string might lead to unexpected output or errors.
- Network or API Downtime: External API unavailability will cause the node to throw errors; retry or check API status.
To resolve errors, verify all input parameters, ensure valid API credentials are configured, and consult logs for detailed error messages.
Links and References
- ISO Currency Codes
- Date Formatting Patterns
- n8n Documentation on Expressions (for using dynamic variable IDs)
This summary is based solely on static analysis of the provided source code and property definitions.