Learn how to connect Google Forms, use the New or Updated Response trigger, retrieve forms and response data with workflow actions, test the integration, and correctly create a contact when a Google Forms response does not match an existing CRM record.

A Google Forms response does not automatically create a CRM contact. If your workflow needs a contact record, use Find Contact to look for an existing match. On the Contact Not Found branch, add and configure a separate Create Contact action before continuing with contact-based follow-up.

Google Forms in Workflows connects a Google account with the automation builder so activity from a Google Form can start a workflow or provide data to later workflow steps. Triggers monitor form-response activity, while Google Forms actions retrieve form or response information during an automation.

This makes Google Forms useful for lead intake, onboarding, surveys, feedback, event registrations, internal requests, and other processes where submitted information needs to drive automated follow-up.

Google Forms can be used as both a workflow trigger source and a data-retrieval step inside an automation.

Using Google Forms directly in workflows reduces manual handling after a response is received and gives submitted information a clear path into CRM, communication, and internal processes.

• Automated Follow-Up: Start a workflow when a new or updated Google Forms response is detected.
• Faster Lead Handling: Search for an existing contact and create one when the workflow is intentionally configured to do so.
• Flexible Data Retrieval: Find forms or response data during later workflow steps.
• Better Internal Coordination: Use submitted information in tasks, notifications, pipeline processes, and other connected workflow actions.
• Personalized Automation: Pass relevant response data into later workflow steps for more tailored follow-up.

Connecting the correct Google account before building the workflow ensures the automation can access the intended forms and response data. The connected Google account must have access to the forms you plan to use.

1. Open the appropriate sub-account.
2. Go to Settings → Integrations.
3. Stay on the All Integrations tab.
4. Find Google Forms.
5. Click Connect.
6. Sign in with the Google account that can access the required forms.
7. Review and approve the requested permissions.
8. Confirm the integration displays as connected before building the workflow.

The Google Forms trigger determines when form activity should begin a workflow. Understanding the polling behavior is important because a submission or update may not enter the workflow immediately.

New or Updated Response

New or Updated Response starts the workflow when a new Google Forms response is detected or when an existing response is updated.

Google Forms actions retrieve forms or response information after a workflow has already started. Returned values can then support later workflow logic, contact management, email, tasks, notes, opportunity actions, or other configured steps.

A complete setup includes the Google Forms connection, the correct workflow trigger or action, and a realistic test submission. Testing before publishing helps confirm that the expected form is accessible and the response data is available to later steps.

Step 1: Open the Workflow Builder

1. Go to Automation → Workflows.
2. Create a new workflow or open an existing workflow.

Search for Google Forms when adding the applicable trigger or action.

Step 2: Add the Google Forms Trigger

1. Select Add Trigger.
2. Search for Google Forms.
3. Choose New or Updated Response.
4. Select the Google Form you want to monitor.
5. Save the trigger settings.

Choose the connected Google Forms event and configure the form used by the workflow.

Step 3: Add Google Forms Actions When Needed

1. Click the + icon at the point where the workflow should retrieve Google Forms data.
2. Search for Google Forms.
3. Choose the appropriate action, such as Find Responses, Find Forms By Name, Find Response by ID, or Find Form By ID.
4. Configure the required form or response values.
5. Save the action and use its returned data in later workflow steps as needed.

Configure the Google Forms action with the form or response information required by the workflow.

Step 4: Test and Publish the Workflow

1. Save the workflow configuration.
2. Publish the workflow.
3. Submit a real test response to the selected Google Form or update an existing response.
4. Allow approximately 5 minutes for polling to detect the activity.
5. Review the workflow execution and confirm the response data reaches the intended downstream actions.

Google Forms can act as the starting point for workflows that need to identify a contact, notify a team, update a pipeline, or launch additional processing. The examples below demonstrate how Google Forms data can be combined with other workflow actions.

Use Case: Webinar Interest Form Automation

A webinar-interest Google Form can start a workflow that checks whether the respondent already exists as a contact, creates the contact when necessary, and then sends the appropriate confirmation.

1. Trigger — New or Updated Response: Select the webinar Google Form.
2. Find Contact: If the form collects an email address, map that response into the Find Contact action.
3. Contact Found: Continue the existing-contact path, such as sending the webinar confirmation or updating the contact.
4. Contact Not Found: Add a separate Create Contact action, map the name, email, phone, and other required values from the Google Forms response, then continue to the confirmation step.

Key distinction: Find Contact only searches for a matching CRM record. It does not create one when no match is found. The Create Contact action must be intentionally added to the Contact Not Found branch.

Use separate Contact Found and Contact Not Found paths so a new CRM record is created only when the workflow is configured to do so.

Use Case: Google Form Submission → Slack Notification

A new or updated form response can notify an internal Slack channel after the Google Forms trigger detects the response. This is useful when sales, support, or operations teams need visibility into new submissions.

1. Use New or Updated Response as the Google Forms trigger.
2. Add the appropriate Slack notification action.
3. Map useful response values such as name, email, phone, company, or submitted answers into the Slack message.
4. Publish and test the workflow with a real Google Form submission.

Use Case: Marketing Inquiry → Research → Task → Pipeline → Email

A connected Google Form can serve as the intake point for a more advanced workflow that enriches a prospect, creates internal work, updates an opportunity, checks for a contact, and sends personalized follow-up.

1. Trigger: A new or updated Google Forms response is detected.
2. Research: Pass relevant submitted information into a connected research or AI action when applicable.
3. Internal Task: Create an internal task containing the prospect and response details.
4. Pipeline: Create or update the appropriate opportunity.
5. Contact Handling: Use Find Contact first. If no contact is found, use Create Contact before running contact-dependent communication actions.

If a form or response is not appearing, first confirm that Settings → Integrations → Google Forms shows the correct Google account as connected and that the account has access to the intended form.

If a new submission does not start the workflow immediately, allow time for the approximately 5-minute polling interval and confirm the workflow is published. Test with a real new submission or an update to an existing response.

If the workflow reaches Find Contact but no CRM record is created, inspect the Contact Not Found branch. A Create Contact action must be present and its required fields must be mapped from the available Google Forms response data.

If the workflow still does not behave as expected, review the workflow execution history for the trigger and action inputs/outputs, confirm the connected account permissions, and provide the workflow name, affected form, test submission time, and execution details to your administrator or support team.