Wrike ACTION
List Custom Fields Keys Options
Retrieves available custom fields so callers can copy field IDs into free-form customFields props in other actions. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Wrike account once, then configure and run List Custom Fields Keys Options 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: "wrike-list-custom-fields-keys-options",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
applicableEntityTypes: ["Applicable Entity Types"],
types: ["Types"],
},
})
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": "wrike-list-custom-fields-keys-options",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"applicableEntityTypes": ["Applicable Entity Types"],
"types": ["Types"]
}
}'// 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": "wrike",
},
},
},
)
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: "wrike-list-custom-fields-keys-options",
arguments: {
applicableEntityTypes: ["Applicable Entity Types"],
types: ["Types"],
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
applicableEntityTypes Applicable Entity Types | string[] | Filter by applicable entity types. One or more of: User, WorkItem. Defaults to WorkItem. Optional |
types Types | string[] | Filter by custom field types. One or more of: Multiple, Percentage, Text, Duration, CalculatedNumeric, Date, CalculatedDate, Numeric, Contacts, Checkbox, Currency, DropDown, LinkToDatabase. Optional |
inheritanceTypes Inheritance Types | string[] | Filter by custom field inheritance types. One or more of: All, Tasks, Projects, Folders. Optional |
title Title | string | Filter by custom field title. Optional |
fields Fields | string[] | Optional fields to include in the response. One or more of: dataUsageStatistics. 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
- wrike-list-custom-fields-keys-options
- Version
- 0.1.1
- App
- Wrike
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