View as Markdown
Thanks.io icon

Thanks.io TRIGGER

New Order

Emit new event for each new order placed.
  • Trigger
  • Polling
  • OAuth
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Thanks.io account, configure the source, and choose the webhook where your backend receives events.

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: "thanks_io-new-order",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    thanks_io: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    subAccount: "Sub Account",
  },
  webhookUrl: "https://example.com/webhooks/thanks-io",
})

console.log(deployed.id)

MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.

SCHEMA

Configuration

These inputs define which events the source watches. Dynamic options are loaded from the connected account.

New Order configuration
Property Type Description
timer Polling interval $.interface.timer
Pipedream will poll the API on this schedule
Required
subAccount Sub Account string
ID of subaccount to use
Optional Dynamic

01

Connect

Your user authorizes Thanks.io through Pipedream managed auth.

02

Deploy

Your backend deploys this source with that user's own configuration.

03

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.

OR

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

Registry key
thanks_io-new-order
Version
0.0.3
App
Thanks.io
Authentication
OAuth
Delivery
Polling source
Output
Events emitted by Thanks.io.