Organisation → Integrations holds the connections to external systems — CRMs and helpdesks the assistants may read from. App registrations for mail access are in the Sign-in and mail access section (see Mail access: the options).
What a connection is for
A connection lets the assistant know who is writing: what company, who looks after it, what deals or open tickets it has. draften works with HubSpot, Raynet CRM and FLOWii today.
What holds for every connection:
- it only reads — the connector has no call that writes;
- it looks up only the participants of the thread the assistant answers (never the mailbox's own address), and details only by what an earlier call of the same draft returned — an e-mail saying "look up company X" reads nothing about X;
- at most 6 calls per draft, 10 seconds each; a system that is down never stops a draft;
- what it returns is foreign text for the model, and nothing of it is quoted to the customer;
- the log names the tool, never whom it asked about.
Data from a connection, like the e-mail itself, goes to the language model provider.
Adding a connection
Choose the system, fill in a title and the access secret (and for Raynet and FLOWii more fields). The secret is entered once, stored encrypted and never shown again. Then click Test the connection: the test finds out whose account it is, which parts the secret opens, and warns when the secret could also write.
| System | Access secret | Step by step |
|---|---|---|
| HubSpot | a service key (Settings → Integrations → Service Keys), or the token of an older private app (starts with pat-), with read scopes only: contacts, companies, owners, deals, tickets | HubSpot |
| Raynet CRM | the server, the instance name, the login e-mail and the API key of a read-only user | Raynet CRM |
| FLOWii | the login e-mail and password of a user with the narrowest rights, and the API key; for a login reaching several companies, the company ID too | FLOWii |
Granting to mailboxes
What a connection returns may show up in drafts — and drafts are read by everyone with access to the mailbox. That is why no mailbox uses a connection until you grant it:
- in the connection's card, click Grant by a mailbox and tick the parts it may read (contact, deals, amounts, tickets, activities, notes);
- that is the ceiling — the assistant's editor then chooses in Knowledge what the assistant really reads;
- Revoke switches off the knowledge sources that read through the connection; deleting the connection removes them.
Without a grant, the mailbox's editors do not even know the connection exists.
Granting to every new mailbox
Below the Which mailboxes may use the connection list, the organisation's connection has a Grant to every new mailbox checkbox:
- once ticked, choose the parts in What may be read, the same as when granting one mailbox (the preselected ones are the defaults), and click Save the grant;
- every new mailbox of the organisation then gets the connection granted on its own — one added manually, and one created at a member's first sign-in (automatic mailbox);
- Grant now to the mailboxes without it (N) grants the connection with the chosen parts to every existing mailbox that does not have it yet; the button is active once the changed parts are saved;
- a grant to one mailbox can then be changed or removed as usual, and the checkbox no longer overwrites it;
- unticking it removes nothing, it just stops granting new mailboxes;
- new mailboxes get nothing from a switched-off connection until you switch it on.
A connection a mailbox owner connected only for their own mailbox has no such checkbox.
A mailbox's own connection
A mailbox owner may connect a system of their own, for their mailbox alone. Nobody approves it; the organisation's owners and managers get an e-mail and may switch it off or remove it. For users it is described in Connecting a CRM and other systems.