- Cómo empezar a usar Airtable
- Introducción a los aspectos básicos de Airtable
- Cómo comunicarse con el equipo de soporte de Airtable
- Pantalla de inicio de Airtable
- Glosario de terminología de Airtable
- Airtable technical requirements
- Diferencias entre las funciones de Airtable para escritorio y para móvil
- Atajos de teclado de Airtable
- Cómo usar Markdown en Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Automatizaciones de Airtable
- Descripción general de automatizaciones
- Guías de automatizaciones
- Guías de automatizaciones integradas
- Guías de automatizaciones en Airtable
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Desencadenantes de automatizaciones
- Desencadenantes de Airtable
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Desencadenante de automatización de Airtable: cuando se actualiza un registro
- Airtable automation trigger: When record enters view
- Desencadenante de automatización de Airtable: a una hora programada
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received
- Desencadenantes integrados
- Desencadenantes de Airtable
- Acciones de automatización
- Acciones en Airtable
- Acción de automatización de Airtable: enviar correo electrónico
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Acción de automatización de Airtable: ejecutar un script
- Airtable automation action: Generate with AI
- Acciones integradas
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Acciones en Airtable
- Bases de Airtable
- Using Airtable Cobuilder
- Descripción general de las bases de Airtable
- Creating and duplicating bases in Airtable
- Structuring your Airtable bases effectively
- Moving Airtable bases between workspaces
- Tables in Airtable
- Crear enlaces para compartir bases de Airtable
- Importing third-party data into Airtable
- Uso de las perspectivas
- Troubleshooting Airtable base performance
- Versiones beta de Airtable
- Colaboración en Airtable
- Asistencia de Airtable Enterprise
- Información general
- External badging in Airtable
- Creating and using Airtable components
- Ask an Expert beta overview
- Data residency at Airtable
- Descripción general de los grupos de usuarios en Airtable
- API de Enterprise de Airtable
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Acceder a los registros de auditoría de Enterprise en Airtable
- Configuración de Jira Server/Data Center para conectarse con Airtable
- Panel de Administración de Enterprise
- Descripción general del panel de administración de Enterprise
- Usuarios: panel de administración de Enterprise en Airtable
- Detalles del usuario en el panel de administración de Airtable
- Grupos: panel de administración de Airtable
- Espacios de trabajos: panel de administración de Enterprise de Airtable
- Bases: panel de administración de Enterprise en Airtable
- Interfaces: Panel de administración de Enterprise en Airtable
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Informes: panel de administración de Enterprise en Airtable
- Airtable admin panel settings
- Guía práctica de Enterprise
- Gestionar a los admins de Enterprise en el panel de administración
- Uso de organizaciones
- Organizational branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub : Org unit assignment with user groups
- Desactivar, retirar el acceso y reactivar usuarios desde el panel de administración
- Gestionar el acceso de usuario a espacios de trabajo y bases
- Airtable Enterprise Key Management
- Custom terms of use
- SSO en Enterprise
- Información general
- Extensiones de Airtable
- Descripción general de las extensiones
- Extensiones por Airtable
- Extensiones integradas
- Campos de Airtable
- Descripción general de los campos
- Archivo adjunto
- Campos basados en fecha
- Fórmula
- Empezar a usar fórmulas
- Fundamentos de fórmulas
- Soluciones frecuentes: principiante
- Soluciones habituales: intermedias
- Soluciones habituales: avanzado
- Campo de texto largo
- Campos de registros vinculados
- Campos con números
- Otros campos
- Campos de compilación, búsqueda y recuento
- Campos de selección y colaborador
- Integración con Airtable
- API
- Getting started with Airtable's Web API
- Crear tokens de acceso personal
- Airtable Webhooks API Overview
- Service accounts overview
- API web de Airtable: usar filterByFormula o parámetros para ordenar
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- Enforcement of URL length limit for Web API requests
- Servicios de integración
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Herramientas para desarrolladores
- API
- Diseñador de Interfaces de Airtable
- Descripción general
- Diseños de página
- Elementos
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Aprendizaje y recursos
- Gestión de Airtable
- Política de Airtable
- Registros de Airtable
- Sincronización de Airtable
- Vistas de Airtable
- Espacios de trabajo de Airtable
- Impresión
- Compartir
- OscuroLigero
- PDF
Airtable automation trigger: Google Workspace
- Actualizado en 14 Aug 2024
- 6 Minutos para leer
- Impresión
- Compartir
- OscuroLigero
- PDF
Plan availability | All plan types with varying limitations |
Permissions |
|
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading | Creating an automation - Learn how to set up your first automation in Airtable. |
Note
As part of our Automations feature, a series of triggers for Google users can be set up in Airtable to automate common tasks or workflows associated with your Google account. If you are unfamiliar with the Automations feature, then we strongly recommend reading the Creating an automation support article before diving in.
Account authorization
As a prerequisite, you will need to already have a Google account. This account will need to be connected to the Airtable base that you are working in. After choosing which trigger you would like to set up, you will have the option to "Manage connected accounts" or "Connect new account". This authorization process is scoped to each individual Google service, so you will need to perform this process multiple times, at least once for each Google Workspace trigger, and also for reauthorizations in the future as needed.
Google Calendar triggers
Note
All Google Calendar triggers will return a Google Calendar Event ID. A Google Calendar event's ID is a unique identifier returned from Google Calendar for that event. If you intend to update a Google Calendar event at any point, we recommend storing the Google Calendar Event ID on your table. Note, that this ID is different from an Airtable Record ID, which is a unique identifier for an Airtable record.
There are currently three Google Calendar triggers to consider using in Automations:
When event created
When event changed
When event cancelled
Note
To track all changes in a Calendar, you'll likely need to set up 3 different automations, one for each Google Calendar trigger listed above.
Each of the Google Calendar triggers requires the same general setup process. You'll need to:
Pick which trigger you want to use
Connect your Google account (or select an already connected account)
Select a calendar that will trigger this automation
Pick an event and Run a test to make sure the connection is configured correctly (at least one event will need to be present in the calendar you selected to be able to test)
After successfully testing a Google Calendar trigger, you are ready to move on to some action steps. Consult below for more information about each trigger type.
Google Forms trigger
For Google Forms, we currently provide one Automation trigger option. Select the “When a response arrives” trigger from the list of available triggers. Then follow these setup steps to connect to the right Google account.
Note
You need to use the “Select response destination” setting in your Google Form and designate a spreadsheet to use to collect response information. For help on this, please visit this support article from Google for more details.
Next, connect to your Google Forms account, and select the spreadsheet and worksheet where your form responses are populating.
Then, run a test to make sure the connection is configured correctly (at least one form response will need to be already submitted to test the connection).
Note
The trigger will only detect rows that are added to the bottom of the spreadsheet. For example, if 3 rows were deleted from the spreadsheet and 3 more were added to replace them, then we wouldn't detect the 3 new rows. However, we would detect an additional 4th row or any subsequent submissions (rows) after that.
Google Sheets trigger
Note
The same row trigger rules apply as outlined in the note at the end of the section on the Google Forms trigger listed just above ^.
There is currently one Google Sheets trigger to choose when setting up an automation. Select the “When row created” trigger from the list of available triggers. Then follow these setup steps to connect to the right Google Sheet:
Connect your Google account (or select an already connected account)
Select a spreadsheet Select a worksheet (the worksheet must have column headers)
Run a test to make sure the connection is configured correctly
Note
The trigger on this automation is designed to run quickly after a new row has been created in a Google Sheet. If the row hasn't been entirely filled out at the time the automation triggers/runs, it may miss important information and not pull it into your Airtable table. This explains why you're able to retroactively test records successfully and pull them from Google into Airtable, yet the automation is unable to capture all of the information contained in a Google Sheet's row in live automation runs.
Add an action
After you’ve configured and tested the Google Workspace trigger, it’s time to add an action.
Action steps example:
For this example, we'll use the example of finding and updating the corresponding record for a Google Calendar event that has been changed or canceled. So to do this we need to do two actions:
Find the record that corresponds to the Google Calendar event.
Update that record with the new details from the triggering Google Calendar event.
This is where the field we created holding "Google Event ID" comes in handy! We can use the "Find record" action to find the record with the same Google Calendar Event ID as the one from our Google Calendar trigger.
Now that we have found our record it's time to update it. We'll use the "Update record" action to update the record we just found with the new information from our Google Calendar trigger:
Then we can update all our fields from our original calendar. Here is what it looks like together:
You don't need to update the Google Event ID because that ID won't change—it is still a unique identifier for this event.
Note
While updating an existing calendar event, if you specify a field and do not input a value for that field, the automation will assume you'd like that field empty within the updated event.
Test and enable your automation
When testing a Google Workspace trigger, you'll have the option of choosing a test record, For example, if you are using the "Google Calendar: When event created" trigger, you'll be able to select an upcoming event or an event that's occurred within the past 3 months to use as a test event.
Once your action is configured and tested, make sure to turn the automation on. In this example, when an event is changed on the calendar selected in the trigger setup, the automation action will run and the corresponding record in Airtable will be updated:
FAQs
Why am I not seeing an option to connect my automation trigger with a shared Drive folder in Google?
Google Workspace automation triggers won't work with files from shared drives. Until this option can be allowed on Google's end, we are unable to support this type of folder. If it's an option to move the file into a personal drive folder, then you should be able to otherwise configure this automation as you intended.
How often does Airtable’s trigger ping Google Workspace?
Airtable relies on Google Drive’s push notification API to notify us when changes are made to the underlying sheet in the user’s Google Drive. Sometimes they push out information within 5 minutes, but other times their push notifications can be delayed for hours. Feel free to review Google's Push Notification documentation more for information.