Actions12
Overview
This node interacts with the Fulfillmenttools API to manage facilities, including deleting a facility by its ID. The "Delete Facility" operation removes a specified facility from the system. It is useful in scenarios where a facility is no longer needed or must be removed due to changes in logistics or business operations.
For example, if a warehouse or distribution center represented as a facility is closed or merged, this node can automate the deletion process within your workflow.
Properties
| Name | Meaning |
|---|---|
| Facility ID | The unique identifier of the facility you want to delete. This is required for the deletion. |
| Force Deletion | A boolean option to force cascading deletion without performing pre-condition checks. If true, related dependent data may also be deleted automatically. |
Output
The node outputs JSON data representing the response from the Fulfillmenttools API after attempting to delete the facility. Typically, this will include confirmation of deletion or details about the deleted resource. No binary data output is involved.
The output JSON structure depends on the API's response but generally confirms success or provides error information if the deletion failed.
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 DELETE requests to the
/facilities/{facilityId}endpoint of the Fulfillmenttools API.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Facility ID will result in an error from the API.
- Attempting to delete a facility that has dependencies without enabling "Force Deletion" might cause the operation to fail due to pre-condition checks.
- Network or authentication issues can prevent successful API calls.
Error Messages:
- Errors returned from the API typically include messages indicating why deletion failed (e.g., "Facility not found", "Cannot delete facility with active orders").
- To resolve, verify the Facility ID is correct, check if dependent resources exist, and consider enabling "Force Deletion" if appropriate.
- Ensure API credentials are valid and have sufficient permissions.
Links and References
- Fulfillmenttools API Documentation (general reference for API endpoints and behavior)
- n8n documentation on creating custom nodes for further customization guidance