CRM Integrations

Connect the handoff.Keep ownership clear.

Customer relationship management (CRM) systems hold commercial records and relationships. Connect them around a business handoff: what should arrive, who owns it and what happens next. Start with that agreement, not an everything-everywhere mirror.

For B2B teams whose demand generation depends on reliable movement between intake, marketing operations and sales.

Discuss your systems handoff Explore the work

Led by Travis Bjorklund. Explore the scope, then choose a conversation or a written brief.

A business handoff, made explicit

One handoff. Two systems.
No mystery in between.

CRM integration connects records and relationships so the next person has usable context. We start with the handoff your business needs, then choose the simplest supported way to deliver and verify it.

Source

Website inquiry

Identity, stated need and permission context

Agreement

Validate & match

Authority, stable identity and exception rules

Destination

CRM + owner

Correct record, company relationship and next action

Illustrative field agreement Not a client record or measured result

What moves from an inquiry into a commercial record
Information	Authority	Before we call it complete
Stable inquiry ID	The originating submission	Repeated delivery refers to the same inquiry, not another new lead.
Contact identity	Agreed identity rules	A verified match or an explicitly new record; ambiguity goes to review.
Company association	Verified account relationship	The contact is associated with the intended company.
Stated need	The buyer's original request	Context survives the transfer without a guessed qualification.
Sales owner	Approved assignment rules	A valid owner or an accountable exception queue.
Marketing permission	The permission record and policy	No opt-out is overwritten by a new inquiry.

Business labels, not a universal API schema. Actual fields, object relationships and permissions are checked in your accounts before implementation.

A connector or a custom build?

Prefer the simpler connection

Native, when it fits

Use the supported connector when its record types, direction, matching rules and error visibility meet the handoff. Existing subscriptions may already provide what you need.

Check what happens on updates and partial failures, not just whether the first record arrives.

Build only the missing responsibility

Custom, for a specific gap

A custom path may be justified by field-level authority, unusual relationships, verification or recovery requirements that the connector cannot support.

That decision includes maintenance and operating ownership, not only the initial build.

What the business should be able to read

A delivery receipt.
Not a green webhook.

Attempted: The request was sent. That alone proves neither acceptance nor the intended result.
Accepted: The destination acknowledged the operation. Required fields and relationships still need checking.
Verified: A readback confirms the agreed result.
Unknown: The response was lost. Reconcile the stable identity before retrying.

These are illustrative states, not a live test. The delivery brief, mapping, test evidence and recovery runbook become the handover for the agreed integration.

Explore furtherRehearse delivery, exceptions and recovery

Explore a real decision

Rehearse a record delivery

Choose a delivery situation and trace a synthetic record through validation, matching, delivery and verification. Each click reveals the next check. When the handoff stops, inspect the recovery plan without triggering a retry.

Illustrative local rehearsal. No real records, account connections or system changes. A completed trace is not a test of your integration.

IntakeIllustrative record handoffCRM

ValidateNot started
MatchNot started
DeliverNot started
VerifyNot started

Example evidence / ready

A qualified record is ready to inspect

Synthetic intake record, not yet validated. The required identity, owner, mapped fields and company association still need to be checked. No real system is connected.

Owner: Integration owner

Ready to trace - nothing attempted

One click, one check

No system is connected. Inspecting recovery explains the work; it never performs a retry or changes the result.

.cs-model .cs-interactive { display: none !important; }

Record-delivery reference

Validate required data, match identity and field ownership, deliver the intended update, then verify destination fields and relationships. An acceptance response is not verification.

Normal delivery / Verify

Readback matches the intended handoff

The synthetic destination record has the expected identity, mapped fields and associations. Only now is the illustrative handoff complete.

Owner: Integration owner

Recovery or follow-up: Keep the stable destination ID and verification receipt. Continue monitoring; a successful example is not a guarantee of uninterrupted future delivery.

Required field missing / Validate

Stop before a destination write

The required account owner is absent. Validation blocks the handoff; nothing is sent to the destination in this example.

Owner: Source data owner

