Automations are what Binee does for you. The results land in your Inbox.

Every automation is one of two kinds: a watcher, which reacts to incoming activity in your connected tools the moment something matches (and can also carry an action step, so Binee acts for you), or a scheduled report, which runs at a time you choose every day. The details are under Automations below.

Beside its kind, every automation has an audience, and each audience has its own results:

You make a team automation in the automation builder: under Deliver to, pick a shared Slack channel instead of your private one. Every automation row carries a visible Personal or Team tag, and every insight carries the tag of the automation that produced it. Both the Automations page and your Inbox have a Personal/Team filter, so you can look at just your own alerts or just what the team sees. Example: filter the inbox to Team before a standup to review only the findings your project channel also saw.

The tag is automatic, worked out from who can actually see the automation's findings: an automation counts as Team when its delivery channel has anyone in it besides you and Binee, and Personal otherwise, including a private alerts channel where it is just you and Binee. Binee rechecks the channel members each time the automation fires, so when a teammate joins your channel later, the automation shows up as Team on its own. The tag changes only the label and the filters, never where anything is delivered. A scheduled automation follows the same rule: point its delivery at a shared channel and it counts as Team, keep it to yourself and it stays Personal.

Team automations are how a team or a whole company gets a live insight stream with no extra setup: any member (or an admin) creates automations and points them at the shared channel. Example: a sales team invites Binee to its sales channel and points two team automations at it, one flagging incoming payment and invoice emails, one flagging clients who sound unhappy or mention escalation. Everyone in the channel sees each payment update and escalation as Binee finds it.

You create and manage automations on the Automations page in the sidebar. A compact strip under the header holds the "Automations are on for you" switch, your daily budget with live usage, and links to delivery preferences and help. Turning the master switch off stops everything from running while keeping every automation editable; the per-automation on/off toggles freeze at their positions until you turn it back on, and everything then resumes exactly as you left it. You can still create new automations while it is off: after saving, Binee offers to turn the master switch on for you, or the automation simply waits. Below it, all your automations sit in one list as rows: each row shows the automation's sources and delivery, an on/off toggle, when it last found something, and how many findings it produced this week. For workspace owners and admins the same list also holds teammates' automations, but only the ones leadership built for them and team automations; a teammate's personal, self-built automations stay private to their owner, admins included, because an automation's configuration can itself be sensitive. Teammate rows are marked "For" that person and show status only, never findings. The list can be filtered by kind (watchers or scheduled), by audience (personal or team), by status (active, paused, needs attention, waiting for approval, declined), by whether the automation takes action, and by whose automations they are. Pressing New automation opens a chooser, the same pattern as new dashboards: start from a ready-made template, describe what you want in Binee Assistant (Build with AI), or build it yourself from a blank form. Templates are suggested for the tools you have connected, one click opens the template in the builder with everything prefilled and editable, and Browse all templates lists the whole library with trigger and source filters. The builder itself reads top to bottom in the order you think: the name and who it is for, then the sources it watches, then the trigger, either "When something happens" (a watcher) or "On a schedule" (a daily report at your time), with the "What should Binee watch for and tell you about?" wording right under it, then the optional "Then Binee does" action step, then delivery, with the urgent switch last. The builder keeps a draft as you type: clicking outside by accident loses nothing, the next blank New automation picks up where you left off, and Start over clears it (starting from a template replaces the draft, since you just made a fresh choice). You can also create, edit, pause, or resume an automation straight from chat, on the web or in Slack: describe what you want to be told about in your own words, and Binee shows a confirmation card with exactly what it will watch (name, instruction, sources, delivery) before anything is saved. A confirmed automation lands in the same automation list as one built on the page, and saying "pause my meeting recaps" or "change that automation to also watch my email" in chat works the same way, with a confirmation card first. The Binee Assistant button at the top of the app opens the same Binee chat beside any page, the Automations page included, so you can create or edit an automation, or ask about a finding, right beside the list; an automation confirmed in the assistant shows up in the list without a reload. The assistant keeps your conversation while you move between pages and starts a fresh one after several hours of quiet or when you close the tab; its history button lists your earlier assistant chats to pick back up, and they all live on the All Chats page too. Example: say "after my sales meetings send me a recap" in chat; if you have also saved the preference "negative client intent matters most to me", every recap leads with how the client sounded, while a teammate watching the same meetings gets a plain recap.

