Overview
This node, named "PickerPro Trigger," is designed to listen for events from the PickerPro service. It acts as a webhook trigger that activates when specific PickerPro events occur, such as new or updated customers, orders, inventory changes, and more. This node is useful in automation workflows where you want to react immediately to changes or updates within the PickerPro system, enabling real-time integrations with other services or internal processes.
Practical examples include:
- Automatically updating a CRM when a new customer is added or updated.
- Syncing inventory adjustments or movements with an external warehouse management system.
- Triggering notifications or downstream workflows when new orders or purchases are created.
Properties
Name | Meaning |
---|---|
Trigger On | Select which PickerPro events should trigger this node. Options include: |
- All Events (trigger on all event types) | |
- Customers (new or updated customers) | |
- Inventory Adjustments (new or updated inventory adjustments) | |
- Inventory Movements (new or updated inventory movements) | |
- Inventory Transfers (new or updated inventory transfers) | |
- Locations (new or updated locations) | |
- Orders (new or updated orders) | |
- Pickings (new or updated pickings) | |
- Products (new or updated products) | |
- Purchases (new or updated purchases) | |
- Routes (new or updated routes) | |
- Suppliers (new or updated suppliers) | |
- Users (new or updated users) | |
- Warehouses (new or updated warehouses) | |
- Zones (new or updated zones) |
Output
The node outputs JSON data containing information about the webhook execution status. The typical output structure includes:
{
"success": true,
"message": "Webhook executed successfully"
}
When the webhook is triggered by an incoming event, the node attempts to register the webhook URLs with PickerPro's API and returns a success message along with the received event body:
{
"success": true,
"message": "Webhook registered successfully",
"body": { /* event data from PickerPro */ }
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential and an organization ID credential for authenticating with the PickerPro API.
- Needs network access to PickerPro's webhook subscription endpoint (
https://api.pickerpro.services/v1.0.0/webhook/n8n/subscribe
). - The node verifies that the server IP address is not localhost; it must be a public or private IP address accessible by PickerPro.
- The node uses n8n's webhook mechanism to receive PickerPro events.
Troubleshooting
- API Key or Organization ID Not Configured: If these credentials are missing or invalid, the node will throw an error indicating they are not configured. Ensure valid credentials are set up in n8n.
- IP Address is Localhost: The node checks the server's IP address and throws an error if it resolves to
localhost
. This means the webhook URL is not publicly reachable. Use a publicly accessible IP or domain. - Invalid Trigger Selection: Selecting "All Events" together with other specific events causes an error. Only select "All Events" alone or specific event types exclusively.
- Webhook Registration Failure: If the node cannot register the webhook with PickerPro, it throws an error. Check network connectivity, API credentials, and PickerPro service status.
- No Valid Webhook Body Received: If the webhook receives no or invalid data, it returns an empty JSON object without triggering downstream actions.
Links and References
- PickerPro API documentation (not provided in code, but typically available from PickerPro)
- n8n Webhook Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/
- Node API Error Handling in n8n: https://docs.n8n.io/integrations/creating-nodes/node-api-error/