Actions12
Overview
The node integrates with the Shipentegra API to find cargo activities based on a provided tracking number. It is useful for logistics and shipping workflows where users need to track the status or history of cargo shipments. For example, a user can input a shipment's tracking number to retrieve detailed activity logs such as transit updates, delivery attempts, or customs clearance events.
Properties
| Name | Meaning |
|---|---|
| Tracking Number | The unique identifier used to track a specific cargo shipment. This is required to query the cargo activities associated with that shipment. |
Output
The node outputs JSON data containing the cargo activities related to the specified tracking number. This typically includes an array or list of activity records detailing events in the shipment lifecycle (e.g., pickup, transit, delivery). The exact structure depends on the Shipentegra API response but generally provides timestamps, locations, and status descriptions for each activity.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the Shipentegra API.
- The base URL for API requests is
https://publicapi.shipentegra.com/v1. - The node expects JSON responses and sends requests with appropriate headers including content type and language preferences.
Troubleshooting
- Missing or invalid tracking number: The node requires a valid tracking number; ensure this property is set correctly.
- Authentication errors: Verify that the API key credential is configured properly and has necessary permissions.
- API connectivity issues: Network problems or incorrect base URL configuration may cause failures.
- Unexpected API responses: If the API changes or returns errors, check the Shipentegra API documentation and update the node or credentials accordingly.
Links and References
- Shipentegra API Documentation (for detailed API endpoints and response formats)
- General n8n documentation on Using API Credentials