Actions12
Overview
This node integrates with the Fulfillmenttools API to manage connections between facilities and carriers. Specifically, the Facility Carrier - Connect operation establishes or updates a connection between a given facility and a carrier by sending detailed configuration data.
Typical use cases include:
- Linking a warehouse or fulfillment center (facility) with a shipping carrier to enable parcel handling.
- Updating carrier-specific settings for a facility, such as billing numbers, contact information, delivery areas, and parcel label classifications.
- Automating the setup of shipping configurations in logistics workflows.
For example, you might use this node to connect your "DHL Köln" facility with the DHL carrier, providing all necessary credentials and configuration details so that orders can be shipped through DHL from that facility.
Properties
| Name | Meaning |
|---|---|
| Facility ID | The unique identifier of the facility you want to connect or patch with a carrier. |
| Carrier Ref | The identifier of the carrier to which the facility will be connected. |
| Locale | Optional locale string to specify localized names and descriptions for parcel label classifications. |
| Facility | A JSON object representing the full configuration of the facility-carrier connection, including: |
| - Credentials (API keys, billing numbers, user credentials) | |
| - Configuration details (contact IDs, return contacts) | |
| - Cutoff time for processing shipments | |
| - Delivery areas (country and postal codes) | |
| - Facility name and status | |
| - Parcel label classifications with localized names and dimensions | |
| - Tags and versioning | |
| - Valid delivery targets (e.g., SHIP_TO_STORE) |
Output
The node outputs a JSON object representing the response from the Fulfillmenttools API after attempting to connect the specified facility with the carrier. This typically includes the updated or created facility-carrier connection details reflecting the submitted configuration.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Fulfillmenttools API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to the Fulfillmenttools REST endpoints.
Troubleshooting
Common issues:
- Invalid or missing Facility ID or Carrier Ref parameters will cause the API request to fail.
- Incorrectly formatted JSON in the Facility property may lead to validation errors.
- Authentication failures if the API key credential is not set up correctly.
- Network connectivity problems preventing access to the Fulfillmenttools API.
Error messages:
- Errors returned from the API will be passed through; typical messages might indicate missing required fields or invalid values.
- If the node throws an error about authorization, verify that the API key credential is valid and has sufficient permissions.
- Validation errors on the Facility JSON usually require checking the structure and required fields against the API documentation.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to process subsequent items even if one fails.
Links and References
- Fulfillmenttools API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node