Connected tools
How a Customer connects its own outside tools to an App, what the App may do with them, and how the Customer takes the access back.
A Customer-scope Integration connects one Customer's own account at another tool to its Tenant. The App then acts in that tool on the Customer's behalf, with only the grants the Customer approved.
Connect
Integration.connect asks the account holder to approve the outside account and records the grants they approve. Harbor Residential connects its calendar, so each renewal's signing date lands on the manager's calendar.
The token is filled in at call time and never reaches an Agent or a screen. The App's code calls the Integration, never the tool directly, so the same call works for every Customer whatever tool it connected.
Keep it working
| Verb | When it runs |
|---|---|
Integration.refresh | Before the outside token expires; a refused refresh moves it to needsReauth |
Integration.reconnect | When the Customer re-approves, keeping its id and cursor, so nothing re-imports |
Integration.pause | When the Customer wants calls stopped, keeping token and cursor |
Integration.resume | To restart from the cursor and release each Action that waited |
An Integration in needsReauth shows on the Tenant's integrations screen until the Customer reconnects it.
Take it back
Integration.revoke ends the Integration at once and revokes the token with the outside tool. Every record it brought in stays in the Tenant, with its history.
Next
Audit log for admins covers what a Customer's admins see of every call.