Access to the Forms API requires a secure credential (API key or OAuth token) scoped to forms.readonly. Keep credentials private, rotate regularly, and store them in your Zapier connection fields.
Zapier handles credential storage and prompts you to authorize the Forms API connection when you create or edit the app connection. Use the recommended permission scope and test in a sandbox first.
– GET /forms/ — Retrieve a list of forms. – GET /forms/submissions — Retrieve submissions for forms. Note: Only these endpoints are required for the flows highlighted on this page; other endpoints exist in the reference documentation.
Trigger: New form submission (GET /forms/submissions).
Actions: Retrieve the latest submissions, map fields like form_id, submission_id, form_title, and submitted_at, and push to your destination (CRM, spreadsheet, or analytics tool).
Method paths: GET /forms/ and GET /forms/submissions to drive the workflow.
Key fields: form_id, submission_id, form_title, submitted_at, respondent_email (where available).
Trigger: Scheduled pull (daily or hourly) via Zapier scheduler.
Actions: Retrieve submissions with GET /forms/submissions, format into a report, and deliver to apps like Google Sheets, BI tools, or a data warehouse.
Method path: GET /forms/submissions (with date filters as needed).
Key fields: submission_id, form_id, submitted_at, respondent_email, status.
Trigger: Hourly data pull for analytics.
Actions: Compile counts per form, total submissions, average response time, and push to your dashboard or reporting tool.
Method paths: GET /forms/ and GET /forms/submissions, with filters for date range and form_id.
Key fields: form_id, forms_count, submissions_count, average_response_time, last_submission_at.
Automate data routing without writing code.
Reduce manual entry and errors by syncing form data to your tools automatically.
Scale integrations across teams with a few clicks and standard templates.
Understand the data elements and the flow: authentication, endpoints, triggers, actions, and field mappings that move data from Forms API to your apps.
A URL path exposed by the service to perform a specific action, such as GET /forms/.
The process of verifying identity and granting access to the API.
An event that starts a workflow or data pull.
A callback URL that receives real-time data updates.
Trigger notifications when a new form submission arrives, then post details to Slack, Teams, or email.
Aggregate daily form activity and send a summarized report to a channel or dashboard.
Push new submissions into your CRM as contacts or activities to keep records up to date.
Enter your API credentials and authorize access to Forms API within your Zapier connection.
Choose GET /forms/ and GET /forms/submissions, then map fields to your destination.
Run tests with sample data to verify mappings before going live.
Authentication for the Forms API typically uses an API key or OAuth token scoped to forms.readonly. When you create or edit the connection in Zapier, select the Forms API and enter your credentials to establish access. Ensure credentials are stored securely and never shared publicly. For production, rotate credentials regularly and use least-privilege access. If tokens expire, follow the provider’s refresh flow and update the connection in Zapier accordingly.
GET /forms/ returns the list of forms and their IDs, titles, and metadata. This endpoint is useful to populate dropdowns and map fields in your workflows. GET /forms/submissions returns submissions for a given form. You can filter by date or form_id as needed; refer to the API reference for supported query parameters and rate limits.
Yes. Use Zapier triggers to start workflows when events occur (for example, a new submission). Use actions to push data into your destination apps. No coding is required to set up typical flows. You can also use webhooks for real-time delivery if your use case requires instant updates.
No heavy coding is required; the Zapier UI guides you through connecting the Forms API, selecting endpoints, and mapping fields. Templates and presets cover common use cases.
Test the integration in Zapier using sample payloads and your connected accounts. Validate mappings, authentication, and error handling by running different scenarios (new submissions, missing fields, date filters). Once tests pass, enable the workflow in production.
The Forms API returns fields such as submission_id, form_id, form_title, submitted_at, and respondent data when available. The answers array contains individual form responses; field names depend on your form configuration.
API endpoint documentation is available in the developer portal for Forms API, including endpoint details, authentication, and example payloads. This reference explains parameters, rate limits, and best practices.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
