Wrike ACTION
List Contact ID Options
Retrieves available contacts so callers can copy an ID into free-form responsibles or contactId 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 Contact ID 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-contact-id-options",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
me: true,
metadata: "Metadata",
},
})
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-contact-id-options",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"me": true,
"metadata": "Metadata"
}
}'// 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-contact-id-options",
arguments: {
me: true,
metadata: "Metadata",
},
})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 |
|---|---|---|
me Me Only | boolean | If true, only the requesting user's contact info is returned. Optional |
metadata Metadata | object | Metadata filter, exact match for metadata key or key-value pair, e.g. { "key": "database-id" } (key only) or { "key": "database-id", "value": "42" } (key-value pair). Optional |
deleted Deleted | boolean | Filter by deleted flag. Optional |
customFields Custom Fields | object | Custom field filter. JSON array of custom field objects, e.g. [{ "id": "IEAAAAAAJ4AAAAAA", "value": "High" }]. Optional |
emails Emails | string[] | Filter by email addresses. Limit 100. Optional |
active Active | boolean | Filter by active status. Optional |
name Name | string | Filter by contact name. Optional |
types Types | string[] | Filter by contact type. One or more of: Group, Asset, Person, Robot. Optional |
fields Fields | string[] | Optional fields to include in the response. One or more of: metadata, currentCostRate, customFields, currentBillRate, jobRoleId, workScheduleId. 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-contact-id-options
- Version
- 0.1.1
- App
- Wrike
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