Form.io ACTION

Update Form Action

Update an action attached to a Form.io form. Only the fields you provide are changed; omitted fields keep their current values. Use List Form Actions to find the action ID. The settings prop is a JSON-string object specific to the action type. See the documentation.

Action
Writes data
API key
SDK
MCP

Start building

IMPLEMENTATION

Call this tool

Connect a user's Form.io account once, then configure and run Update Form Action from your backend or agent.

Pipedream Connect

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: "form_io-update-form-action",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    form_io: { authProvisionId: "apn_xxxxxxx" },
    formId: "Form ID",
    actionId: "Action ID",
  },
})

console.log(result)

curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "form_io-update-form-action",
    "configured_props": {
      "form_io": { "authProvisionId": "apn_xxxxxxx" },
      "formId": "Form ID",
      "actionId": "Action ID"
    }
  }'

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "form_io",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
  name: "form_io-update-form-action",
  arguments: {
    formId: "Form ID",
    actionId: "Action ID",
  },
})

SCHEMA

Inputs

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

Update Form Action inputs
Property	Type	Description
`formId` Form ID	`string`	The `_id` of the form. Run List Forms first to obtain valid form IDs. Required
`actionId` Action ID	`string`	The `_id` of the form action. Run List Form Actions first to obtain valid action IDs. Required
`title` Title	`string`	Updated title of the action. Optional
`handler` Handler	`string[]`	When the action runs. Values: `before`, `after`. Optional
`method` Method	`string[]`	Which operations trigger the action. Values: `create`, `update`, `read`, `delete`, `index`. Optional
`priority` Priority	`integer`	Execution priority of the action. Optional
`settings` Settings	`string`	JSON-string object of action-specific settings; the shape depends on the action type. Example (webhook action): `{"method":"post","url":"https://example.com/webhook"}`. Parsed with JSON.parse() before sending. Optional

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: form_io-update-form-action
Version: 0.0.1
App: Form.io
Authentication: API key
Read-only: No
Destructive: No
Open world: Yes
Source: View on GitHub ↗

Call this tool #

Inputs #

Tool details #

Call this tool

Inputs

Tool details