View as Markdown
MoDeck icon

MoDeck TRIGGER

New Render Completed

Emit new event when a render is completed.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's MoDeck 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: "modeck-render-complete",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    modeck: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    deck: "Deck Name",
  },
  webhookUrl: "https://example.com/webhooks/modeck",
})

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 Render Completed configuration
Property Type Description
timer Polling interval $.interface.timer
Pipedream will poll the MoDeck on this schedule
Required
deck Deck Name string
The deck name you want to edit.
Required Dynamic

01

Connect

Your user authorizes MoDeck 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
modeck-render-complete
Version
0.0.1
App
MoDeck
Authentication
API key
Delivery
Polling source
Output
Events emitted by MoDeck.