PostNL icon

PostNL

Interact with PostNL API

Actions17

Overview

This node interacts with the PostNL API to retrieve updated shipping statuses filtered by a customer number within a specified time period. It is useful for logistics, e-commerce, or fulfillment workflows where you need to track shipment updates frequently and programmatically. For example, an online store could use this node to automatically fetch recent shipment status changes every 10 minutes to update order tracking information in their system.

Properties

Name Meaning
Customernumber Your unique customer number registered with the shipping service. This identifies which customer's shipments to query for updates.
Period 0 The start timestamp of the period to check for updated shipments. Must be in ISO format YYYY-MM-DDTHH:MM:SS. Defines the beginning of the time window for returned shipment updates.
Period 1 The end timestamp of the period to check for updated shipments. Must be in ISO format YYYY-MM-DDTHH:MM:SS. Defines the end of the time window for returned shipment updates.

Note: The two period properties together define a maximum 2-hour window for querying shipment updates. Scheduling calls every 5-15 minutes and adjusting these periods accordingly ensures no updates are missed.

Output

The node outputs JSON data containing the updated shipment statuses for the given customer number within the specified period. The structure typically includes shipment details such as tracking numbers, current status, timestamps of updates, and possibly other metadata related to each shipment's progress.

If binary data were involved (e.g., labels or documents), it would be summarized here, but this node focuses on JSON shipment status data only.

Dependencies

  • Requires an API key credential for authenticating with the PostNL API.
  • Needs the base URL environment variable configured to point to the correct PostNL API endpoint.
  • Relies on the PostNL API being accessible and responsive.

Troubleshooting

  • Common issues:

    • Invalid or missing customer number will result in no data or errors.
    • Incorrectly formatted period timestamps can cause request failures.
    • Requesting a period longer than 2 hours may lead to API errors or truncated results.
    • Network or authentication errors if API credentials or environment variables are misconfigured.

  • Error messages:

    • Authentication errors indicate invalid or missing API credentials; verify and re-enter them.
    • Validation errors about period format require ensuring timestamps follow the exact ISO format.
    • Rate limiting or quota exceeded errors suggest reducing call frequency or checking API usage limits.

Links and References

Discussion