To use the Workflows API with Zapier App Connector authenticate via your API key and the surveys.readonly scope defined for this integration
Connect your Zapier App Connector account securely to authorize requests to the Workflows API
GET /surveys/ — list all surveys; GET /surveys/submissions — list submissions for surveys; more endpoints are listed in the full guide as needed
Trigger when a new survey is created in Workflows API
Actions: fetch surveys map fields to your app and start analytics
Method GET Path /surveys/
Key fields id, title, created_at
Trigger on new submissions added to a survey
Actions: pull submission data update CRM records notify teams
GET /surveys/submissions
submission_id, survey_id, responder_email, submitted_at
On demand sync of survey data to keep systems aligned
Actions: POST or PATCH responses push updates to related records
Example path POST /surveys/{survey_id}/submissions
id, status, updated_at
No code automation of survey data flows between systems
Faster access to survey insights through live syncing
Scalable integrations that grow with your survey program
Glossary of core terms used in this guide to help you navigate API connections
Application Programming Interface that allows apps to talk to each other
A specific URL in an API that performs a function
A callback URL that notifies your system when an event occurs
Permission to access resources using tokens or keys
Automatically generate a new survey in Workflows API when a trigger fires in Zapier
Push each survey response into a contact’s timeline in your CRM
Aggregate survey data and send reports on a schedule
Get your API key and set proper scopes in Workflows API and in Zapier App Connector
Enter the endpoint paths and param mappings in the Zapier app settings
Create zaps that map fields and trigger actions across apps
No coding is required for basic setup. Use the Zapier App Connector to map fields and trigger actions using the Workflows API endpoints. If you need more customization you can add filters and multi step zaps to handle complex flows.
The example endpoints in this page cover surveys GET /surveys and GET /surveys/submissions. Other endpoints may be available in the Workflows API depending on your plan. Refer to the API docs for full endpoint lists and pagination details.
To test the connection run a test in Zapier and verify the response from GET /surveys. If authentication fails check tokens scopes and base URL. Use test data and inspect error codes to troubleshoot.
The required scope for this integration is surveys.readonly. Ensure your OAuth token includes this scope. If you need write access request elevated scopes from your GHL admin and update the Zapier app settings.
Yes you can customize which fields are sent to your app and CRM. Use field mapping in the Zapier step to select required data. Consider using filters and transformations to normalize data before it lands in downstream systems.
Errors are surfaced as standard HTTP status codes. Common issues include 401 unauthorized 403 forbidden and 429 rate limit. Implement retries with exponential backoff and log error messages for troubleshooting.
API rate limits vary by plan. Check your account dashboard and the API docs for current limits. If you hit limits consider batching requests or spacing polls to reduce load.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
