Jadlog

Overview

This node allows users to track a shipment using the Jadlog courier service by providing a shipment tracking number. It fetches and parses tracking information from Jadlog's public tracking webpage, extracting details such as event dates, origins, statuses, destinations, and related documents for the shipment.

Common scenarios include:

• Automatically retrieving the current status of a package during an automated workflow.
• Monitoring delivery progress and updating internal systems or notifying users based on shipment events.
• Integrating Jadlog shipment tracking into broader logistics or customer support processes.

Example use case: A user inputs a shipment tracking number, and the node returns a timeline of tracking events with timestamps and locations, enabling real-time shipment monitoring.

Properties

Output

The node outputs an array of JSON objects, each representing a tracking event extracted from the Jadlog tracking page. Each object contains:

• dateStr: The original date and time string of the event (e.g., "dd/mm/yyyy hh:mm").
• origin: The location where the event occurred.
• status: The status description of the shipment at that event.
• destination: The destination location related to the event.
• document: Any associated document or reference number.
• date: A JavaScript Date object parsed from the dateStr for easier date manipulation.

No binary data is output by this node.

Dependencies

• The node depends on internet access to make HTTP GET requests to Jadlog's public tracking URL.
• It uses the cheerio library to parse HTML responses and extract tracking data.
• Requires an active network connection and no special API keys or authentication tokens.

Troubleshooting

• Empty or incomplete results: If the tracking number is invalid or not found, the node may return an empty array. Verify the tracking number format and correctness.
• HTTP request failures: Network issues or changes in Jadlog's website structure can cause errors or empty responses. Check connectivity and consider updating the node if the site layout changes.
• Parsing errors: If Jadlog modifies their HTML structure, the parsing logic may fail silently, resulting in missing data. In such cases, review and update the CSS selectors used for scraping.
• Unhandled exceptions: The node logs errors to the console but does not throw them further. Users should monitor execution logs for troubleshooting.

Links and References

• Jadlog Official Website
• Cheerio GitHub Repository - Used for HTML parsing in this node.