Recovery or follow-up: Correct the missing field in its authoritative system, then revalidate the whole current record. Do not bypass destination requirements or invent an owner.

Identity is ambiguous / Match

Multiple plausible records need review

Matching finds more than one candidate and no confirmed stable destination ID. Do not pick the first result, merge automatically or create another duplicate.

Owner: CRM data steward

Recovery or follow-up: Review identity and confirm the intended destination. Record the stable ID and matching rationale before any resumed handoff; a shared email or similar name alone is not sufficient.

Destination unavailable / Deliver

No connection; retry remains pending

This example fails before a connection to the destination is established. No delivery is confirmed, and the source remains pending.

Owner: Integration operations owner

Recovery or follow-up: Restore connectivity and apply the agreed bounded retry policy. Recheck current source state and stable identity before replay. If the write outcome is uncertain instead, reconcile it before any retry.

Write response was lost / Verify

The write may have succeeded

A write was attempted, but the response and destination readback are unavailable. Outcome unknown is neither failure nor confirmed success.

Owner: Integration operations owner

Recovery or follow-up: Reconcile the destination by stable identifier and available receipts before attempting another write. If reconciliation is inconclusive, retain an exception for review rather than creating a second record.

Newer destination change / Match

Protect the authoritative newer value

The source payload disagrees with a newer field value owned by the destination. This mapping cannot safely overwrite it.

Owner: Named field owner

Recovery or follow-up: Apply the agreed field-level ownership and conflict rule. Review current source and destination revisions, record the decision and rebuild the handoff; never silently choose whichever event arrived last.

A connection is a narrower job than a CRM rebuild

We can connect an agreed handoff without assuming a database migration, historical cleanup or new sales process. Those dependencies are identified separately. Marketing operations addresses the wider operating design.

Subscriptions, access, provider limits and the number of exception paths shape feasibility and fees. No real-time, zero-loss or autonomous-recovery promise is made.

A few useful answers

Before systems are connected

Browse the decision library ↗

When is a native connector enough?

A native connector is often the right starting point when its supported records, direction and update rules fit the handoff. We examine those limits before proposing custom work. Custom delivery becomes relevant when a necessary business rule, ownership boundary or verification requirement cannot be met reliably.

Which platforms can you connect?

Feasibility depends on your subscriptions, permissions and application programming interface (API), the supported way software exchanges information. We check actual access rather than assume every account exposes the same capabilities. HubSpot’s CRM documentation illustrates why supported record types, properties and associations must be confirmed during discovery.

HubSpot: Understanding the CRM APIs ↗

What happens when systems disagree?

We agree authority field by field, not declare one application right about everything. A newer conflicting value triggers review rather than an automatic overwrite. Salesforce conversion behavior and organization-specific rules need explicit consideration where relevant. The approved mapping reflects your operating model, with named owners for exceptions and protected fields.

How do you handle failed writes and duplicates?

First establish what happened. A lost response may follow a successful write, so check a stable identifier or receipt before retrying. Verification checks intended fields and associations. Retry rules remain bounded and provider-specific. HubSpot’s legacy public-app webhook guide illustrates why repeated notifications require duplicate protection, not a universal retry policy.

HubSpot: Webhooks API guide ↗

Does this include a CRM migration?

Not by default. Connecting an agreed handoff differs from moving an entire database, rebuilding a schema or repairing historical records. Discovery can identify those dependencies and distinguish essential preparation from a separate migration. Data cleanup, deduplication and historical backfills need their own scope, acceptance criteria and accountable owner.

What determines scope, fees and handover?

Scope follows the handoff, systems involved, available access, exceptions and evidence needed for acceptance. Fees are agreed against that work; subscriptions, custom data repair and ongoing maintenance are identified separately. Handover includes operating documentation, recovery ownership and monitoring responsibilities so the connection does not depend on undocumented knowledge.

Directly with Travis

Connect the next commercial decision

Bring the handoff that is slowing demand generation down. Work directly with Travis to define ownership, test the connection and leave an operating agreement your team can use. The goal is connected commercial work, not more software.

Discuss your systems handoff Talk with Travis