Every automation has exactly one owner: it runs on that owner's connections, reports only to them, and one member's insights never land in another member's feed. Owners and admins can build or transfer an automation for a member (see Building an automation for a teammate below), but it does nothing until that member approves it. Every automation is either:

A watcher automation can do more than notify: it can carry an optional action step, "Then Binee does", that runs the moment the automation fires. Example: "When a client emails asking for new work, create a task in my ClickUp Client requests list with the email summarized" - the insight tells you what was found, and the ClickUp task is already waiting in the list. You write what Binee should do in plain words and press Add actions: Binee turns your text into separate, clearly worded action items listed below, each with the abilities it needs already worked out. Review the list, uncheck or remove any item, and describe more to add more - one watcher can carry several actions. Anything your text asks for that Binee cannot do yet is said plainly instead of silently dropped. Reopening a saved automation shows its action step as one item; to restructure it, remove the item and describe the step again. The same works in chat: "warn me when a client email asks for new work, and then create a ClickUp task for it" stages one confirmation card showing both the watching and the doing.

Acting always starts with your explicit permission. Saving an automation with an action step shows a popup naming exactly what Binee may do, and nothing acts until you allow it. Actions run only on your own connections, at most 3 per firing, and every insight from an acting automation carries a "What Binee did" line saying exactly what happened, including when an action failed. Editing the action step asks for your permission again, and removing it turns the automation back into notify-only. Both kinds can act: a watcher acts the moment it flags something, and a scheduled automation acts right after its daily report is produced. Example: a daily client activity report whose action step opens a ClickUp task for each client reply still owed by the end of the day.

When an owner or admin builds an automation with an action step for you, your approval covers the actions too: the review shows what Binee would be allowed to do, in the same editor. Always approve never covers actions - an automation that acts always asks you personally, even with the standing permission on.

Each completed action uses about 1 extra credit on top of the automation's normal firing cost (see Cost and the daily budget below).

Workspace owners and admins can build an automation for another member, for the colleague who wants Binee watching for them but will not set it up themselves. In the automation builder, pick the teammate under "Who is this automation for?", write the automation as usual, and send it. Example: an operations lead builds the account manager an automation that flags when a client asks for new work by email while that client's invoices sit unpaid; the account manager approves it once and gets those warnings from then on. The same works in chat: "build Scott an automation that warns him when a client email sounds unhappy" stages the usual confirmation card, then saves the automation for Scott. A name that matches any teammate always means the teammate, even one who shares your name (say "for me" when you mean yourself), and when several teammates match a name, Binee asks which one you mean, telling them apart by email. Scheduled automations can be built for a teammate the same way.

