View as Markdown
WOXO icon

WOXO TRIGGER

New Video

Emit new event on each new video.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's WOXO 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: "woxo-new-video",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    woxo: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    projectId: "Project ID",
  },
  webhookUrl: "https://example.com/webhooks/woxo",
})

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 Video configuration
Property Type Description
timer Timer $.interface.timer
Required
projectId Project ID string
The ID of project. You can get this ID from the url. E.g. With URL woxo.tech/video/editor?slug=F0AOtl8sdg the ID will be F0AOtl8sdg
Required

01

Connect

Your user authorizes WOXO 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
woxo-new-video
Version
0.0.2
App
WOXO
Authentication
API key
Delivery
Polling source
Output
Events emitted by WOXO.