View as Markdown
Orshot icon

Orshot ACTION

Get Studio Template Modifications

Get available modification keys for a studio template
  • Action
  • Read only
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Orshot account once, then configure and run Get Studio Template Modifications from your backend or agent.

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 result = await pd.actions.run({
  id: "orshot-get-studio-template-modifications",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    orshot: { authProvisionId: "apn_xxxxxxx" },
    templateId: "Studio Template ID",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Get Studio Template Modifications inputs
Property Type Description
templateId Studio Template ID string
The ID of the studio template to render. You can find this on the template playground page.
Required

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
orshot-get-studio-template-modifications
Version
0.0.2
App
Orshot
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes