# New Ecwid Paid Orders — ecwid

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

- Key: `ecwid-paid-orders`
- Type: Trigger (Polling)
- Version: 0.0.4
- App: ecwid (`ecwid`) — https://pipedream.com/apps/ecwid.md
- This page (HTML): https://pipedream.com/apps/ecwid/triggers/paid-orders
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/ecwid/sources/paid-orders/paid-orders.mjs

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Timer |
| `history` | `integer` | Yes | Max number of days to get the orders from |
| `setFulfilmentStatus` | `boolean` | Yes | 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 |
| `newFulfilmentStatus` | `string` | Yes | New Fulfilment Status to be updated in the order |

## Returns

Events emitted by ecwid.

## Run it

**TypeScript**

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const deployed = await pd.triggers.deploy({
  id: "ecwid-paid-orders",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    ecwid: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    history: 10,
  },
  webhookUrl: "https://example.com/webhooks/ecwid",
})

console.log(deployed.id)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "ecwid-paid-orders",
    "webhook_url": "https://example.com/webhooks/ecwid",
    "configured_props": {
      "ecwid": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "history": 10
    }
  }'
```

**MCP**

MCP servers expose ecwid actions as on-demand tools.

New Ecwid Paid Orders is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/ecwid.md · All apps: https://pipedream.com/apps