Address Validation and Billbee Order Correction using Endereco - n8n Workflow

E-commerce businesses relying on Billbee for order management.
Automation specialists looking for robust n8n templates for logistics.
Users needing to implement external address validation (like Endereco) within their n8n environment.
Warehouse operations teams seeking to minimize shipping errors caused by incorrect addresses.

Managing high volumes of e-commerce orders often results in address errors, leading to shipping delays and manual intervention. This specialized n8n workflow solves this critical issue by integrating Billbee with the professional address validation service, Endereco. When a new order is imported into Billbee, the n8n trigger immediately initiates the validation process. The n8n node logic first standardizes the address data and performs complex checks, particularly for tricky house number formats. It then sends the information to Endereco. If Endereco suggests a correction, the workflow automatically applies the corrected address back to the Billbee order via a PATCH request, adding a success tag. If validation fails or requires manual review (e.g., complex address line 2 scenarios), the n8n workflow applies a corresponding error tag, ensuring full transparency in Billbee. This robust automation, built using standard n8n node types, drastically reduces manual work and improves shipping accuracy, making this one of the most useful n8n templates for logistics.

The entire process is initiated by an external event and flows through several key n8n node steps:

1. Start and Configuration (n8n Trigger): The n8n workflow begins with a Webhook n8n trigger, activated by Billbee upon order import, passing the OrderId. A subsequent Set n8n node (ConfigNode) collects this ID and sets up necessary API keys (Billbee Developer and Endereco).


2. Retrieve Data: An HTTP Request n8n node (get order data) uses the orderID to fetch detailed shipping information from the Billbee API.


3. Data Preparation: The data is processed using a Split Out n8n node and a Set n8n node (Set Address Fields) to extract and map the Billbee address fields into standardized formats (e.g., cleaning slashes from house numbers).


4. Filtering: A Filter n8n node (Filter Out PickUpShops) is used to skip address validation for known non-standard delivery locations (like German 'Packstation') that might fail standard API checks.


5. House Number Logic (Core Logic Flow Control): A series of If n8n nodes check for missing house numbers. If missing, the logic attempts to extract the number from AddressLine2. If extraction is ambiguous (number and letter combinations), a manual review tag (manualaddresscheck) is set in Billbee using an HTTP Request n8n node.


6. Address Validation: The prepared address is sent to the Endereco API via an HTTP Request n8n node (Check Address endereco api).


7. Conditional Update: An If n8n node (check if new address is not empty) evaluates the Endereco response.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Import this n8n workflow JSON into your n8n instance.


2. Billbee Setup (Trigger): Configure a new rule in your Billbee settings. Set the trigger event (e.g., 'Order imported'). The action should be 'Call External URL', pointing to your n8n webhook URL, including the Order ID parameter (e.g., YOURN8NWEBHOOK_LINK?Id={OrderId}).


3. Credentials: This n8n workflow requires two primary credentials:

1. Activation: Once credentials and keys are set in the n8n node configurations, activate the n8n workflow.

Webhook (n8n trigger): The starting point, receiving the OrderId from Billbee via a URL query parameter.
ConfigNode (Set n8n node): Stores the necessary API keys and extracts the orderID from the incoming n8n trigger data, making them accessible to downstream n8n nodes.
get order data (HTTP Request n8n node): Fetches comprehensive Billbee order details using the Billbee API, essential for obtaining the current shipping address data.
Set Address Fields (Set n8n node): Standardizes field names (e.g., Street, zip) and performs initial data cleanup, like removing potential characters from the house number field. This prepared data is crucial for the Endereco API n8n node call.
Filter Out PickUpShops (Filter n8n node): Uses logical checks to prevent the n8n workflow from processing certain types of addresses (like 'Packstation') that are often rejected by address validation services.
check if housenumer is not empty (If n8n node) / Nested If Logic: A complex set of If n8n nodes that implements core logic flow control to handle house number data augmentation, crucial for successful validation by the Endereco n8n node.
Check Address endereco api (HTTP Request n8n node): Submits the address data to Endereco's addressCheck method. This is the central address validation n8n node of the workflow.
set new delivery address to billbee (HTTP Request n8n node): Performs a PATCH request back to the Billbee API to update the shipping address with the corrected prediction data from Endereco.

• set billbee tag (HTTP Request n8n node): Adds status tags (enderecoaddressfailed or enderecoaddressvalidated) to the Billbee order, providing immediate feedback on the result of the n8n workflow execution.