Docs · Connector reference

Wrike connector reference

Operations, inputs, troubleshooting, and questions for the Wrike connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Wrike connection

Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

Resource	Record identity	Start with	Page coverage
Spaces	`id`	Top level	Cursor
Tasks	`id`	Top level	Cursor
Contacts	`id`	Top level	None configured
Folders and projects	`id`	Top level	Cursor

Record identity: Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with: Resolve the parent identifier first.
Cursor: Cursor pagination. Continue from the returned cursor; an initial page is not a complete inventory.
None configured: No page continuation is configured for this resource. Check the response and any provider limits before treating it as a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Action: Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
Read: Retrieves information; check the returned scope and identifiers before use.

Operation	Effect	Approval	Provider permissions	Inputs
Task Create	Action	Approval required	wsReadWrite	6
Task Update	Action	Approval required	wsReadWrite	6
Folder Create	Action	Approval required	wsReadWrite	4
Task Get	Read	By policy	Default	1
Task Rename	Action	Approval required	Default, wsReadWrite	2

Inputs by operation

Task Create Action · approval required

Inputs for Wrike Task Create
Input	Requirement	Accepted value
`description`	Optional	stringMaximum characters: 100000
`folder_id`	Required	stringMinimum characters: 1Maximum characters: 256
`idempotency_key`	Optional	stringMinimum characters: 1Maximum characters: 256
`importance`	Optional	stringMinimum characters: 1Maximum characters: 64
`status`	Optional	stringMinimum characters: 1Maximum characters: 64
`title`	Required	stringMinimum characters: 1Maximum characters: 255

Task Update Action · approval required

Inputs for Wrike Task Update
Input	Requirement	Accepted value
`description`	Optional	stringMaximum characters: 100000
`idempotency_key`	Optional	stringMinimum characters: 1Maximum characters: 256
`importance`	Optional	stringMinimum characters: 1Maximum characters: 64
`status`	Optional	stringMinimum characters: 1Maximum characters: 64
`task_id`	Required	stringMinimum characters: 1Maximum characters: 256
`title`	Optional	stringMinimum characters: 1Maximum characters: 255

Folder Create Action · approval required

Inputs for Wrike Folder Create
Input	Requirement	Accepted value
`description`	Optional	stringMaximum characters: 100000
`idempotency_key`	Optional	stringMinimum characters: 1Maximum characters: 256
`parent_id`	Required	stringMinimum characters: 1Maximum characters: 256
`title`	Required	stringMinimum characters: 1Maximum characters: 255

Task Get Read

Inputs for Wrike Task Get
Input	Requirement	Accepted value
`task_id`	Required	string

Task Rename Action · approval required

Inputs for Wrike Task Rename
Input	Requirement	Accepted value
`task_id`	Required	string
`title`	Required	stringMinimum characters: 1Maximum characters: 255

When the Wrike task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the oauth connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Wrike connector

Can I use my existing agent with Wrike?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Wrike?

This connector supports 2 actions, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Wrike?

Prepare Wrike account host, OAuth client ID, OAuth client secret, Wrike access token; the connection uses OAuth, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Wrike keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.

Wrike connector overview Docs All connectors