Triggers

Automation Triggers defines the triggers that run agent workflows when webhook events match conditions. The surface lives under Automations, with one row per trigger and columns for trigger, source, action, runs, and active. The rows shown are MS Teams Drive to Meetings (Test), Fireflies to Deliverables, New Deliverable to Agent Ops Session, Client Theme Follow-Up Actions, Proof Feedback to Brand Profile Update, V2 Test, and Project Brief Review Agent.

Sources name the event each trigger listens to: ziflow/proof.approved, database/ai.meetings.insert, database/ai.work_items.insert with the condition work_item_type_id equals deliverable, message/general, database/ziflow.proof_comments.insert with the condition author_email not_contains presh, database/projects.tasks.insert, and database/ai.campaign_strategy.update. Every row’s action is an Agent Workflow. Runs carry the count plus the last-run date: New Deliverable to Agent Ops Session shows 2 (last 7/21/2026), Proof Feedback to Brand Profile Update shows 618 (last 7/10/2026), V2 Test shows 490 (last 2/5/2026), and Project Brief Review Agent shows 4652.

• One trigger starts one kind of work; the trigger name says which workflow it starts.
• The source plus its condition decides when the trigger fires; narrow the condition before broadening the workflow.
• After any trigger change, watch the next runs and their approval outcomes before calling the change done. Denial patterns are design feedback.
• The Active toggle enables or pauses a trigger; a dead trigger that stays enabled is a surprise waiting for a bad moment. New Trigger adds one.

What next

• Automations: the automated work these triggers start.
• Workflows: the workflows and statuses that work runs inside.
• Notifications: the event catalog and delivery templates behind trigger sources.