Post-Purchase CX Automation Platform built for Retail. WeSupply helps retailers reduce their customer support tickets with Pre-purchase delivery prediction, automated shipping tracking, proactive notifications and self-service returns.
Orders can be pushed into the WeSupply platform via a JSON containing the order data. See the docs here
Write custom Node.js code and use any of the 400k+ npm packages available. Refer to the Pipedream Node docs to learn more.
The WeSupply API serves as a bridge connecting your ecommerce platforms to WeSupply's order tracking and logistics features. By utilizing the API within Pipedream, you unlock the potential to automate order updates, streamline returns, and enhance customer service interactions. Pipedream's serverless platform allows you to create workflows that trigger based on certain events, process data, and connect to countless other APIs and services—essentially turning your WeSupply data into actionable insights and automated tasks without the need for a dedicated backend infrastructure.
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
wesupply: {
type: "app",
app: "wesupply",
}
},
async run({steps, $}) {
return await axios($, {
url: `https://${this.wesupply.$auth.client_name}.labs.wesupply.xyz/api/orders/lookup`,
headers: {
Authorization: `Bearer ${this.wesupply.$auth.oauth_access_token}`,
},
})
},
})
Develop, run and deploy your Node.js code in Pipedream workflows, using it between no-code steps, with connected accounts, or integrate Data Stores and File Stores.
This includes installing NPM packages, within your code without having to manage a package.json
file or running npm install
.
Below is an example of installing the axios
package in a Pipedream Node.js code step. Pipedream imports the axios
package, performs the API request, and shares the response with subsequent workflow steps:
// To use previous step data, pass the `steps` object to the run() function
export default defineComponent({
async run({ steps, $ }) {
// Return data to use it in future steps
return steps.trigger.event
},
})