View as Markdown
Dify icon

Dify ACTION

Get App Parameters

Return the connected Dify app's configuration: its user_input_form (the exact input variable names, types, and which are required), file-upload limits, opening statement, and suggested questions. Call this before Run Workflow to know what to pass in its Inputs parameter, instead of guessing variable names. Example: an app with one required text variable returns { user_input_form: [{ "text-input": { variable: "city", label: "City", required: true, default: "" } }], opening_statement, suggested_questions, file_upload, ... }, so pass { "city": "..." } as Inputs. See the documentation
  • Action
  • Read only
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Dify account once, then configure and run Get App Parameters 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: "dify-get-app-parameters",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    dify: { authProvisionId: "apn_xxxxxxx" },
  },
})

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 App Parameters inputs
Property Type Description

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
dify-get-app-parameters
Version
0.0.1
App
Dify
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes