Integrations
Messaging
Bring Operator into the channels your team already talks in.
3 min read
Bring Operator into the channels your team already talks in. 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:
- pick up requests made in a channel
- post prepared updates where the team will see them
- route an approval to the person who owns it
Common workflows
- approval routing
- Morning Brief delivery
- inbox and channel triage
What context is relevant
- messages in the channels you connect
- who sent them and when
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
- messages sent outside your workspace
- anything customer-facing
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
How approvals work
The checkpoint between prepared work and executed work.
4 min read
How integrations work
Scoped access, connected per workflow and revocable at any time.
4 min read