Click-through rate on your re-engagement Notifications dropped from 4.7% to 2.8% over the last 14 days, well below your 4.2% trailing average. The decline is concentrated on Android Players acquired through the May onboarding flow. Outcome data shows attributed purchases from push fell 34% in the same window.
An agent watches one thing and acts on it. Not a workflow, just a standing watch that usually does nothing and acts the moment it should.
An agent does what you'd do, and only what you've authorized.
It acts on the same governed metrics as your dashboards, and every action is logged and traceable.
It alerts and recommends on its own; anything that changes data is yours to approve.
Point a new agent at a throwaway channel and watch its judgment before it touches anything real.
It remembers what it already flagged and waits before acting again, so it won't alert you about the same thing twice.
It joins your OneSignal Outcomes and Notifications to your product usage and revenue data, so you see which campaigns and Player segments produce activated users and downstream spend, not just delivery counts. When a campaign that used to drive conversions goes quiet, you find out before the cohort churns.
When opt-in rates on a platform or Player segment start dropping faster than their baseline, it tells you which Applications are affected, how many active Players you are losing reach to, and whether the decline maps to a specific device type or acquisition cohort. You find out the week it shifts, not when the next send underperforms.
It watches Notification delivery and click rates across your Applications over time. When deliverability falls, a segment's tap rate drifts from its historical norm, or Outcome conversions drop without a corresponding change in send volume, it flags the gap and lines up the investigation for you to review before the next campaign repeats the problem.
Beyond alerts and write-backs, an agent can run arbitrary Python, so it can do whatever the task actually requires: call an API, kick off a job, reshape the data, or wire into your own tooling. The action space is yours to define.
You could rig one of these with a cron job and a Slack webhook in an afternoon. The watching is the easy part. Here's what you'd own forever, and don't, here:
Every OneSignal object, modeled and query-ready the moment you connect.
It runs on your real OneSignal account (test notifications, dormant players, inconsistent tags and all), not a tidy demo.
A message in the channel you choose, with the context and a button to act on it.
A summary in the inbox of the people who need to see it.
A payload to your own systems, to wire the agent into whatever you already run.
A flag written back to your warehouse for everything downstream to pick up.
Kick the question to Fi to investigate the why and propose the fix.
Expose it to your own agents and tools over MCP, and drive it from your stack.
Run it in your own VPC or fully self-hosted. Everything it does is pure SQL and Python you can inspect.
Fi is your AI analyst. It helps you build and customize everything in Definite, including the agents that watch and act.
Your AI analyst. Ask questions in plain English, and let it help you build and customize everything in Definite, including your agents.
Meet Fi →The watchers and actors. Once you've built one, it runs on its own, keeping an eye on what matters and acting the way you would.
Autonomous agents →