> ## Documentation Index > Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt > Use this file to discover all available pages before exploring further. # Link reference documents from Google Drive > Attach files the signed-in user picked in the Google Picker. Each is fetched with that user's own drive.file grant, read in the background and summarized. A file that is already linked is returned as its existing document. ## OpenAPI ````yaml /openapi.json post /ai-context/documents/drive/ openapi: 3.1.0 info: contact: email: support@getoneprofile.ai name: Oneprofile Support description: >- REST API reference for Oneprofile, the GTM data layer for your CRM. Manage tables, enrichments, and integrations. Authenticate with an API key to get started. termsOfService: https://www.getoneprofile.ai/terms title: API Reference | Oneprofile version: '0.0' servers: - url: https://api.getoneprofile.ai security: [] tags: - description: >- The Getting started checklist: a workspace's progress through the six steps from its first people search to its first launched sequence. name: onboarding - description: Sender profiles, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - description: >- The LinkedIn channel: connecting an account to a sender, its safety limits and history, and the protocol the browser extension speaks. name: linkedin - description: 'The unified outreach inbox: threads, replies, labels, events.' name: inbox - description: 'The AI reply layer: workspace settings, drafts, and approval.' name: inbox-ai - description: Notification rules, per-user preferences, and the Slack connection. name: notifications - description: Endpoints for seeing all available integration types. name: integration-types - description: Endpoints for creating and managing integrations. name: integrations - description: Endpoints for the generic OAuth install/claim app-listings engine. name: app-listings - description: Endpoints for creating and managing API keys. name: apikey - description: Endpoints for managing billing and subscription information. name: billing - description: Endpoints for creating and managing tables. name: tables - description: Endpoints for table columns, formula previews, and on-demand column runs. name: table-columns - description: Endpoints for table rows and manual cell edits. name: table-rows - description: Endpoints for observing and cancelling table recompute runs. name: table-runs - description: >- Endpoints for org-shared per-column display preferences: hidden, pinned, width, and colour tint. name: table-ui-prefs - description: >- Endpoints for the org-shared names given to the column tint palette: what this organisation calls each colour. Org-level, not per-table. name: table-column-color-labels - description: >- Endpoints for the enrichment action catalog, model list, presets, draft generation, and saved agents. name: table-enrichments - description: >- Endpoints for teaching a saved agent from example rows: training sessions, per-row feedback, and the proposed prompt to approve. name: agent-training - description: >- The durable audit trail of a table's enrichment actions: configured, edited, run, cancelled, and settled cost. name: table-enrichment-audit-logs - description: Endpoints for saving and applying column templates. name: table-templates - description: Server-sent change feed for a table's grid. name: table-events - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.' name: table-views - description: >- The per-table AI Assistant: named conversations, the column suggestions a build turn produces, and the questions an analyze turn answers. name: table-assistant - description: >- Endpoints for PER-USER table preferences: favourites and recently opened. Unlike the rest of the table surface these are personal, so two members of one organisation legitimately see different answers. name: table-user-prefs - description: >- Endpoints for building a table from an uploaded CSV: upload and preview the inferred columns, commit the reviewed mapping, then poll the row load. name: table-imports - description: Endpoint for downloading a table's rows as CSV. name: table-export - description: >- Endpoints for the integration a table imports from: attach and preview it, promote imported fields into columns, and run the import on demand. name: table-sources - description: >- Endpoints for a table's recurring import cadence: set it, pause it, and read the next fire times. name: table-schedules - description: >- Endpoints for pushing a table's rows out to a connected integration: list writable destinations, derive their write capabilities, and map export columns. name: table-writeback - description: >- Endpoints backing a lookup column's setup: the connections whose records a column could read, and the identity fields one record type can be looked up by. name: table-integration-lookup - description: >- Endpoints for sourcing leads from the lead database: count and preview matches, land them in a table, and keep saved searches. Alongside people and company searches, leads can be sourced from buying signals — what a company or person just did — with a catalogue endpoint behind the picker that builds them. name: find-leads - description: >- Endpoints for discovering a domain's subdomains from public certificate logs and landing the results in a table. name: find-subdomains - description: Endpoints for the credit balance meter and usage reporting. name: credits - description: >- Endpoints for the workspace referral program: the shareable link, the friends who joined through it, and claiming a code after signup. name: referral - description: >- Endpoints for the affiliate program's own dashboard: enrolling and claiming a code, the summary, stats and activity feed, the commission ledger, and identity verification and payouts. name: affiliate - description: >- Endpoints for the design partner program's customer surface: whether this workspace is a design partner, the badges its feedback has earned, and sending and reading that feedback. name: design-partner - description: >- Endpoints for the org-level AI business context — company description, ideal customer profile, buyer personas, interest signals and social proof — plus domain-based generation and the reference documents whose summaries ride alongside those fields. name: ai-context - description: >- Endpoints for the signed-in user's Google Drive connection: starting and finishing the OAuth grant, checking or dropping it, and minting the short-lived token the Google Picker needs. name: google-drive paths: /ai-context/documents/drive/: post: tags: - ai-context summary: Link reference documents from Google Drive description: >- Attach files the signed-in user picked in the Google Picker. Each is fetched with that user's own drive.file grant, read in the background and summarized. A file that is already linked is returned as its existing document. operationId: link_ai_context_documents_from_drive requestBody: content: application/json: schema: $ref: '#/components/schemas/AiContextDriveLinkRequestSchema' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/AiContextDocumentsCreatedSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: >- Drive is not connected, a file cannot be reached, or the workspace is full. '500': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Internal server error. '502': description: Google rejected the token refresh; the grant is gone. '503': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Service unavailable. security: - APIKeyHeader: [] - HTTPBearer: [] components: schemas: AiContextDriveLinkRequestSchema: description: Request body for linking files picked in the Google Picker. properties: file_ids: description: Drive file ids from the Picker, in the order they were picked. items: maxLength: 255 minLength: 1 pattern: ^[A-Za-z0-9_-]+$ type: string maxItems: 25 minItems: 1 title: File Ids type: array required: - file_ids title: AiContextDriveLinkRequestSchema type: object AiContextDocumentsCreatedSchema: description: The documents a Drive link created, in the order the files were picked. properties: documents: items: $ref: '#/components/schemas/AiContextDocumentReadSchema' title: Documents type: array required: - documents title: AiContextDocumentsCreatedSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object ForbiddenResponse: properties: detail: description: The detail of why the request is forbidden. title: Detail type: string required: - detail title: ForbiddenResponse type: object UnprocessableEntityResponse: properties: detail: description: >- The detail of the error. This is the error message to show to the user. You should also use the issues field to show more detailed error messages per field. Use this field for a single liner error message. title: Detail type: string issues: description: >- The issues that caused the error. There can be multiple issues. Each issue is a user-facing error message. items: $ref: '#/components/schemas/UnprocessableEntityIssue' title: Issues type: array required: - detail - issues title: UnprocessableEntityResponse type: object ServerErrorResponse: properties: detail: description: The detail of why the server returned an error. title: Detail type: string required: - detail title: ServerErrorResponse type: object AiContextDocumentReadSchema: description: >- One reference document: what it is, how far it got, and what prompts read. properties: content_type: title: Content Type type: string created_at: format: date-time title: Created At type: string drive_file_id: anyOf: - type: string - type: 'null' title: Drive File Id drive_web_view_link: anyOf: - type: string - type: 'null' description: Where to open the original in Google Drive, for linked documents. title: Drive Web View Link error: anyOf: - type: string - type: 'null' description: Why the document could not be read, written for the reader. title: Error filename: title: Filename type: string id: format: uuid title: Id type: string in_prompt_budget: default: true description: >- Whether this document's summary actually fits the prompt budget alongside the documents before it. Computed on the list; a single read reports true. title: In Prompt Budget type: boolean included_in_context: description: Whether this document's summary joins the business context. title: Included In Context type: boolean size_bytes: title: Size Bytes type: integer source: $ref: '#/components/schemas/AiContextDocumentSource' description: Whether the file was uploaded or linked from Google Drive. status: $ref: '#/components/schemas/AiContextDocumentStatus' description: Poll the list while any document is still `processing`. summary: anyOf: - type: string - type: 'null' description: The markdown summary that stands in for this document in AI prompts. title: Summary summary_edited: description: True once somebody saved over the written summary by hand. title: Summary Edited type: boolean summary_generated_at: anyOf: - format: date-time type: string - type: 'null' title: Summary Generated At title: title: Title type: string updated_at: format: date-time title: Updated At type: string required: - id - source - status - error - title - filename - content_type - size_bytes - summary - summary_edited - summary_generated_at - included_in_context - drive_file_id - drive_web_view_link - created_at - updated_at title: AiContextDocumentReadSchema type: object UnprocessableEntityIssue: properties: input: anyOf: - type: string - type: integer - type: number - type: boolean - items: {} type: array - additionalProperties: true type: object description: The user's input that caused the error. title: Input loc: description: >- The location of the error. Always contains 1 or 2 elements. The first element is the type of location (e.g. 'body', 'query', 'path', 'header'). The second element is the name of the field that caused the error. If the error is not related to a specific field, the second element is not present. items: type: string title: Loc type: array msg: description: The message of the error. The error message to show to the user. title: Msg type: string type: description: >- The type of the error. Useful for frontend code to handle different types of errors. title: Type type: string required: - loc - msg - type - input title: UnprocessableEntityIssue type: object AiContextDocumentSource: description: Where a reference document came from. enum: - upload - google_drive title: AiContextDocumentSource type: string AiContextDocumentStatus: description: >- How far a reference document has got through extraction and summarizing. Unlike a generation job, ``PENDING`` IS observed here: the row commits first and its workflow starts after that commit, so a reader can catch the gap. The two terminal states are absorbing. enum: - pending - processing - ready - failed title: AiContextDocumentStatus type: string securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey HTTPBearer: scheme: bearer type: http ````