Actions6
Overview
This node integrates with the Myparcelasia API to perform various actions related to shipping and user information management. Specifically, the Get User Details operation retrieves user information from the Myparcelasia service using provided authentication tokens.
Common scenarios where this node is beneficial include:
- Fetching authenticated user details for account verification or display.
- Integrating user data retrieval into automated workflows for shipping or order processing.
- Using user information as part of conditional logic in larger automation sequences.
Example use case: An e-commerce platform automates order fulfillment by first retrieving user details from Myparcelasia to confirm account status before creating shipments.
Properties
| Name | Meaning |
|---|---|
| CJ Token | The CJ Token used for authenticating requests to the Myparcelasia API. |
| API Key | The API Key required for accessing the Myparcelasia service endpoints securely. |
Both properties are required for the Get User Details operation and must be provided as secure strings (password type).
Output
The output JSON contains the response returned by the Myparcelasia API endpoint for user details. This typically includes user-specific information such as account data, profile details, or other metadata associated with the authenticated user.
The structure depends on the API response but will be directly passed through as JSON under the json field of the output item.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Myparcelasia API endpoints.
- Needs valid authentication credentials: a CJ Token and an API Key.
- Network connectivity to
https://api.customje.com/mpa-get-user.php. - No additional environment variables or n8n credential types are explicitly required beyond providing the tokens as input parameters.
Troubleshooting
- Authentication errors: If the CJ Token or API Key is invalid or expired, the API may return an error. Verify that the tokens are correct and have not been revoked.
- Network issues: Failure to reach the API endpoint could be due to network problems or firewall restrictions. Ensure the n8n instance has internet access.
- Unexpected API responses: If the API changes or returns unexpected data, the node output might not match expectations. Check the API documentation or contact Myparcelasia support.
- Operation not implemented error: This node only supports predefined operations. Using an unsupported operation name will throw an error.
Links and References
- Myparcelasia API Documentation (Assumed URL; replace with actual if known)
- n8n HTTP Request Helper Documentation