Sharpei icon

Sharpei

Consume Sharpei Api

Overview

This node integrates with the Sharpei API to perform operations related to various resources, including Customers. Specifically, the "Get Customer" operation retrieves detailed information about a single customer identified by a unique customer PID. This is useful in scenarios where you need to fetch up-to-date customer data from Sharpei for processing, reporting, or synchronization with other systems.

Practical examples include:

  • Retrieving customer details before updating records in a CRM.
  • Fetching customer information to personalize communications or offers.
  • Validating customer existence and status before processing orders.

Properties

Name Meaning
Customer PID The unique identifier (PID) of the customer to retrieve. This is required to specify which customer’s data to fetch.

Output

The node outputs JSON data representing the customer's details as returned by the Sharpei API. The structure typically includes all relevant customer fields such as name, contact information, status, and any other metadata provided by the API.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the customer, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the Sharpei API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL for API requests is https://api.prod.gosharpei.com/api.
  • Proper network access to the Sharpei API endpoint must be ensured.

Troubleshooting

  • Missing or invalid Customer PID: The operation requires a valid customer PID; ensure this property is set correctly.
  • Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate. Verify credential configuration.
  • Network issues: Connectivity problems to the Sharpei API endpoint can cause request failures.
  • API response errors: If the specified customer PID does not exist, the API may return a 404 or similar error. Handle such cases gracefully in workflows.

Links and References

Discussion