Asking the AI to build a workflow triggered by a CRM event — a new company being created, a client being updated — used to fail with an "unknown event type" error, even though the workflow editor offered those triggers manually. The copilot's validator simply hadn't learned about them.
Now it has. The copilot can create and edit workflows on the full set of triggers, including client, company, and tenant events, and it understands how they behave: CRM triggers fire for every actor, including automations, and ticket-specific filters like status or priority don't apply to them. If you combine a CRM trigger with a ticket-only filter, you get a clear warning instead of a silent no-op.
Live everywhere — try "build me an enrichment workflow that runs when a company is created."