Run Node Code with Node API on New Ecwid Paid Orders from ecwid API

Pipedream makes it easy to connect APIs for Node, ecwid and 2,000+ other apps remarkably fast.

Trigger workflow on

New Ecwid Paid Orders from the ecwid API

Next, do this

Run Node Code with the Node API

No credit card required

▶

Watch us build a workflow

4 min

Watch now ➜

Trusted by 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a ecwid trigger and Node action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Ecwid Paid Orders trigger
1. Configure timer
2. Configure Max Days Back
3. Configure Set order fulfilment status (Preferred)
4. Select a New Fulfilment Status
5. Connect your ecwid account
Configure the Run Node Code action
1. Connect your Node account
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Ecwid Paid Orders on ecwid

Description:Search for new orders which are PAID and AWAITING_PROCESSING. Emits events for each order and sets order fulfilment status to PROCESSING

Version:0.0.3

Key:ecwid-paid-orders

View on GitHub

ecwid Overview#

Ecwid's API offers dynamic access to an online store's data, allowing for the automation of tasks such as inventory management, order processing, and customer data analysis. With Pipedream's serverless integration platform, you can create custom workflows that trigger actions within Ecwid or synchronize data across various other apps and services. This capability can streamline operations, save time, and reduce the likelihood of human error.

Trigger Code#

import ecwid from "../../ecwid.app.mjs";
import { FULFILMENT_STATUS_LIST } from "../../commons/commons.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  name: "New Ecwid Paid Orders",
  version: "0.0.3",
  key: "ecwid-paid-orders",
  description: "Search for new orders which are PAID and AWAITING_PROCESSING. Emits events for each order and" +
    " sets order fulfilment status to PROCESSING",
  props: {
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    history: {
      label: "Max Days Back",
      description: "Max number of days to get the orders from",
      type: "integer",
      default: 30,
    },
    setFulfilmentStatus: {
      label: "Set order fulfilment status (Preferred)",
      description: "Upon receiving the order, fulfilment status will be set to user defined value so that " +
        "the same order is not fetched again. If unchecked, it needs to be handled in the workflow",
      type: "boolean",
      default: true,
    },
    newFulfilmentStatus: {
      label: "New Fulfilment Status",
      description: "New Fulfilment Status to be updated in the order",
      type: "string",
      options: FULFILMENT_STATUS_LIST,
      default: "PROCESSING",
    },
    ecwid,
  },
  type: "source",
  methods: {},
  async run() {
    let ordersResponse = await this.ecwid.getOrders(this.history);
    for (const order of ordersResponse.items) {
      this.$emit(order, {
        id: order.id,
        summary: `Order ${order.id}`,
        ts: Date.now(),
      });
      if (this.setFulfilmentStatus) {
        let updateStatus = await this.ecwid.updateFulfilmentStatus(
          order.id,
          this.newFulfilmentStatus,
        );
        if (updateStatus.updateCount === 1)
          console.log("Updated Order Status of " + order.id +
            " to " + this.newFulfilmentStatus);
        else
          console.error("Error Updating Order Status of "
            + order.id + " to " + this.newFulfilmentStatus);
      }
    }
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
	`timer`	`$.interface.timer`
Max Days Back	`history`	`integer`	Max number of days to get the orders from
Set order fulfilment status (Preferred)	`setFulfilmentStatus`	`boolean`	Upon receiving the order, fulfilment status will be set to user defined value so that the same order is not fetched again. If unchecked, it needs to be handled in the workflow
New Fulfilment Status	`newFulfilmentStatus`	`string`	Select a value from the drop down menu:`AWAITING_PROCESSINGPROCESSINGSHIPPEDDELIVEREDWILL_NOT_DELIVERRETURNEDREADY_FOR_PICKUPOUT_FOR_DELIVERY`
ecwid	`ecwid`	`app`	This component uses the ecwid app.

Trigger Authentication#

ecwid uses API keys for authentication. When you connect your ecwid account, Pipedream securely stores the keys so you can easily authenticate to ecwid APIs in both code and no-code steps.

You must be on a paid ecwid plan to use this integration.

About ecwid#

Online store platform

Action#

Run Node Code on Node

Description:Write custom Node.js code and use any of the 400k+ npm packages available. Refer to the [Pipedream Node docs](https://pipedream.com/docs/code/nodejs) to learn more.

Version:0.0.2

Key:node-run-node-code

View on GitHub

Node Overview#

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:

Action Code#

import node from "../../node.app.mjs";

export default {
  name: "Run Node Code",
  version: "0.0.2",
  key: "node-run-node-code",
  description: "Write custom Node.js code and use any of the 400k+ npm packages available. Refer to the [Pipedream Node docs](https://pipedream.com/docs/code/nodejs) to learn more.",
  props: {
    node,
  },
  type: "action",
  methods: {},
  async run({
    steps, $,
  }) {
    // Return data to use it in future steps
    return steps.trigger.event;
  },
};