fulfillmenttools icon

fulfillmenttools

Consume fulfillmenttools API

Actions12

Overview

This node integrates with the Fulfillmenttools API to manage facilities within a fulfillment or logistics system. Specifically, the "Facility - Create" operation allows users to create a new facility by providing detailed information about it, such as address, contact details, operational parameters, and services offered.

Common scenarios where this node is beneficial include:

  • Automating the onboarding of new warehouse or store locations into a fulfillment platform.
  • Centralizing facility data management in workflows that coordinate inventory, shipping, or order processing.
  • Integrating facility creation as part of larger supply chain automation pipelines.

For example, a logistics company can use this node to programmatically add new distribution centers with all relevant metadata, enabling downstream processes like order routing and capacity planning.

Properties

Name Meaning
Facility A JSON object representing the facility to be created. It includes comprehensive details such as:
- address: street, city, postal code, country, phone numbers, email addresses, and additional info.
- closingDays: dates and reasons for facility closures.
- contact: contact person details including name and role.
- customAttributes: any custom key-value pairs.
- fulfillmentProcessBuffer: buffer time in minutes.
- locationType: type of location (e.g., STORE).
- name: facility name.
- capacityPlanningTimeframe: timeframe for capacity planning.
- pickingTimes: daily picking schedules with start/end times and capacities.
- pickingMethods: methods used for picking orders (e.g., SINGLE_ORDER).
- scanningRule: rules for scanning items.
- services: services provided by the facility (e.g., SHIP_FROM_STORE).
- status: operational status (e.g., ONLINE).
- tenantFacilityId: external identifier.
- capacityEnabled: boolean flag for capacity control.
- tags: tags associated with the facility.

Output

The output JSON contains the response from the Fulfillmenttools API after creating the facility. This typically includes the full representation of the newly created facility resource, confirming the stored data and possibly including generated IDs or timestamps.

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 API endpoints.

Troubleshooting

  • Invalid or incomplete facility data: If required fields are missing or malformed in the facility JSON, the API may return validation errors. Ensure all mandatory fields like address, name, and status are correctly set.
  • Authentication errors: Failure to provide valid API credentials will result in authorization errors. Verify that the API key/token is correctly configured in n8n.
  • Network issues: Connectivity problems can cause request failures. Check network access and API endpoint availability.
  • API rate limits: Excessive requests might trigger rate limiting; consider adding delays or retries.
  • Error messages returned by the node will include the API error message in the error field if "Continue On Fail" is enabled, helping diagnose issues.

Links and References

Discussion