Overview
This node integrates with the FedEx API to perform address validation, specifically resolving and verifying postal addresses. It is useful in scenarios where you need to ensure that shipping or billing addresses are accurate and standardized before processing orders or shipments. For example, an e-commerce workflow can use this node to validate customer addresses to reduce delivery errors and improve logistics efficiency.
The "Resolve" operation under the "Address Validation" resource takes input address components and returns a validated and standardized address.
Properties
| Name | Meaning |
|---|---|
| Street Line 1 | The first line of the street address (required). Can be a static string or an expression. |
| Street Line 2 | The second line of the street address (optional). Can be a static string or an expression. |
| Street Line 3 | The third line of the street address (optional). Can be a static string or an expression. |
| City | The city name of the address (required). Can be a static string or an expression. |
| State Code | Two-letter ISO state abbreviation code (required). Can be a static string or an expression. |
| Postal Code | Zip or postal code (required). Can be a static string or an expression. |
| Country Code | Two-letter ISO country code (required, default "US"). Can be a static string or expression. |
Output
The node outputs JSON data containing the resolved and validated address details returned by the FedEx API. This typically includes standardized address lines, city, state, postal code, country, and possibly additional metadata such as delivery point validation status or geocoding information.
If the node supports binary output (not indicated explicitly here), it would likely relate to any document or label generation related to the address, but based on the provided code and properties, the primary output is structured JSON with address validation results.
Dependencies
- Requires an active FedEx API key credential configured in n8n for authentication.
- Depends on the FedEx Address Validation API endpoint.
- Uses internal logging utilities for verbose output during execution.
Troubleshooting
- Missing Required Fields: Ensure all required fields (Street Line 1, City, State Code, Postal Code, Country Code) are provided; otherwise, the API call will fail.
- Invalid API Credentials: Authentication errors may occur if the FedEx API key is missing or invalid. Verify credentials in n8n settings.
- Incorrect Address Format: If the address components do not conform to expected formats (e.g., invalid state or country codes), the API may return errors or no matches.
- Network Issues: Connectivity problems can cause timeouts or failures when calling the FedEx API.
- Error Messages: Common error messages from the FedEx API might include invalid address, unauthorized access, or quota exceeded. Review the message details and adjust inputs or credentials accordingly.
Links and References
- FedEx Developer Portal
- FedEx Address Validation API Documentation
- n8n Expressions Documentation (for using expressions in property values)