Integrations

Knobs

Mail and calendar from knobs.io, connected the same way as Google or Microsoft — with one extra step, because a Knobs workspace admin has to let OppFlow in before anyone can connect.

Knobs is a workspace suite with its own mail and calendar. As an email and calendar provider it behaves exactly like the other two: the workspace picks one provider, and then each person connects their own mailbox. Everything on Email & calendar applies here.

Two levels, not one

This is the difference worth knowing. Google and Microsoft let an individual consent on their own. Knobs does not: a Knobs workspace admin registers OppFlow first, and only then does a Connect button appear for anyone else. Until that happens the card shows not available with a link explaining what the admin has to do — deliberately not a Connect button that would fail.

Permissions

The connect flow asks for four scopes, in the Knobs vocabulary:

profile:read

Who you are, so the connection can be labelled with the right account.

mail:read

Threads involving contacts on your deals, for the activity timeline.

mail:send

Sending a draft you have reviewed. Nothing sends without you.

calendar:read

Meetings involving those same contacts.

Knobs also defines mail:modify. OppFlow never asks for it, so it cannot delete, move or relabel your mail.

Granted, not requested

What the connection can actually do is read from the scopes Knobs granted, not the ones OppFlow asked for. If a workspace policy withholds one, the card shows the reduced capability rather than claiming it works.

The workspace id

Knobs returns a workspace id alongside the tokens, and every Knobs route is scoped by it. That is why a connection is bound to one workspace: OppFlow cannot address a mailbox without knowing which workspace it lives in.

OppFlow.ai docs · by Traversal · v0.1.32