Authenticate to the Forms API using OAuth 2.0 or API keys via the Zapier App Connector, with the scope forms.readonly to limit access.
Configure the Zapier App Connector to securely store credentials, refresh tokens, and enforce the forms.readonly scope for safe access.
GET /forms/ — List all forms; GET /forms/submissions — Retrieve submissions for forms
Trigger: Retrieve the list of all forms to begin automation.
Actions: Read forms, fetch form definitions, and pull data for downstream apps.
GET /forms/
Key fields: form_id, form_name, form_url
Trigger: New or updated submissions can trigger automations.
Actions: Pull submission data, filter by form_id, export to CRM, spreadsheets, or analytics.
GET /forms/submissions
Fields: submission_id, form_id, submitted_at, answers
Trigger: Access historical submissions for a specific form.
Actions: Retrieve and export submissions for a selected form.
GET /forms/{form_id}/submissions
Fields: form_id, submission_id, answers
Automate data workflows without writing code.
Synchronize form data to CRMs, spreadsheets, analytics, and dashboards in minutes.
Secure authentication with OAuth 2.0 and token rotation keeps data safe.
Overview of the main elements and processes involved when integrating the Forms API with the Zapier App Connector.
A contract that allows applications to talk to the Forms API to access forms and submissions.
An authorization framework that enables secure access to GHL data without sharing passwords.
A specific URL route in the GHL API that performs an action, such as retrieving forms or submissions.
Permissions granted to an app to access GHL data.
Create a Zap that triggers on new submissions and routes data to your CRM.
Schedule periodic pulls of form data to populate dashboards.
Auto-fill PDFs or emails using form data.
Confirm access to forms data and verify permissions.
Define which events should start automations and what data to send.
Activate the workflow and monitor for errors and retries.
The Forms API exposes endpoints such as GET /forms/ to list all forms and GET /forms/submissions to fetch submissions. Use these endpoints within the Zapier App Connector to build automated workflows that channel form data into your CRM, spreadsheet, or analytics tool. To keep data safe, apply the forms.readonly scope by default and request higher permissions only when needed. Second, test each step of your Zap to ensure data maps correctly and handles errors gracefully.
Authentication is required to access the Forms API. You can use OAuth 2.0 or API keys via the Zapier App Connector. Store credentials securely, rotate tokens regularly, and scope access to forms.readonly to minimize risk. If using OAuth, ensure your redirect URI is configured in your GHL developer settings and that permissions align with your workflow.
Yes. You can pull submissions on a schedule by configuring time-based triggers in Zapier that call GET /forms/submissions at defined intervals. This enables batch updates and periodic reporting without manual runs. For real-time needs, you can also trigger on new submissions when supported by your form provider.
Scopes grant specific permissions to access GHL data. For read-only data such as forms and submissions, use forms.readonly. Other scopes may allow write or admin actions; request them only if your workflow requires editing forms or submissions. Always follow the principle of least privilege.
To test a new connection, create a test Zap in Zapier and run a dry run to verify authentication, endpoint responses, and data mappings. Check for correct form lists, sample submissions, and error handling. Review rate limits and retry behavior to ensure stability.
Yes. You can query data for a specific form using the endpoint GET /forms/{form_id}/submissions, which returns submissions tied to that form. Combine this with form metadata from GET /forms/ to build focused automations and detailed reports.
Rate limits are documented in the API reference and may vary by plan. If you reach limits, implement exponential backoff retries and consider batching requests or caching non-critical data. Always monitor API usage within Zapier and your GHL settings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