Approval is what keeps this safe. An automation built for you does nothing until you approve it: a "Pending your approval" card appears at the top of your Automations page naming who built it and what it would do, and pressing Review opens the automation in the normal automation editor, with "From" the builder at the top. Change anything you like, the wording, the sources, the urgency, and answer right there: Approve and activate (which saves your edits and approves exactly what you see), Always approve, or Decline. You are told it is waiting on three surfaces so it is never missed: a "Needs your approval" card in the notification bell at the top of the app whose "Go approve" button opens that review right where you are, on any page, so you can answer and keep working (it counts into the bell's badge until you decide), an email, and a message in your private Binee channel on Slack when your Slack account is linked. These notices are transactional, they always send and no notification setting turns them off, because the automation cannot do anything until you answer. Once an automation runs, it runs on your own connected tools and its findings go to you, like any automation you built yourself, and you can edit, pause, or delete it like any other. Automations a teammate built for you keep a "By" marker in your list, and a "Built for me" filter shows just those.

Always approve is a standing permission: after a confirmation popup, automations your workspace owners and admins build, update, or transfer to you activate immediately, without asking each time, and you get an FYI notification instead of a request. A line above your automation list shows when this is on, and "Require approval" next to it turns it back off anytime.

Declining does not erase the request: the automation disappears from your list, and the builder sees a Declined status on that automation's row in their list. They can fix what was wrong and press "Send again", which sends it back to you for a fresh approval, or withdraw it. Builders are not build-and-forget either: they can edit an automation they built at any time. Editing an automation you already approved sends it back to you for approval and pauses it until you answer (unless you chose Always approve, in which case the change applies right away and you are notified). A builder can also pick sources the teammate has not connected yet: the builder sees a clear warning naming the missing tools, the automation can still be sent, and it starts watching those sources once the teammate connects them in Settings, Integrations.

So the builder can pick sources that will actually work, owners and admins can see which tools each member has connected and whether each connection is healthy. That is names and health only, for example "ClickUp connected, Google expired", never any content from those tools.

Owners and admins can transfer any automation to a different member, from the transfer button on a teammate's automation row or from the automation's own edit window (the "Transfer this automation" section). A transferred automation becomes the new owner's automation in every sense: it waits for their approval, then watches their own connected tools and reports to them, and the previous owner stops receiving it. Nothing needs re-wiring, because an automation is an instruction, not a connection: it always runs on its current owner's tools. Transferring an automation to yourself claims it and activates it right away. A claimed automation that carries an action step keeps the step off until you approve it yourself from the automation's editor, since actions now run on your connections. Example: the operations lead who built all the client-risk automations hands one to the new account manager; the account manager approves once and the warnings follow the account, not the person who left.

Everyone sees their own automations' health right in the automation list: an automation that cannot fire shows a "Needs attention" note naming exactly what to fix, for example a source tool you have not connected yet. For owners and admins the same list also holds the teammate automations they may see (leadership-built and team automations, never a teammate's personal self-built ones) with the same honest health states (active, paused, waiting for approval, declined, or needs attention, with the reason spelled out), each marked with who it runs for, plus a transfer button. That is configuration and health only; what an automation finds still goes only to its owner. The Filters button narrows the list by type, status (needs attention included), or person, and shows a live count next to each choice. Example: filter to "Needs attention", spot that a teammate's deadline automation went quiet because their ClickUp connection expired, and nudge them to reconnect before a client date promised by email slips.

Binee seeds a few preset automations when you first turn insights on. Presets are ordinary automations: you can edit, pause, or delete them, and restore them later with Restore Binee preset automations. Deleting an automation is permanent (Binee asks first); presets can always be restored.

Each automation has its own urgent flag. Urgent automations deliver through your urgent notification channels; everything else uses the regular channels.

An insight is a finding Binee flags from real events, like a stalled task or a thread that needs attention. Every insight cites the actual events it is based on; Binee refuses to store a finding it cannot back with evidence.

When an automation combines several sources, Binee cross-checks the others before it writes the finding: it looks up the people involved in your business graph and pulls in their related work and conversations, so the insight arrives with the check already done. Example: an automation saying "tell me when a client complains about a delivery in a meeting, and check it against our tasks" produces one insight that quotes the complaint from the meeting and shows next to it that the related task really is overdue, with both cited as evidence. A cross-check that finds nothing, or cannot run, is said plainly in what the insight relies on, never papered over.

For meeting recordings, Binee reads the full transcript of each new meeting, not just the recording tool's own summary. What it keeps from the transcript is guided by your active automations in your own words: if your automation says negative client intent matters most, that is what gets noticed and quoted. Tone, hesitations, and side remarks that vendor summaries drop are exactly what this catches. The raw transcript itself is never stored; Binee keeps only the short extract it needs.

New insights appear in the notification bell at the top of the app (which also pins any automation waiting for your approval above the feed), and the Inbox page in the sidebar is where you process them. It has four tabs: Open (what needs you, urgent pinned on top), Snoozed, Done, and All. On each insight you can mark it Done, snooze it (until tomorrow, for a week, or until new evidence - that last one wakes the insight when the same automation finds something new), or mark it Not useful with a reason. Done insights are never deleted; the Done tab keeps the full history. You can filter every tab by the automation that produced a finding or by its evidence source, and select several insights to mark Done together. The bell stays the quick entry point.

Marking an insight Not useful teaches the automation that produced it: pick a reason (wrong match, not urgent, already knew) and Binee uses your recent feedback to settle borderline calls for that automation going forward. Example: mark two "task slightly delayed" findings as not urgent, and that automation stops flagging small slips while still catching the delay that breaks a date you promised a client by email. Your instruction always outranks feedback. Your feed is personal: read, snoozed, and done states belong to you, and no other member sees your feed. Each insight names the automation that found it, so you always know why it appeared. Team insights additionally post to their automation's shared channel, where everyone in the channel sees them.

