--- title: Wrike API Integration on Truto slug: wrike category: Ticketing canonical: "https://truto.one/integrations/detail/wrike/" --- # Wrike API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ### Unified Ticketing API - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Collections** — Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection. - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **Fields** — Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Ticket, Contact, etc. is_user_defined attribute within Field can be used to differentiate between custom and system defined Fields. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Users** — Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc. - **Workspaces** — Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization. ## How it works 1. **Link your customer's Wrike account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Wrike.** The Proxy API is a 1-to-1 mapping of the Wrike API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync support escalations into Wrike engineering workflows** — Helpdesk and customer support SaaS companies can let their users escalate complex bugs or feature requests directly into Wrike as tasks, keeping comments and status changes in sync across both platforms so support agents always have visibility into engineering progress. - **Auto-provision Wrike projects from deal closures** — CRM and revenue operations platforms can automatically create Wrike projects with pre-populated custom fields when a deal closes, eliminating manual handoffs between sales and delivery teams and ensuring professional services can start onboarding immediately. - **Pull Wrike task data into client-facing dashboards and billing tools** — Agency management and billing SaaS products can read completed tasks, time logs, and project metadata from Wrike to generate accurate invoices and real-time progress reports for end clients without exposing internal project details. - **Push approved assets and status updates back into Wrike campaigns** — Marketing automation and creative proofing tools can write final deliverables as attachments to Wrike tasks, update custom fields to reflect approval status, and leave comments tagging the responsible campaign manager — all without leaving the proofing tool. - **Centralize user and group data for cross-platform identity mapping** — Any B2B SaaS that needs to assign work or mention users across systems can pull Wrike's user directory, groups, and roles to accurately map identities between their product and their customer's Wrike instance. ## What you can build - **Two-way ticket and comment sync** — Keep tasks (tickets), status changes, and threaded comments synchronized between your product and your customer's Wrike workspace in near real-time. - **Automated project provisioning from external triggers** — Create new Wrike folders or projects (collections) with custom field values pre-filled whenever a qualifying event occurs in your SaaS — like a deal closing or a client onboarding starting. - **Custom field read/write for structured data mapping** — Read and write Wrike custom fields so your product can exchange structured metadata like client region, estimated revenue, or external reference IDs without manual data entry. - **Attachment push for deliverable handoff** — Automatically attach final files — approved assets, signed documents, generated reports — to the correct Wrike task so delivery teams have everything in one place. - **User directory sync for assignment and identity resolution** — Import Wrike users, groups, and roles into your application to power accurate task assignment, @-mention resolution, and permission mapping across platforms. - **Workspace-scoped data access for multi-team customers** — Let your users select which Wrike Space (workspace) your integration accesses, so enterprise customers can scope the integration to a single department like Marketing or IT without exposing unrelated data. ## FAQs ### How does Truto handle authentication with Wrike? Truto manages the full OAuth 2.0 flow that Wrike requires, including token refresh. Your application never touches raw credentials — Truto stores and rotates tokens on your behalf so your end users simply authorize the connection once. ### How do Wrike concepts map to Truto's Unified Ticketing API? Wrike Tasks map to Tickets, Folders and Projects map to Collections, Spaces map to Workspaces, and Wrike's Custom Fields map to Fields. Comments, Attachments, and Users map directly to their unified counterparts. ### Can the integration handle Wrike's nested sub-task hierarchy? Wrike allows indefinitely nested sub-tasks. Through Truto's Unified Ticketing API, you can read parent-child relationships on Tickets. Keep in mind that deeply nested structures may require recursive calls, which Truto's pagination handling simplifies. ### Are there specific Truto tools available for Wrike today? Wrike tools are built on request. Once you signal interest, Truto provisions the integration against its Unified Ticketing API and Unified User Directory API, covering Tickets, Collections, Workspaces, Comments, Attachments, Fields, Users, Groups, and Roles. ### Does Truto handle Wrike's API rate limits and pagination? Yes. Truto abstracts away Wrike's rate limiting and cursor-based pagination so your application receives consistent, paginated responses without needing to implement back-off logic or track page tokens. ### Can I read and write Wrike Custom Fields through the unified API? Yes. Wrike relies heavily on Custom Fields for structured data like client metadata or external IDs. Truto's Unified Ticketing API exposes these through the Fields resource, allowing you to both read existing values and write updates.