Myparcelasia icon

Myparcelasia

Custom operations

Actions6

Overview

This node integrates with the Myparcelasia API to perform various parcel-related actions. Specifically, the Get Postcode operation allows users to look up details about a given postcode by sending a request to the Myparcelasia service.

Common scenarios where this node is beneficial include:

  • Validating or enriching address data in shipping workflows.
  • Automating logistics processes that require postcode verification.
  • Integrating postcode lookup into order fulfillment pipelines.

For example, an e-commerce workflow could use this node to verify customer postcodes before creating shipments, ensuring accurate delivery information.

Properties

Name Meaning
CJ Token The authentication token required to access the Myparcelasia API.
API Key The API key credential for authenticating requests to the Myparcelasia service.
Postcode The postcode string to look up via the API.

Output

The output of the node is a JSON object containing the response from the Myparcelasia postcode lookup API. This typically includes detailed information related to the provided postcode, such as location data or validation results.

The output structure is:

{
  "json": {
    // Response fields returned by https://api.customje.com/mpa-get-postcode.php
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires valid credentials: a CJ Token and an API Key for the Myparcelasia API.
  • Makes HTTP POST requests to https://api.customje.com/mpa-get-postcode.php.
  • Requires network connectivity to the Myparcelasia API endpoint.
  • No additional environment variables or n8n configurations are needed beyond providing the credentials.

Troubleshooting

  • Authentication errors: If the CJ Token or API Key is invalid or missing, the API will reject the request. Ensure both credentials are correctly entered and active.
  • Invalid postcode format: Providing an incorrectly formatted postcode may result in an error or empty response. Verify the postcode input matches expected formats.
  • Network issues: Failure to reach the API endpoint can cause timeouts or connection errors. Check internet connectivity and firewall settings.
  • API changes: If the Myparcelasia API changes its endpoint or request format, the node may fail. Confirm the API documentation if unexpected errors occur.

Common error messages thrown by the node include:

  • "The operation is not implemented yet!" — indicates an unsupported operation was selected.
  • "The resource \"actions\" is not known!" — indicates an invalid resource selection.

Resolving these involves selecting the correct Resource ("Action") and Operation ("Get Postcode").

Links and References

Discussion