Integrations
Email and calendar
Connect the systems your day already runs on so Operator can prepare real work.
3 min read
Connect the systems your day already runs on so Operator can prepare real work. A connection is only useful in service of a workflow, so decide what you want Operator to carry first, then grant the access that motion needs.
What Operator can use it for
Access is granted per workspace and tied to the workflows that use it. With this connection in place, Operator can:
- read the conversations relevant to a connected workflow
- prepare replies and follow-ups for review
- use meeting context to prepare summaries and next actions
Common workflows
- inbox triage
- meeting follow-up
- Morning Brief
What context is relevant
- message content and participants for the workflows you enabled
- calendar events and attendees
Permissions and access
Access is scoped to the workflow you enabled and can be revoked at any time. Connect the narrowest access that lets the workflow work, not the broadest access the tool offers.
Good to know
Exact permission names differ per provider. Grant only the access the workflow requires and review it periodically.
Where approval happens
- every outgoing external message
- meeting invitations sent on your behalf
Human checkpoint
If an action would be awkward to undo, keep it behind an approval.
Disconnecting access
A connection can be removed at any time. Once removed, Operator no longer has access to that system and the workflows depending on it stop until the connection is restored.
The same connect, scope and revoke model applies to every system. How integrations work
Continue learning
Inbox and communications triage
Classify incoming messages, prepare replies and escalate only what needs a person.
4 min read
Meeting follow-up
Turn meeting context into summaries, CRM updates, drafts and next actions.
4 min read
How integrations work
Scoped access, connected per workflow and revocable at any time.
4 min read