> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adside.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Upload Drive File to Meta

> Upload a file from Google Drive directly to Meta Ads Manager. Requires both Google and Meta channel connections.



## OpenAPI

````yaml /api-reference/openapi.yaml post /google/drive/upload-to-meta
openapi: 3.1.0
info:
  title: Multi-Source Ads API
  version: 1.0.0
  description: >-
    Unified API for managing ad campaigns across Meta, LinkedIn, and Google. MCP
    tools are accessed via JSON-RPC 2.0 over HTTP (`POST /{source}/mcp`). Google
    Sheets/Drive endpoints use standard REST.
servers:
  - url: https://api.adside.ai
    description: Production
  - url: http://localhost:3100
    description: Local development
security:
  - bearerAuth: []
tags:
  - name: Accounts
    description: ''
  - name: Ads
    description: ''
  - name: Analytics
    description: ''
  - name: Asset Groups
    description: ''
  - name: Assets
    description: ''
  - name: Audiences
    description: ''
  - name: Campaign Groups
    description: ''
  - name: Campaigns
    description: ''
  - name: Conversions
    description: ''
  - name: Creatives
    description: ''
  - name: Drive
    description: ''
  - name: Google
    description: ''
  - name: Google Ads
    description: ''
  - name: Google Tag Manager
    description: ''
  - name: Keywords
    description: ''
  - name: Linkedin
    description: ''
  - name: Meta
    description: ''
  - name: Meta Reporting
    description: ''
  - name: OAuth
    description: ''
  - name: Other
    description: ''
  - name: Reports
    description: ''
  - name: Sheets
    description: ''
  - name: Targeting
    description: ''
  - name: Tiktok
    description: ''
  - name: Workspace
    description: ''
paths:
  /google/drive/upload-to-meta:
    post:
      tags:
        - Google
        - Drive
        - Meta
      summary: Upload Drive File to Meta
      description: >-
        Upload a file from Google Drive directly to Meta Ads Manager. Requires
        both Google and Meta channel connections.
      operationId: google_drive_upload_to_meta
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - file_id
              properties:
                file_id:
                  type: string
                  description: Google Drive file ID to upload
                file_name:
                  type: string
                  description: Optional file name override for the uploaded Meta asset
      responses:
        '200':
          description: Upload result with Meta asset ID
        '400':
          description: Missing file ID or unsupported Drive file type
        '403':
          description: Meta channel not connected (both Google and Meta are required)
        '502':
          description: Google download or Meta upload failed
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key (sk_live_*) — SHA256 hashed, looked up in Redis. Generate via
        the web app's workspace settings.

````