Events & the Workflow Engine
Subscriberbot is designed to be event-driven. Meaningful changes in the Relationship Graph are published as events, and a Workflow Engine turns those events into automated actions.
The event bus
Every significant change emits an event. Core event types include:
| Event | Emitted when |
|---|---|
SubscriptionCreated | A new Relationship is detected or created. |
RenewalDetected | An upcoming or recurring renewal is identified. |
InvoiceReceived | A new invoice arrives for a Relationship. |
TrialStarted | A free trial begins. |
TrialEnding | A trial is about to convert to paid. |
ChurnPredicted | The AI Brain predicts likely cancellation. |
The Workflow Engine
Workflows subscribe to events and run a sequence of steps. They are how "data changes" become "things that happen". Examples of workflows:
When an invoice arrives → classify it → update the subscription → notify finance.
When a renewal is due in 30 days → create an approval task.
When a subscription is cancelled → revoke access and archive its assets.
A workflow, illustrated
name: invoice-to-finance
on: InvoiceReceived
steps:
- classify: { using: ai-brain }
- update: { relationship: $event.relationshipId }
- notify:
channel: slack
audience: finance
How events relate to automations
The Autonomous Subscription Management policies and the agent framework are both consumers of this event bus. A policy such as "auto-cancel unused trials" is, under the hood, a workflow that listens for TrialEnding and evaluates usage before acting. See the Automations guide for how to build these.
Data platform
Events also flow into the Data Platform, which includes a subscription data lake, an analytics warehouse, the knowledge graph, an embedding store, and an AI memory store. Together these give the AI Brain both the history and the context it needs to reason well.