Project management · wired today
Drive Wrike with governed agents
Project trackers hold the state your agents plan against. The Wrike connector is one of 205 executable connectors and gives agents 12 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Wrike
| Tool | What it does |
|---|---|
get_current_contact | Get the Wrike user the access token belongs to |
get_account | Get the Wrike account the access token belongs to |
list_contacts | List the Wrike contacts (users and groups) in the account |
list_spaces | List the Wrike spaces the token can access |
list_folders | List the Wrike folder and project tree the token can access |
get_folder | Get one Wrike folder or project by ID, with its description and project dates |
list_tasks | List Wrike tasks across the account, optionally filtered by status, importance or title |
list_folder_tasks | List the Wrike tasks inside one folder or project |
get_task | Get one Wrike task by ID, with its description, responsibles and dates |
list_workflows | List the Wrike workflows and their custom statuses |
list_timelogs | List Wrike time entries across the account |
list_task_timelogs | List the Wrike time entries logged against one task |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Wrike connector needs
You provide access token from your Wrike account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Wrike's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Wrike API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Wrike integration FAQ
What can Quox agents do with Wrike?
Agents can run 12 read-only tools against Wrike: get current contact, get account, list contacts, list spaces, list folders and more. Every call is receipted in the evidence trail.
What does the Wrike integration need?
You provide access token from your Wrike account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Wrike credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Wrike connector?
This connector was blind shape-proven against the real Wrike API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.