You can mark insights read one by one, or all at once: both the bell and the Inbox have a "Mark all as read" button (on the Inbox page it sits next to the filters). It marks every unread insight read, regardless of which filters are active. In each list, a red dot marks an urgent insight and a purple dot marks everything else; a bold title means you have not read it yet.

The delivery matrix lives in Settings, then Notifications, in the Insight notifications section. It has two rows (Urgent, and Everything else) and three columns: In-app, email, and Slack. In-app is always on and shown as such: your Inbox is the record of what your automations found, so it can never be silenced by accident (to stop an automation entirely, pause it on the Automations page). By default, urgent insights also go to both email and Slack, and everything else goes to Slack only. Slack here means your own private Binee insights channel and requires a connected Slack. Team automations are different: their insights are always posted to the shared channel they target, regardless of the matrix, because delivering there is the automation's own job. Scheduled automations email their reports through the Everything else row unless the automation is marked urgent. The unsubscribe link in an insight or report email flips the matching email toggle here, exactly as if you had turned it off on this page; the automation itself keeps running and its results keep landing in your Inbox.

There is also a master switch per member, the "Automations are on for you" switch on the Automations page. Even with notification channels off, insights still appear in the app.

The urgent flag also controls how fast Binee reacts. When any of your active automations is marked urgent, new email is checked the moment it arrives, wherever your email provider can notify Binee instantly; inboxes on providers without instant notifications are picked up on the next 15-minute pass. Everything else is checked in batches every 15 minutes, which keeps watching efficient enough to stay free. Example: an automation marked urgent that watches for a client threatening to cancel gets checked seconds after the email lands when instant notifications are available, while a regular automation that connects overdue ClickUp work to promises made by email catches up on the next 15-minute pass.

Some sources are checked by polling on your behalf, at a pace that respects your own account's limits in that tool. Meeting recordings work this way: Binee checks for newly processed meetings about every hour, and only while you have an active automation watching that source, so your account's API budget is never spent on watching you did not ask for. A meeting becomes an event once its AI summary is ready, which is usually a few minutes after the meeting ends.

Customer invoices are also checked by polling, a few times a day, and only while you have an active automation watching that source. An invoice becomes an event when it goes past its due date while still unpaid, so an automation like "warn me when a client's invoice goes overdue, and check whether they emailed us recently" fires within a day of the due date passing, with the customer's related conversations cross-checked into the finding. Invoices that were already overdue before you created the automation are not flagged retroactively; ask in chat for the current overdue list instead, and you get it with the amounts still owed.

One deliberate exception: while a ClickUp Setup build is running (and for about 10 minutes after), Binee does not watch ClickUp events in that workspace. A build creates many lists, docs, and tasks in quick succession, and those are Binee's own writes, not your team's activity. Watching resumes automatically.

The same principle applies to email: the notification emails Binee itself sends you, like insight alerts, are not treated as new events. When one lands in a watched inbox, Binee recognizes its own sending address and skips it, so an alert about a client email can never trigger a duplicate alert about itself.

Watching is free: the matching step that checks incoming events against your automations costs nothing. When an event matches and Binee runs a full investigation, that firing costs a flat 1.3 credits. An automation with an approved action step additionally uses 1 credit per completed action, at most 3 actions per firing, so an acting automation's most expensive possible firing is 4.3 credits; the builder says this before you approve the step, and only completed actions are charged. When the workspace balance is too low to cover actions, the action step is skipped for that firing and the insight says so; the finding itself still arrives.

To keep a busy day from burning through credits, each member has a daily budget: the number of paid firings Binee may run for you per day. It defaults to 50 and you can set it anywhere from 1 to 500 at the top of the Automations page. When your budget is reached, your insights pause for the rest of the day (measured in UTC) and resume the next day. Your budget is yours alone; hitting it never pauses a teammate.

If the workspace runs out of credits entirely, new insight firings pause honestly until credits renew or are topped up. Nothing is deleted, and everything resumes once the balance is back to at least 1 credit.