Forms API Integration: Real-Time Form Submissions, Normalized Responses, and Downstream Workflows

February 9, 2026

Forms are where intent enters your system.

Job applications, contact requests, surveys, registrations, feedback, internal questionnaires — forms are the primary way people volunteer structured data. But once responses start flowing, most teams hit the same problems: inconsistent schemas, delayed access to submissions, brittle exports, and unclear ownership of identity.

Forms API integration exists to solve this. In this guide, we'll explain what a Forms API actually does, which objects matter in practice, how submission lifecycles work, how updates are delivered, and how Unified's Forms API fits alongside CRM, Marketing, Enrichment, ATS, and HR within the broader platform.

Introduction to Forms API Integrations

Form builders such as Typeform, Google Forms, and Tally are used to collect structured data across many workflows:

• Lead capture and contact requests
• Surveys and research
• Job applications
• Event registrations
• Internal questionnaires and approvals

Each platform exposes its own API, schema, and authentication model. Products that need to support multiple form tools often encounter:

• Inconsistent question and answer formats
• Provider-specific submission models
• Uneven support for real-time delivery
• Fragile exports and manual workflows

A Forms API provides a normalized ingestion layer that allows applications to read forms and submissions consistently across platforms — without building and maintaining separate integrations.

What Is a Forms API?

A Forms API allows applications to programmatically access form definitions and completed submissions from form platforms.

In practice, this includes:

• Listing available forms and their fields
• Retrieving completed submissions
• Reading typed answers in a consistent schema
• Ingesting responses into downstream systems

Forms APIs are event ingestion APIs. They are not systems of record and they do not execute workflows themselves. Their role is to expose structured input data reliably and in real time.

Forms API vs CRM, Marketing, Enrichment, ATS, and HR

Unified treats Forms as one category within a broader system, with clear boundaries.

• Forms APIs ingest raw submissions and answers.
• CRM APIs manage contacts, companies, deals, and pipelines.
• Marketing APIs manage lists, subscribers, campaigns, and engagement.
• Enrichment APIs append firmographic or demographic attributes.
• ATS APIs manage candidates, jobs, and applications.
• HR APIs manage employees and organizational data.

Forms do not own identity. They collect inputs. Any relationship between a form response and a CRM contact, marketing subscriber, candidate, or employee must be established explicitly by the application.

Real-Time vs Batch Form Data

Live Access to Source Platforms

Unified's Forms API routes every request directly to the connected form platform. There is no cached replica or background synchronization layer. Reads reflect the current state of the source system, subject to provider rate limits and availability.

Update Delivery: Webhooks and Polling

Form platforms vary in how they deliver updates:

• Some providers support native submission webhooks
• Others rely on polling
• Form metadata changes rarely emit events

Unified supports both native webhooks (when available) and virtual webhooks (generated by polling). When neither is available, applications must poll submission endpoints using timestamp filters.

Core Forms Data Models (and How They Behave)

Unified normalizes Forms data within the Forms category, exposing two objects: Form and Submission. Provider capabilities vary and should be handled defensively.

Forms

Forms represent the template and structure of a survey or questionnaire.

• Include identifiers, names, descriptions, and configuration flags
• Contain an array of fields describing each question
• Include metadata such as published URLs and response counts
• Expose created_at and updated_at timestamps

Although Unified's API surface includes create and update endpoints for forms, Google Forms, Typeform, and Tally are read-only in practice. Their integration capability pages show no writable fields. Forms can typically be deactivated via is_active, but deletion is not supported.

Submissions

Submissions represent completed responses.

• Include identifiers, timestamps, and a form_id
• May include respondent metadata such as email or name (provider-dependent)
• Contain an array of typed answers
• Are immutable once created

There are no endpoints to create, update, or delete submissions through Unified. Creation happens in the underlying form platform. Unified exposes submissions for retrieval only.

Submission Lifecycle and Answer Semantics

Creation

A submission is created when a respondent completes a form in the source platform. Unified does not create submissions.

Immutability

Submissions cannot be modified after creation. The updated_at timestamp typically matches created_at, reflecting the immutable nature of responses.

Typed Answers

Answers are returned as structured JSON:

• Strings, numbers, booleans
• Arrays or objects for multi-select or matrix questions
• Optional file identifiers for uploads

This preserves semantic meaning and avoids forcing all responses into string values.

Identity and Ownership in Forms

