Learn how to obtain an API key, set the scope (forms.readonly), and securely connect to the Forms API.
Authorize the Zapier app, grant necessary permissions, and verify the connection to ensure data can flow.
GET /forms/ — Retrieve all forms; GET /forms/submissions — Retrieve submissions for forms
Trigger: when a new form is added or on-demand sync
Actions: fetch forms, map form fields to your app, create/update records
GET /forms/
Key fields: id, title, description, created_at
Trigger: on new submission or on a schedule
Actions: fetch submissions, map to records, attach to contact/company
GET /forms/submissions
Key fields: submission_id, form_id, submitted_at, data
Actions: combine forms and submissions data, export as a dataset
GET /forms/ and GET /forms/submissions
Key fields: forms.id, submissions.submission_id, submissions.form_id
Build automations without writing code
Enable real-time or scheduled data sync between Forms API and your apps
Leverage a visual workflow builder to map data quickly
A quick glossary of terms and processes used when connecting GHL Forms API with the Zapier App Connector
Application Programming Interface: a set of rules that lets software interact with each other.
A specific URL on an API that performs a function.
The process of proving identity to access API resources securely.
A method for servers to send real-time data to clients as events occur.
Map form responses to contact fields to auto-create or update CRM records.
Use responses to drive lead scoring and routing logic in your CRM.
Notify teammates automatically when new submissions arrive.
Obtain an API key, set scope to forms.readonly, and authorize the Zapier app.
Add GET /forms/ and GET /forms/submissions to your Zapier workflow steps.
Test mappings, validate data, and deploy to production.
To authenticate, generate an API key from your GHL account and add it to the Zapier connection as a header. Use the forms.readonly scope to limit access to read operations. Store keys securely, rotate regularly, and test the connection with a lightweight Zap to confirm that GET /forms/ returns data.
You typically need read permissions for forms and submissions; ensure the API key or OAuth token has the forms.readonly scope. In Zapier, grant the app access to your account. If you need write access, request higher scopes; for most data retrieval use cases, readonly suffices.
Yes, you can fetch submissions with GET /forms/submissions; you may filter by form_id to target specific forms. Zapier can poll or trigger on new submissions depending on your plan. Pair this with GET /forms/ to enrich submission data with form metadata.
The core endpoints are /forms/ and /forms/submissions. Depending on your setup, additional endpoints may exist; this page focuses on the primary read endpoints for forms and submissions. Always consult the API reference for endpoint availability and rate limits.
No coding is required for basic integration. You configure an API connection in Zapier and set up triggers and actions using the Forms API data. If you need custom logic, you can use code steps or webhooks, but it is not necessary for standard retrieval and mapping.
Data can be pulled on a schedule or via triggers, depending on the API and your Zapier setup. The /forms/ endpoint can provide form data in near real-time when polled frequently. Submissions updates depend on how you configure the trigger and the API’s response times.
Map fields by selecting source fields from the form data and assigning them to destination fields in your app. Use Zapier’s data mapping tools to align field names and formats. Test mappings to ensure data types and date formats match your destination system.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
