Test the CRM connector with two contacts before AI can write

An AI agent can now build a CRM connector in less than a minute. Speed is not the part that deserves your attention. Before the agent can write to your customer database, the team needs proof that it finds the right person, updates the intended fields, and does not turn a new contact into a duplicate.

On August 11, Intercom released a template connecting Fin for Sales to Marketo. Intercom's current HubSpot guide uses the same structure. The AI reads the CRM schema, suggests mappings, and builds two separate connectors: one that reads contact data and one that writes qualified contacts back.

Source: Intercom: Integrate Fin for Sales with Marketo within minutes.

What Fin for Sales does with HubSpot and Marketo

A data connector is the part of an AI workflow that retrieves or sends structured information to another system. Fin uses the read connector at the start of a sales conversation to find existing customer context. The write connector runs only when the conversation reaches a chosen outcome, such as qualification for sales.

HubSpot connects through OAuth. Fin also inspects custom HubSpot properties, runs a test search, and suggests mappings between CRM fields and Intercom attributes. Fields with no match can receive a new hs_ prefix. HubSpot sync is an upsert: it updates the contact with the same email address or creates a contact if none exists.

Marketo requires a REST endpoint, identity URL, client ID, and client secret from an API service. The connector is limited to a selected person partition. The read connector matters even more here because it finds the person's Marketo ID. Without it, a write operation may have to match on email alone and can fail when several people share an address.

Sources: Intercom's HubSpot connector guide. Intercom's Marketo connector guide.

Test the CRM connector with two contacts

Use one existing internal test contact and one approved internal address that may become a new test record. Label both clearly in the CRM. If you have a sandbox or test partition, use it. The aim is to verify both update and creation without involving real inbound leads.

1. Decide what the agent may read and write

List the fields required for qualification. Name, email, company, source, and a clear qualification outcome are often enough for the first test. Remove fields the agent does not need.

For HubSpot, an authorized administrator should review the OAuth access. For Marketo, use a scoped API service and keep the client secret in the integration's secret manager, not in a chat or shared document.

2. Build the read connector first

Ask Fin to generate the contact-enrichment connector. Review every proposed mapping before saving it. Pay close attention to custom CRM fields, required fields, and the unique identifier used for matching.

Run the existing test contact through a sales conversation. A passing test retrieves the correct company and contact details without changing the record.

3. Allow CRM updates only after a clear outcome

Build the write connector and attach it to one specific sales outcome, not to every closed conversation. Define which information Fin must collect before the connector can run.

Run the same existing test contact again. The CRM should still contain exactly one contact. Only approved fields may change, and previous values outside the mapping should remain intact.

4. Try one controlled creation

Run the approved internal address that is not yet in the CRM. Confirm that the agent creates exactly one record in the intended partition or workspace, with the right source label and qualification outcome.

Search by both email and CRM ID. If you find two records, disable the write connector and fix the matching rule before another run.

5. Read the execution trail

Intercom shows connector events in the conversation. Confirm that the read connector ran at the start, the write connector ran only after the chosen outcome, and both steps succeeded. Record the test date, contact ID, mapping version, and reviewer in your operations log.

Source: Intercom: Fin for Sales integrations and data-connector verification.

Approve the connector only when the whole chain holds

The connector is ready for a bounded pilot when it:

• finds the correct existing contact before qualification;
• updates one record without creating a duplicate;
• creates a new record with the intended fields and source label;
• writes only after the selected sales outcome;
• leaves a readable execution trail for success and failure.

Fin for Sales is available on Intercom's latest pricing plans and, after a free trial, is billed per successful outcome. Check plan access and usage limits before starting the pilot.

Source: Intercom: Fin for Sales explained.

Once this test passes, the same two-contact check can become a reusable acceptance test for other AI connectors. It also fits the work Hammer Automation handles through Tool Forge: define access, mappings, stop rules, and run logs before an agent touches live customer workflows.