Skip to main content

Build Automations

Automations let Subscriberbot act on your behalf. They combine events, policies, and the AI agents so that routine subscription decisions happen without you.

Policies​

A policy is a rule: a condition and an action. Policies are the simplest way to delegate authority.

mutation {
  subCreatePolicy(input: {
    name: "Cancel expensive unused subscriptions",
    when: "usage.idleDays >= 90",
    condition: "plan.monthlyPrice > 20",
    action: CANCEL
  }) { id }
}

In plain language: if a subscription has been unused for 90 days and costs more than $20/month, cancel it.

Workflows​

For multi-step logic, use a workflow that listens for an event and runs a sequence:

name: renewal-approval
on: RenewalDetected
when: amount > 500
steps:
  - create-task:
      type: approval
      assignee: finance
  - wait-for: approval
  - on-approve: { renew: $event.relationshipId }
  - on-reject: { cancel: $event.relationshipId }

Autonomy levels​

You choose how much authority to delegate. Every automated action is recorded as an event in the graph and is fully auditable.

LevelBehavior
NotifyThe agent only suggests; you act.
ApproveThe agent prepares the action and waits for your approval.
AutonomousThe agent acts within the bounds of the policy.

Common automations​

  • Auto-cancel unused trials before they convert.
  • Switch to annual plans where savings exceed a threshold.
  • Unsubscribe from low-engagement newsletters (for example, open rate under 5%).
  • Route every invoice to finance with an AI-generated classification.
  • Flag duplicate or overlapping tools for consolidation.

Next​

Environment selection

Automations run against production by default. For local development and testing, set BURDENOFF_ENV=local to use local gateways. See Environment Selection for endpoint details.