Actions12
Overview
This node interacts with the Fulfillmenttools API to manage facility carriers associated with specific facilities. The Facility Carrier: Get operation retrieves detailed information about a particular carrier linked to a given facility. This is useful when you need to fetch carrier-specific data such as shipping options, classifications, or localized descriptions for a parcel label within a facility's context.
Common scenarios:
- Retrieving carrier details to display or process shipping options for orders fulfilled from a specific facility.
- Accessing localized carrier information to support multi-language user interfaces.
- Verifying carrier references and their configurations before creating or updating shipments.
Example:
You have a warehouse (facility) and want to get details about a specific carrier used there, including localized names and descriptions for labels, to present accurate shipping choices in your order management system.
Properties
| Name | Meaning |
|---|---|
| Facility ID | The unique identifier of the facility from which you want to retrieve the carrier information. |
| Carrier Ref | The unique identifier/reference of the carrier associated with the facility. |
| Locale | Optional parameter specifying the locale/language for localized names and descriptions of parcel label classifications. |
Output
The output JSON contains the detailed information of the requested facility carrier as returned by the Fulfillmenttools API. This typically includes:
- Carrier identifiers and references.
- Configuration details related to the carrier at the specified facility.
- Localized names and descriptions if the
localeparameter was provided. - Parcel label classifications and other metadata relevant to the carrier.
If the API supports binary data for this resource (not indicated here), it would be summarized as representing any files or attachments related to the carrier.
Dependencies
- Requires an active connection to the Fulfillmenttools API via an API key credential configured in n8n.
- The node depends on internal helper functions (
fulfillmenttoolsApiRequest) to make authenticated HTTP requests to the Fulfillmenttools REST endpoints. - No additional external services are required beyond the Fulfillmenttools API.
Troubleshooting
- Missing or invalid Facility ID or Carrier Ref: The API call will fail if either identifier is missing or incorrect. Ensure these IDs are valid and correspond to existing resources in your Fulfillmenttools account.
- Locale issues: Providing an unsupported locale may result in default language responses or errors. Verify supported locales with Fulfillmenttools documentation.
- API authentication errors: If the API key credential is not set up correctly or has expired, requests will fail with authentication errors. Reconfigure or renew the API key in n8n credentials.
- Network or connectivity problems: Ensure that n8n can reach the Fulfillmenttools API endpoint without firewall or proxy restrictions.
Links and References
- Fulfillmenttools API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes (for understanding node development concepts)