What it is
When you connect a service to OpenBase, the connector brings its automations with it — the recurring tasks OpenBase should take on in that area. Inbox triage, mentions watch, a daily briefing from your calendar. You see each automation; you toggle each one individually.
What you can do
- Active on connect — Connect the service, automations are live. No settings tour.
- Visibility — On the connector page you see every automation of a service, plus its last-active time.
- Disable an automation — Right at the Canvas item it produced ("via Inbox triage / disable"). Two clicks, confirmed.
- Approval workflows for external actions — Reading is autonomous; writing (sending mail, posting in Slack) still goes through explicit approval.
- Reactive tools remain — Disabling an automation stops the proactive behaviour; the underlying tools remain available when you ask OpenBase in chat.
How it looks in the workspace
- Connect the connector — OpenBase shows which automations come with it.
- The automations run as soon as the observation window for the connector is reached.
- Results appear on the Canvas with a clear "via {automation}" attribution.
- If an automation becomes too much, switch it off. The mail or Slack capabilities in chat are unchanged.
Why it works in the enterprise
The hardest part of proactive AI is trust: what is it doing for me right now? Automations make it explicit — as named, revocable tasks with approval for external actions. No black-box heuristics, no "the AI just did that".
With which connectors
Slack, Google Workspace, Gmail, HubSpot, Jira, Asana and GitHub each ship their own automations — more connectors follow.
Ready for the AI workspace that knows your company?
Start for free