Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Shipping and fulfillment → Create Fulfillment
AI-generatedOverview
This node integrates with the Haravan platform to handle various resources and operations related to e-commerce activities such as orders, products, accounts, and specifically shipping and fulfillment. The "Create Fulfillment" operation under the "Shipping and fulfillment" resource allows users to create fulfillment records for orders, which is essential for managing order shipment processes.
Typical use cases include automating the creation of shipment fulfillments when an order is ready to be shipped, updating fulfillment status in real-time, or integrating with external logistics providers. For example, after an order is paid, this node can automatically trigger a fulfillment creation to notify the warehouse or shipping service.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional fields to customize the request behavior. |
| - Logging Request | Boolean option to enable logging of each API request sent to Haravan for debugging purposes. |
The node supports additional properties defined elsewhere (not fully shown here), but for the "Create Fulfillment" operation, the main customizable input is the "Options" collection with the "Logging Request" boolean flag.
Output
The node outputs an array of JSON objects representing the results of the executed operations. Each output item contains metadata about the execution, including:
executionId: Unique identifier for the current execution.resource: The resource type being operated on (e.g., "Shipping and fulfillment").operation: The operation performed (e.g., "Create Fulfillment").status: Status of the operation, typically"completed"if successful.timestamp: ISO string timestamp of when the operation was processed.
If multiple items are processed, the output will be an array of such result objects. The node does not explicitly output binary data.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- Depends on the Haravan API accessible via network.
- No other external dependencies are indicated.
- The node expects proper configuration of credentials within n8n to communicate with Haravan.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity problems preventing access to Haravan API.
- Incorrect resource or operation parameters leading to unexpected results or errors.
Error Messages:
- Errors thrown during execution will include the item index causing the failure.
- If "continue on fail" is disabled, the node stops at the first error; enabling it allows processing remaining items.
- Enabling the "Logging Request" option can help debug by providing detailed logs of API requests.
Resolution Tips:
- Verify API credentials and permissions.
- Check network connectivity and API endpoint availability.
- Use the logging option to inspect request payloads and responses.
- Ensure input data matches expected formats for the selected resource and operation.