All articles

AI Agent Triggers Reference

Last updated on

Wrike Documentation Team

Wrike Documentation Team

TL;DR

Wrike agent triggers define when an AI agent runs. Choose a trigger type - Scheduled, Event-based, Date-based, API-triggered, or Wrike Automations - then set the scope (any subitem or the item itself). AI Agents can read most custom field types, authors, assignees, parent/sibling/subtask data, and location context to automate workflows like intake, triage, reminders, and reporting.

Table 10. Availability

Free Team Business Pinnacle Apex
Availability: Business, Pinnacle, Apex. ; Unavailability: Free, Team;

Overview

Triggers define when an AI agent runs. Choose the trigger type that matches your workflow, then set the scope that determines which items the trigger applies to.

AI Agent Trigger Types Trigger Types

Trigger type When it fires Example
Scheduled At a set interval (Daily, Weekly, or Custom) A risk status reporter that runs daily
Event-based On events such as New item created or Field value changes (status or other fields) Fire when status changes
Date-based Relative to a date field value "3 days before Due Date" or "When Start Date is reached"
API-triggered When changes are made via the Wrike API Integration with external systems
Wrike Automations Bidirectional with Automations - rules can trigger AI agents, and agent actions can activate rules Complex multi-step workflows combining AI + rule-based automation

Note

Date-based details: Works with Date and Date-time custom fields, supports working-days calculation. Ideal for reminders, escalations, and deadline-based actions.

How AI Agents Can Read Custom Fields

AI agents can read and react to these custom field types: Text, Number, Percent, Currency, Date, Single Select, Multi Select, Duration, Checkbox, Link to Database, Mirrors, and Calculated/formula fields.

In addition to custom fields, AI agents can read:

  • Author and assignee of the work item
  • Empty custom fields - agents can reason about what's missing, not just what's present
  • Calculated/formula fields - can expose system data agents can't access directly (capacity, workload, scheduled hours)
  • Parent item custom fields
  • Sibling and subtask items for cross-item reasoning
  • Location context - where the agent sits in the space and account hierarchy

Trigger Scope

Set the scope for when the trigger should happen:

Any subitem of the work item where the AI Agent was added

  • Use for task-level actions, like Intake or Triage. The AI agent reacts to changes in subitems and acts on those subitems.
  • Example: The Intake agent is added to an Incoming Requests folder. When a new subitem is added, it triggers the AI agent to check if all required information (like assignee or due date) is provided, then posts a comment to that subitem.

Item where the AI Agent was added

  • Use for aggregate actions, like a risk reporter. The AI agent reacts to changes in this item and acts on this same item.
  • Example: A custom agent is added to a Product Launch project to notify followers about changes. If any custom field changes, the AI agent posts a comment and @mentions all followers.

What’s Next?

0 comments

Please sign in to leave a comment.

Top

Related articles