How to connect a website form to a CRM without losing enquiries

Connecting a form to a CRM should turn every valid request into a record someone can follow. The work includes defining fields, distinguishing contacts from requests, handling interruptions and confirming delivery. This guide helps prepare that connection with the technical team, whether using an existing connector or requiring a bespoke integration.

By Lyntev. Updated on .
About 4 minutes to read.

A request that stays connectedThe same reference follows the request and prevents duplicates.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Define the data contract
  • Test repetition and recovery
  • Estimate time with exceptions included

Draw the complete journey of a request

Choose a form and destination. For example: a quote request, creating or identifying the contact, opening an opportunity and assigning a person responsible. First check whether the CRM already offers a connection covering this journey, necessary fields and an inspectable failure history.

Separate the visitor’s acknowledgement from completion in the CRM. In an integration with later processing, “request received” should appear only after the request is saved in a recoverable way. The team needs to distinguish received, pending, completed and requiring review. An alert email alone does not demonstrate that the CRM received everything.

A journey that allows recovery from interruptions
  1. Receive

    Validate and save the request with an identifier.

  2. Route

    Place pending work in a persistent queue.

  3. Record

    Associate contact, request and person responsible in the CRM.

  4. Confirm

    Save the result and make exceptions visible.

Proposed architecture to adapt to the connector and supplier guarantees.

Define a contract for each field

Write the name, type, required status and destination of fields before connecting applications. A request and a contact are different entities: the same person may send two legitimate requests. The submission identifier follows the request; the CRM identifier follows the contact.

HubSpot’s contacts API documents operations using email or unique properties depending on the operation. Check your supplier’s rule and update policy. Do not merge people merely because they have the same name or replace already confirmed data with empty form fields.

Define a contract for each field
FieldProposed ruleDestination
submission_idUnique per request; preserved on retriesExternal request reference
emailValidated; identity according to the CRMContact
servicoValue from a controlled listOpportunity type
mensagemText with a size limitRequest description
submitted_atDate and time with an explicit time zoneTime of receipt

Validate on the server and limit access

Browser validation helps correct errors during completion. MDN explains why this validation also needs to exist on the server: submissions may arrive by another route. Validate types, allowed fields and sizes; return messages that let people correct the request.

CRM credentials stay on the server with the permissions required for the operation. Define abuse protection and the retention period for diagnostic data. In technical logs, prefer identifiers and states to full copies of personal messages. A quote request should not automatically change marketing preferences either.

Fictitious example of a request contractjson
{
  "version": 1,
  "submission_id": "demo-00042",
  "submitted_at": "2026-11-17T10:15:00Z",
  "contacto": { "nome": "Ana Exemplo", "email": "ana@example.com" },
  "pedido": { "servico": "manutencao", "mensagem": "Fictitious request." }
}

Make a retry produce the same result

An interruption can occur after the CRM saves a record but before confirmation reaches the website. Resending without checking may create a duplicate. Stripe’s webhook documentation describes retries and duplicate events; it is an example of behaviour to check in the contract of the supplier you use.

Request an idempotency mechanism: recognising an operation already applied and returning its existing result. Reserving the identifier should support two simultaneous attempts. If an operation has several stages, save progress and mark completion only after mandatory stages. Where the destination offers no suitable unique key, a way to reconcile uncertain results must be defined.

Decide in advance what happens on failure

Automatic attempts need intervals, a limit and a route to human review. Respect supplier guidance on usage limits. Define who receives the alert, where they consult the request and how they resume processing without re-entering data.

In the pilot, compare valid requests received with those completed, pending and referred for review. Each identifier should have an explainable state. Also run a recovery test: restoring the connection must allow pending requests to complete without creating new ones.

Decide in advance what happens on failure
Test situationExpected behaviour
Invalid requestExplain the field to correct; do not create an incomplete opportunity.
Same request delivered twiceReuse the operation; check it has not duplicated.
CRM unavailableKeep pending; retry in a limited, visible way.
Response lost after savingReconcile by identifier before creating again.
Field removed from CRMSuspend the invalid attempt and notify the person responsible.

Estimate time including exceptions

In this fictitious scenario, 200 tasks per month at 4 minutes represent 13 hours and 20 minutes. If 80% are eligible, there are 160 tasks to review for 0.5 minutes and 40 manual tasks at 4 minutes. Adding one monthly hour of monitoring gives a new total of 5 hours: the potential difference is 8 hours and 20 minutes.

Use the simulator with measurements of your process. The estimate does not automatically include initial configuration, learning or exceptional incidents, nor does it convert time into money. The difference may be negative. Compare the projection with the pilot and adjust the eligible percentage when genuine exceptions emerge.

Deliver a worksheet that allows implementation and verification

Complete this worksheet before implementation. After the pilot, add test results and the person responsible for continuity. A connection is easier to maintain when the team knows the fields, states and recovery procedure.

Worksheet for your project

Form–CRM connection worksheet
Source form and purpose:
CRM, destination object and person responsible:
Required fields and update rules:
Unique identifier for each request:
Rule for finding or creating the contact:
States: received / pending / completed / review
Where a request not yet delivered is saved:
Attempt limit and alert destination:
How to reconcile a lost response:
Technical data retention period:
Tests: valid / repeated / simultaneous / unavailability / recovery
Count of received requests and destination of each:
Measured manual time, exceptions and monitoring:
Person responsible for approval and date:

Estimate working time

Compare current effort with a scenario including human review, tasks that remain manual and oversight. Initial values are a fictional example.

Monthly scenario data

Count occurrences of the same process in a representative month.

Team working time, excluding waiting.

Human work remaining in each automated task.

Remaining tasks retain their current time.

Maintenance and exceptions beyond the review already counted.

Time potentially freed: 8 h 20 min per month.

Current work
13 h 20 minPer month
Work in the scenario
5 hPer month

160 eligible tasks and 40 tasks retained in the current process.

How the calculation works

Eligible tasks = monthly tasks × eligible percentage ÷ 100.

Current work = monthly tasks × current minutes ÷ 60.

Work in the scenario = [(ineligible tasks × current minutes) + (eligible tasks × review minutes)] ÷ 60 + oversight hours.

The difference is current work minus work in the scenario. It may be negative. The calculation allows an average monthly volume, so the eligible quantity may be fractional.

Initial implementation effort is excluded. Time freed does not itself mean money saved: validate time and quality in a pilot.

Calculations run in this browser. Values are neither sent nor saved.

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.