Shopier icon

Shopier

Interact with Shopier API
Join our community

Actions5

Overview

The node interacts with the Shopier API to retrieve order information. Specifically, for the "Order" resource and "Get" operation, it fetches details of a single order based on a provided Order ID. This is useful in scenarios where you need to obtain detailed information about a specific order, such as its status, customer details, or transaction history.

Practical examples include:

  • Fetching an order's details after receiving a webhook notification about a new purchase.
  • Retrieving order data to update your internal CRM or ERP system.
  • Displaying order information in a custom dashboard or report.

Properties

Name Meaning
Order ID The ID of the order to retrieve

Output

The node outputs JSON data representing the retrieved order. This JSON typically includes all relevant order details returned by the Shopier API, such as order status, items, customer information, payment details, and timestamps.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the order, but this is not applicable for the "Get Order" operation.

Dependencies

  • Requires an API key credential for authenticating with the Shopier API.
  • The node makes HTTP requests to https://api.shopier.com.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Order ID will likely result in an error from the API indicating the order was not found.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • "The operation "get" is not supported for resource "order": This indicates a mismatch between selected resource and operation; ensure "Order" resource and "Get" operation are selected.
    • API errors related to authorization or invalid parameters will be passed through; verify the Order ID and API credentials.

  • Resolution tips:

    • Double-check the Order ID value for correctness.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion