Myparcelasia icon

Myparcelasia

Custom operations

Actions6

Overview

This node integrates with the Myparcelasia API to perform various shipping-related actions. Specifically, the Check Price operation calculates the shipping cost based on sender and receiver postcodes, receiver country code, and declared weight of the package.

Typical use cases include:

  • Quickly obtaining shipping price estimates before creating shipments.
  • Automating shipping cost calculations in e-commerce workflows.
  • Comparing shipping costs for different destinations or weights.

For example, an online store could use this node to dynamically fetch shipping prices during checkout based on customer location and package weight.

Properties

Name Meaning
CJ Token The authentication token required by the Myparcelasia API.
API Key The API key credential for accessing the Myparcelasia service.
Sender Postcode The postal code from where the shipment will be sent (required).
Receiver Postcode The postal code of the shipment's destination (optional).
Receiver Country Code The country code of the shipment's destination (optional), e.g., "SG" for Singapore.
Declared Weight The weight of the package in kilograms used to calculate the shipping price (required).

Output

The node outputs a JSON object containing the response from the Myparcelasia API's price check endpoint. This typically includes:

  • Pricing details for the shipment based on the provided parameters.
  • Any additional metadata returned by the API relevant to the shipping cost.

No binary data is output by this operation.

Example output structure (simplified):

{
  "price": 12.34,
  "currency": "USD",
  "service_level": "standard",
  "estimated_delivery_days": 5,
  ...
}

Dependencies

  • Requires valid CJ Token and API Key credentials for authenticating requests to the Myparcelasia API.
  • Makes HTTP POST requests to https://api.customje.com/mpa-check-price.php.
  • Needs network access to the external API endpoint.
  • No additional environment variables or n8n-specific configurations are required beyond providing the credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing CJ Token/API Key will cause authentication failures.
    • Incorrect or missing required fields like sender postcode or declared weight may result in API errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "The operation is not implemented yet!" — indicates an unsupported operation was selected.
    • "The resource \"actions\" is not known!" — indicates an invalid resource parameter.
    • API error responses usually contain descriptive messages; ensure credentials and parameters are correct.

  • Resolutions:

    • Verify that the CJ Token and API Key are correctly entered and active.
    • Ensure all required input properties are provided and valid.
    • Check internet connectivity and firewall settings allowing outbound HTTPS requests.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

Discussion