Pular para o conteúdo

Google Drive Trigger

Trigger your automations when files are created, updated, or removed in Google Drive. Typical workflows include summarizing newly uploaded content, enforcing sharing policies, or notifying owners when critical files change.

  1. Open your deployment in CrewAI AMP
  2. Go to the Triggers tab
  3. Locate Google Drive and switch the toggle to enable
Enable or disable triggers with toggle

The drive example crews parse the payload to extract file metadata, evaluate permissions, and publish a summary.

from drive_file_crew import GoogleDriveFileTrigger
crew = GoogleDriveFileTrigger().crew()
crew.kickoff({
"crewai_trigger_payload": drive_payload,
})

Teste sua integração de trigger do Google Drive localmente usando a CLI da CrewAI:

Terminal window
# Visualize todos os triggers disponíveis
crewai triggers list
# Simule um trigger do Google Drive com payload realista
crewai triggers run google_drive/file_changed

O comando crewai triggers run executará sua crew com um payload completo do Drive, permitindo que você teste sua lógica de parsing antes do deployment.

Track history and performance of triggered runs with the Executions list in the deployment dashboard.

List of executions triggered by automation
  • Verify Google Drive is connected and the trigger toggle is enabled
  • Teste localmente com crewai triggers run google_drive/file_changed para ver a estrutura exata do payload
  • If a payload is missing permission data, ensure the connected account has access to the file or folder
  • The trigger sends file IDs only; use the Drive API if you need to fetch binary content during the crew run
  • Lembre-se: use crewai triggers run (não crewai run) para simular execução de trigger