Every WorksBuddy agent shares one data layer and can trigger the others automatically. This page shows how Ranko fits into that suite, both as a trigger for other agents and as something other agents can trigger.
Automations Ranko triggers
These are examples of events in Ranko that can set work in motion across the suite.
| When this happens in Ranko | Connected agent | What happens |
|---|---|---|
| A 90 day publishing plan is approved | Taro (projects) | Article tasks are created and scheduled for the content team. |
| A page is published | Sigi (documents) | The finished article and its source brief are filed and version tracked. |
| A new article ranks or gets quoted by an AI assistant | Evox (campaigns) | The page is queued for promotion across campaign channels. |
| Rank decay is detected on a published page | Taro (projects) | A refresh task is queued with the competitor gap details attached. |
| A high intent comparison page goes live | Lio (CRM) | New inbound leads from the page are routed to the right owner. |
Automations that trigger Ranko
These are examples of events elsewhere in the suite that can prompt action in Ranko.
| When this happens in another agent | Source agent | What happens in Ranko |
|---|---|---|
| A new product or feature ships | Taro (projects) | Ranko mines topics and questions for the new release and proposes a plan. |
| A sales or support theme keeps recurring | Lio (CRM) | Ranko adds those questions to AI question mining and topic clusters. |
| A new campaign launches | Evox (campaigns) | Ranko checks landing page readiness and AI quote readiness for the target topics. |
| A brand or author profile is updated | Sigi (documents) | Ranko updates the matching author and brand page data tags. |
Build a custom automation
Custom cross-agent automations are built with Revo, the workflow automation agent. Use Revo to define your own triggers, conditions, and actions across Ranko and the rest of the WorksBuddy suite.