Who This Is For / When to Use
Use this guide if you want to:
Trigger workflows from Google Form submissions
Look up Google Forms or responses inside a workflow
Use form answers to drive conditional automation
Eliminate third-party connectors like Zapier for Google Forms
What the Google Forms Integration Does
The Google Forms integration allows Kyrios workflows to read and retrieve data from Google Forms.
It supports:
Polling-based detection of new responses
Searching for forms or responses by name or ID
Conditional branching based on whether data exists
Mapping individual answers into workflow steps
Important Limitation
This is a one-way integration.
Kyrios can read form data but cannot modify forms or submit responses.
Key Features and Benefits
Native Synchronization
No external middleware required
Fewer subscriptions and fewer failure points
Near Real-Time Triggers
New responses are checked approximately every 5 minutes
Uses polling, not instant webhooks
Granular Data Mapping
Access:
Individual question responses
Form name
Submission timestamp
Map values into CRM fields, messages, or logic steps
Advanced Search Actions
Find forms or responses using:
Form ID
Form name
Response ID
Conditional Branching
All “Find” actions include:
Found path
Not Found path
Historical Data Retrieval
Retrieve past responses
Use pagination for large datasets
Step 1: Locate Google Forms in the Workflow Builder
Go to Automations.
Open Workflows.
Open an existing workflow or create a new one.
Click Add Trigger or Add Action.
Use the search bar and select Google Forms.
Step 2: Connect Your Google Account
You must authenticate Google Forms before using any triggers or actions.
Option A: Connect from a Workflow
In Triggers or Actions, select Google Forms.
Click Connect.
Complete Google OAuth authentication.
Option B: Connect from Integrations Settings
Go to Settings.
Open Integrations.
Select Google Forms.
Authenticate your Google account.
Note
The connected Google account must own or have access to the forms you want to use.
Step 3: Available Google Forms Actions
Find Responses (Premium Action)
The Find Responses action retrieves submissions from a specific form.
Required Fields
Form: Select the Google Form
Since: Date/time to start retrieving responses
Limit: Maximum number of responses to return
Optional Field
Next Page Token: Used for pagination when retrieving large datasets
Behavior
Includes two paths:
Responses Found
Responses Not Found
Find Form by ID
Searches for a specific form using its unique Google Form ID.
Use Case
Validate that a form exists before proceeding
Prevent workflow errors
Paths
Form Found
Form Not Found
Find Forms by Name
Searches for Google Forms by name.
Use Case
Useful when Form IDs are not known
Can return multiple matches
Find Response by ID
Retrieves a specific form submission using a response ID.
Use Case
Reprocessing or enriching an existing contact
Using dynamic IDs from previous steps or webhooks
Step 4: Testing the Action
Configure the Google Forms action.
Click Test Action.
Review returned sample data.
Confirm values are available for mapping.
Step 5: Map Response Data into the Workflow
Once data is retrieved, you can:
Update contact fields
Send emails or SMS
Create conditional If/Else branches
Route logic based on specific answers
Response values appear as custom values in subsequent workflow steps.
Step 6: Save, Publish, and Monitor
Click Save on each action.
Save the workflow.
Toggle from Draft to Publish.
Important:
Workflows do not run while in Draft.
Authentication must remain active to maintain polling.
Pro Tips
Polling Awareness
Google Forms triggers run on a ~5-minute polling cycle.
Expect a short delay between submission and workflow execution.
Dynamic ID Usage
Use custom values from earlier steps when configuring:
Find Response by ID
Find Form by ID
Single Trigger Rule
Each form response triggers a workflow only once.
To reprocess data, use a separate workflow with a Find action.
Common Issues and Fixes
Workflow Not Triggering
Confirm the workflow is Published
Ensure Google authentication is still active
Allow up to 5 minutes for polling
Form or Response Not Found
Verify the correct Form ID or name
Use the Not Found branch to handle errors safely
Missing Response Data
Test the action to confirm sample data exists
Ensure the form has at least one submission
FAQ
How quickly does the workflow start after a form submission?
Kyrios checks for new responses approximately every 5 minutes. There may be a short delay between submission and workflow execution.
Can Kyrios send data back to Google Forms?
No. This integration is read-only. Kyrios can retrieve form data but cannot update or submit forms.
What happens if a Form ID cannot be found?
The workflow follows the Not Found branch. You can use this path to send an internal alert or stop the workflow safely.
Can I trigger actions based on specific answers?
Yes. Use an If/Else step after retrieving responses to evaluate answers (for example, only follow up if a priority field equals “Urgent”).
Can I connect multiple Google accounts?
You can connect one Google account per integration. If your forms are owned by multiple accounts, share them with the connected account to manage everything from one workflow.