fulfillmenttools icon

fulfillmenttools

Consume fulfillmenttools API

Actions12

Overview

This node integrates with the Fulfillmenttools API to create new orders in a fulfillment system. It is designed to send detailed order data, including consumer information, ordered items, and payment details, to the API for processing.

Common scenarios where this node is beneficial include:

  • Automating order creation from an e-commerce platform or custom shop system.
  • Synchronizing orders between different sales channels and a centralized fulfillment backend.
  • Streamlining order management workflows by programmatically submitting orders for fulfillment.

Practical example:
You have an online store and want to automatically push each new customer order into your fulfillment provider's system. This node takes the complete order object (with customer address, line items, and payment info) and creates the order remotely via the API.

Properties

Name Meaning
Order The full order object to be created in the fulfillment system. This JSON includes:
- orderDate: Date/time of the order.
- consumer: Customer details including email and addresses.
- tenantOrderId: Unique order identifier.
- status: Order status (e.g., "OPEN").
- orderLineItems: Array of ordered products with quantity and product attributes.
- paymentInfo: Payment-related information such as currency.

Users must supply a valid JSON structure representing the order as expected by the API.

Output

The node outputs the JSON response returned by the Fulfillmenttools API after creating the order. This typically contains the created order's details, confirmation, or any metadata provided by the API.

  • The output is a JSON array where each item corresponds to an input item processed.
  • Each item's json field holds the API response for that order creation request.
  • No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Fulfillmenttools API.
  • Users must configure an API authentication credential (such as an API key) within n8n to authorize requests.
  • The node uses internal helper functions to make HTTP POST requests to the /orders endpoint of the Fulfillmenttools API.

Troubleshooting

  • Invalid Order JSON: If the supplied order JSON is malformed or missing required fields, the API may return validation errors. Ensure the order object matches the expected schema.
  • Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify the configured API key or token.
  • Network Issues: Connectivity problems can prevent successful API calls. Check network access and proxy settings if applicable.
  • API Rate Limits: Excessive requests might trigger rate limiting. Implement retry logic or reduce request frequency.
  • Error Handling: If the node is set to continue on failure, error messages from the API will appear in the output under an error property for the respective item.

Links and References

Discussion