Customer success

Connect Drive Folder

Map a folder in the organisation's Google Drive to this client. OWNER/ADMIN.

Uses the Workspace connection the organisation already has - no new grant is made. Mapping the same Drive folder again UPDATES it, and mapping a different folder to the same Library folder REPLACES that mapping. A sync is queued straight away so the files start importing. 400 when the company is not an active client.

post/customer-success/companies/{company_id}/drive-folder

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/customer-success/companies/{company_id}/drive-folder
  • Auth: HTTP bearer

Path parameters

company_idstring required

Company id.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

folder_idstring required

Google Drive folder id.

folder_namestring required

Folder name, as shown in Drive.

local_folder_keystring nullable

Which Library folder the files land in. Derived when omitted.

local_folder_namestring nullable
library_folder_idstring nullable

Library folder id. REPLACES any other mapping to the same Library folder.

library_folder_pathstring nullable
labelstring nullable

Response

Successful Response

dataOrgPayload required

An open envelope for a single role, team, member or account record.

Open on purpose. The app's own response models on this surface grow with the product - RoleResponse gained rep_limits and manages_role_slugs, TeamResponse gained channel counts and a campaign count - and a pinned mirror would SILENTLY DROP whatever it had not caught up on. A dropped permission in a role read is the worst possible kind of stale: it reads as "they do not have it".

Changes

No recorded changes to this operation across all 2 revisions of this API.