OtherReal-timeUpdated May 2026

Wrike

Wrike enterprise project task management

Wrike is the enterprise project-management platform — used by mid-to-large companies that need structured project hierarchies, custom workflows per team, time tracking, request forms, and reporting. Tiny Command exposes four actions, no triggers (Wrike has webhooks configured at the space/account level via /webhooks endpoints — set them up via HTTP action and point at a Tiny Command webhook trigger): List Tasks (filterable by project, assignee, status, due date), Create Task, Update Task (change status, dates, assignees), Add Comment (post a comment to a task's discussion thread). The connection uses Wrike OAuth at account scope. Wrike's resource model nests Spaces → Folders → Projects → Tasks (with Tasks the leaf-level work unit). Tasks have rich attributes — assignees, dates (start/end), status, custom fields, dependencies, time-tracked hours. Most cross-app workflows interact at the task level: a Linear/Jira issue triggers Create Task in Wrike for the PM team to track delivery against the engineering work.

Connect Wrike

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Wrike can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Add Comment	Adds a comment to a Wrike task with optional @mentions. Use for automation activity logs, status updates, or AI summarization of attachments.	3 fields	View →
Create Task	Creates a task inside a Wrike folder/project with title, description, assignees, dates, importance, and custom field values. The standard write action for piping form submissions or external tickets into Wrike.	7 fields	View →
List Tasks	Lists tasks in a Wrike folder (or all tasks if no folder is given), with filters for status, assignee, and date. Used for digests, sprint reviews, or warehouse export.	2 fields	View →
Update Task	Updates fields on an existing Wrike task: title, description, status, assignees, dates, importance, or custom fields. Only the fields you pass are changed.	4 fields	View →

Recipes

Pre-built Wrike workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Wrike → Slack alerts

AI-triage every Wrike event, ping the right channel only when it matters.

Wrike → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Wrike → Notion database

Turn Wrike into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Wrike once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Wrike field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Wrike integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Wrike to Tiny Command?

Open the Tiny Command workflow builder, drop in a Wrike node, and click Connect. Authorize Wrike once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Wrike triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Wrike today. Use Tiny Command's universal Webhook or Schedule trigger to start Wrike workflows, then run any Wrike action you need.

What Wrike actions can I run from a workflow?

4 Wrike actions are available out of the box, covering other operations like "Add Comment". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Wrike integration real-time?

Wrike actions execute synchronously inside your workflow. Tiny Command waits for Wrike's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Wrike with Tiny Command?

No. Every Wrike trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Wrike API endpoint directly.

How much does the Wrike integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Wrike integration itself has no per-app surcharge.