Forms intentionally avoid identity coupling.

• Forms do not reference contacts, users, or employees.
• Submissions may include respondent_email or respondent_name, but no cross-category IDs.
• There is no contact_id, member_id, candidate_id, or employee_id.

Identity resolution happens outside the Forms API. Applications typically match respondents to CRM contacts, marketing subscribers, candidates, or employees using shared attributes such as email.

Update Delivery and Polling Strategies

Submission Updates

• Typeform supports native submission webhooks.
• Google Forms and Tally use virtual webhooks (polling behind the scenes).
• When webhooks are unavailable, applications must poll using updated_gte.

Recommended Polling Pattern

1. Store the most recent updated_at timestamp.
2. Call the submissions list endpoint with updated_gte.
3. Process returned submissions.
4. Update the stored timestamp.
5. Apply exponential backoff on rate-limit responses.

Polling frequency should reflect urgency. Near-real-time workflows may poll every minute; analytics ingestion may poll hourly or daily.

Security, Privacy, and Data Handling

Form submissions often contain sensitive data. Unified's architecture minimizes exposure.

Zero-Storage Design

• Form data is routed directly to source platforms.
• No submission payloads are stored at rest.
• No customer data is written to logs.
• Requests are stateless and region-aware (US, EU, AU).

If long-term storage is required, applications must persist data themselves.

PII Handling and Compliance

Submissions may include:

• Email addresses
• Names
• Free-text responses containing arbitrary personal data

Unified passes data through exactly as provided by the source platform. Developers are responsible for:

• Secure storage
• Access controls
• Consent management
• Compliance with GDPR, CAN-SPAM, CASL, and similar regulations

For AI-driven workflows, MCP-based integrations can remove sensitive fields before downstream processing.

Common Forms API Integration Use Cases

Lead Capture

Ingest contact requests or sign-ups and create CRM contacts or marketing subscribers explicitly.

Survey and Feedback Analytics

Aggregate responses across multiple platforms into a unified dataset for analysis.

Workflow Triggers

Trigger downstream logic — notifications, tasks, or approvals — when new submissions arrive.

ATS and HR Intake

Use forms for applications or internal surveys, then create candidates or employee records via the appropriate APIs.

AI-Powered Analysis

Analyze structured responses using embeddings or classification without storing raw form data in Unified.

Challenges and Constraints to Plan For

Unified is explicit about Forms limitations:

• Submissions are immutable
• Identity resolution is external
• Write support for forms varies by provider
• Form deletion is not supported
• Webhook support is uneven
• PII handling is the application's responsibility

These constraints reflect real provider behavior and should be incorporated into system design.

Build vs Buy Forms Integrations

Building In-House

• Multiple provider schemas
• Inconsistent answer formats
• Custom polling and retry logic
• Ongoing maintenance as platforms evolve

Using a Unified Forms API

• One ingestion surface
• Normalized forms and submissions
• Typed answers
• Live access to source platforms
• Centralized authentication and maintenance
• Usage-based pricing aligned with API volume

Best Practices for Implementing Forms APIs

• Treat forms as event sources, not records
• Persist submissions in your own system
• Design for immutable responses
• Match identities explicitly using email or answer data
• Poll incrementally using timestamps
• Secure free-text responses carefully
• Keep Forms, CRM, and Marketing responsibilities separate

Ingest form data with clear boundaries

If your product relies on ingesting structured input from multiple form platforms, building and maintaining those integrations independently quickly becomes complex.

Unified's Forms API provides a normalized, real-time ingestion layer for forms and submissions across supported platforms — without storing form data or collapsing category boundaries.

→ Start your 30-day free trial

Test form ingestion with live submissions and normalized schemas.

→ Book a demo

Discuss form ingestion, downstream workflows, or cross-category integrations with the team that built the platform.

FAQ

What is a Forms API?

An API that allows applications to read form templates and submissions programmatically.

Which platforms are supported?

Unified supports platforms including Typeform, Google Forms, and Tally, with additional providers available.

Are form submissions real time?

Yes. Submissions are available as soon as the source platform records them, subject to provider webhook or polling behavior.

Can I create or edit submissions via the API?

No. Submissions are immutable and read-only.

Does the Forms API store response data?

No. Form data is never stored at rest.

How does Forms differ from Marketing or CRM APIs?

Forms collect input. Marketing executes campaigns. CRM manages relationships. Each category has a distinct role.