Wrike

Connect AI agents to Wrike. Agents create folders and tasks, update status and assignments, post and read comments, and look up contacts to keep project work moving across your workspace.

11 actions API key available

Wrike website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A client kickoff form arrives with scope, dates, and stakeholders

Create Folder spins up the project with Is Project enabled, owners set, status Green, and the engagement dates

List Contacts resolves the delivery team's contact ids for assignment

Create Task seeds the standard work breakdown, each task with responsibles and YYYY-MM-DD due dates

Agent verifies every seeded task landed with an assignee and a due date, because an unassigned task in week one becomes an unowned crisis in week six

The delivery lead reviews the generated plan and adjusts owners before the client sees anything

Create Comment posts the kickoff summary and form link on the top task

The project permalink goes to the account channel

What This Integration Enables

Wrike is where enterprise work is supposed to be visible, and the gap between "supposed to" and "is" gets filled by coordinators doing data entry. This connector hands that entry to FlowRunner agents. They browse the folder tree, create projects with owners, statuses, and date ranges, seed and update tasks with assignees resolved from real contact ids, keep discussion on the record with comments, and pull task inventories for reporting. The design view: a project tool earns trust when its data is current and attributed, and loses it one stale task at a time. Agents are good at current; humans stay in charge of what work means. - Convert forms, emails, and chat requests into properly filed tasks - Stand up projects with owners, RAG status, and dates from intake data - Sync task status, importance, and dates as work moves in other systems - Post and read comments so decisions live on the task, not in DMs - Export task, project, and contact inventories for dashboards

Without FlowRunner

Intake is retyping Requests arrive in forms, email, and chat, and a coordinator re-keys them into Wrike days later

Status lives in people's heads The true state of work surfaces only in standups, then evaporates

Stale tasks accumulate silently Deferred work from last quarter clogs every view until nobody trusts the task list

With FlowRunner

Intake is instant and attributed Requests become tasks in the right project with responsibles and dates the hour they arrive

Status is written where work lives Agents sync statuses and post comments, so the project view is the standup

Cleanup is proposed, not improvised Agents surface stale tasks with evidence and a person decides what gets cancelled

Use Case Scenarios

The intake queue that files itself

A request lands via [Typeform](/integrations/typeform). The agent classifies it, finds the destination with List Folders, and calls Create Task with a title, distilled description, importance, and a due date derived from the request's SLA. The responsible comes from List Contacts, matched to the on-duty owner. Requests that do not fit an existing project trigger Create Folder as a project, seeded with the standard first tasks. The requester gets the permalink back, and the coordinator's transcription shift ends permanently.

Status that flows both directions

When a deploy completes in the engineering stack, the agent calls Update Task to move the linked task to Completed and Create Comment to record the release version and time. Going the other way, a Friday sweep runs List Tasks filtered to Active and High importance, checks due dates with Get Task, and posts the at-risk list to [Slack](/integrations/slack) with permalinks. The Monday status meeting reads the project, not a slide assembled Sunday night.

The portfolio report nobody compiles

Weekly, the agent walks List Folders, pulls project objects with Get Folder for owner, status, and dates, then runs List Tasks In Folder per project to count open, overdue, and completed work. The rollup lands in [Google Sheets](/integrations/google-sheets): every project, its RAG status, and its task health on one tab. The PMO reviews exceptions instead of chasing twelve project leads for updates that were already visible in Wrike all along.

Human-in-Loop Highlight

Update Task can set a status of Cancelled, and in Wrike that is how work dies: the task drops out of active views, responsibles stop seeing it, and whatever client commitment it represented quietly stops being tracked. A cleanup agent that cancels everything untouched for 90 days will eventually cancel the task that was waiting on the client's legal team, and no one will notice until the client does. So FlowRunner stale-work sweeps never cancel on their own judgment. The agent builds the docket: task title, project, responsibles, last comment from List Comments, days idle, and the delivery lead rules on each: cancel, defer, or reassign via Add Responsible IDs. The same gate holds for Create Comment when the text will land in a client-shared project, because a comment in Wrike is a written record with an audience the agent cannot see. Machines propose the cleanup; the person who made the commitment decides which commitments are dead.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

11 actions

Folders and Projects

List Folders Lists all folders and projects as a lightweight tree with ids, titles, scope, and child ids. Projects are folders carrying a project object. The map every filing decision starts from.
Get Folder Retrieves full details for one or more folders by id: title, description, permalink, shared users, custom column ids, and for projects the owners, status, and dates.
Create Folder Creates a folder or, with Is Project enabled, a project with owner contact ids, a status (Green, Yellow, Red, Completed, On Hold, Cancelled), and start and end dates.

Tasks

List Tasks Lists tasks account-wide with filters for title, status (Active, Completed, Deferred, Cancelled), and importance (High, Normal, Low), up to 1000 per page. The read behind portfolio sweeps.
List Tasks In Folder Lists the tasks inside one folder or project with the same status and importance filters. The per-project view for rollups.
Get Task Retrieves full task detail by id or comma-separated ids: description, status, importance, dates, responsibles, followers, parent folders, custom fields, and permalink.
Create Task Creates a task in a folder or project with title, description, status, importance, responsible contact ids, and YYYY-MM-DD start and due dates.
Update Task Updates title, description, status, importance, or dates, changing only supplied fields. Assignees change via Add Responsible IDs and Remove Responsible IDs. The write FlowRunner gates when the status is Cancelled.

Comments

List Comments Lists a task's comments chronologically with text, author contact id, and creation date. The context read before any reply.
Create Comment Adds a plain-text comment to a task. The write that puts an agent's findings on the permanent record.

Contacts

List Contacts Lists the account's users and groups with id, name, email, and type. Supplies the contact ids behind every assignment and ownership decision.

Frequently Asked Questions

What can FlowRunner do with Wrike?

FlowRunner agents can run List Folders, Get Folder, and Create Folder in Wrike, plus 8 more actions.

Does connecting Wrike to FlowRunner require OAuth?

No. Wrike connects to FlowRunner with an API key, no OAuth flow required.

Can Wrike trigger a FlowRunner workflow automatically?

Wrike doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Wrike

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us