# Wrike AI automation and integrations

> Wrike has a REST API v4 authenticated with OAuth 2.0 or a permanent access token, plus webhooks. Zapier and Make have built-in Wrike apps, and n8n connects through its HTTP Request node. Useful AI automations triage request forms, turn emails and meetings into tasks and write project and client status reports. Wrike documents a limit of 400 requests per minute per access token or IP address.

- Category: Project Management
- Vendor: https://www.wrike.com/
- How to connect: Wrike REST API v4; Webhooks; Zapier and Make apps; n8n HTTP Request node
- Authentication: OAuth 2.0 for apps, or a permanent access token generated in the app console for internal integrations
- Notes: Wrike accounts live in different data centers. The OAuth token response includes the host to call, so integrations must use it instead of hard-coding one API host. Permanent tokens act as the user who created them.
- Last updated: 2026-10-14

## What you can automate with Wrike

- **Request form triage.** Classify request form submissions, fill custom fields, set priority and route each new task to the right team's folder or project. Guide: https://www.lumeor.studio/guides/automate-internal-approvals/
- **Email to task.** Create tasks from client or stakeholder emails with an AI summary, a proposed assignee and the original thread linked. Guide: https://www.lumeor.studio/guides/ai-email-to-task-automation/
- **Meeting action items.** Extract action items from meeting transcripts and create Wrike tasks under the relevant project with owners and dates. Guide: https://www.lumeor.studio/guides/ai-meeting-summaries-and-action-items/
- **Project status reports.** Summarize progress, overdue tasks and blockers per project into a written status for sponsors and stakeholders. Guide: https://www.lumeor.studio/guides/automate-project-status-updates/
- **Agency client reporting.** Combine Wrike delivery progress with campaign metrics into a client-ready monthly report. Guide: https://www.lumeor.studio/guides/ai-marketing-agency-client-reporting/
- **Portfolio operations summary.** Roll up workload, slipping dates and capacity signals across spaces into one weekly operations brief. Guide: https://www.lumeor.studio/guides/automate-weekly-ops-reporting/

## What makes Wrike workable to automate

Wrike structures work as spaces, folders, projects and tasks, with custom fields, custom item types, workflows with custom statuses, and request forms. The v4 REST API covers all of these plus comments, attachments, time logs and approvals. Webhooks can be registered for an account, folder or space and report task and folder changes. Zapier and Make both have Wrike apps; n8n uses HTTP Request nodes.

What catches integrations is configuration and hosting. Statuses belong to custom workflows, so "Completed" in one space may be a different status ID from another. Custom fields are referenced by ID. And API calls must go to the data center host returned during OAuth, which differs for EU accounts.

## The AI layer

Wrike is common in marketing teams, agencies and PMOs with structured intake. AI fits naturally around that intake and reporting:

- **Triage** of request forms and emails into the right project with fields filled, as described in [internal approval workflows](/guides/automate-internal-approvals/).
- **Task creation** from meetings and email threads.
- **Reporting**, especially client-facing summaries, as in [client reporting for marketing agencies](/guides/ai-marketing-agency-client-reporting/).

Pass the model the actual list of projects, statuses and custom field options, and reject anything outside it.

## Limits to plan around

- **400 requests per minute** per access token or IP address. Spread calls evenly and back off on 429 responses.
- **Page size caps.** Task listings return at most 1,000 tasks per page; use the pagination token and filters on large accounts.
- **Data center hosts.** Use the host from the OAuth response for every call.
- **ID formats.** Convert legacy numeric IDs to v4 IDs before using them.
- **Custom workflows.** Map status IDs per workflow rather than by name.

## How Lumeor typically connects it

We set up an OAuth app or a permanent token on a dedicated integration user, build reusable n8n HTTP Request nodes for task creation, custom fields and comments, and cache folder, user and status IDs nightly. Wrike webhooks feed n8n for triage. Weekly summaries run on a schedule and post to Teams or email, following [automated project status updates](/guides/automate-project-status-updates/).

## Frequently asked questions

### Does n8n have a Wrike node?

Not a built-in one. n8n connects to Wrike through the HTTP Request node with an OAuth 2.0 credential or a permanent token, and a Webhook node receives Wrike events. Zapier and Make both have built-in Wrike apps.

### Why do task IDs from the Wrike UI not work in the API?

The web app shows older numeric IDs, while API v4 uses different string IDs. Wrike provides an endpoint to convert legacy IDs to v4 IDs. Store v4 IDs in your workflows and convert anything copied from the browser.

### How should I handle Wrike's rate limit?

Wrike documents a limit of 400 requests per minute per access token or IP address. Spread requests evenly rather than in bursts, cache lookups such as folders, custom fields and users, and use exponential backoff on 429 responses.

### Do I need a custom workflow if Wrike has built-in AI and automation?

Wrike's own automation rules and AI features handle many in-app tasks. Build externally when inputs come from email, forms or other systems, when outputs go to clients or other tools, or when you need strict routing rules with validation.

---

Source: https://www.lumeor.studio/tools/wrike/
Published by Lumeor Studio, Newtown, PA. hello@lumeor.studio. Get a written scope: https://www.lumeor.studio/start/