Integrations · Connection before assumption

Connect the tools that matter — with the data flow understood first.

An integration is useful when it removes a real hand-off and has a clear owner. 121 starts with the job, the authoritative system and the failure path before recommending a native connection, connector, API or manual exchange.

Subscribe to 121 CRM Seller, billing and cancellationSee workflow automation

Customer Thread

One connection, four questions

Illustrative example

Need
Name the hand-off
Route
Choose connection type
Data
Define direction and owner
Test
Exercise success and failure
Approve
Accept limits and cost
Human decision

Illustrative assessment. Connections, access and costs depend on the chosen setup.

Connection register

Show the route, owner and evidence for every connection.

A useful integration directory distinguishes a direct connection, connector or API, manual exchange and a capability that has not yet been verified.

121

Northstar Joinery

Fictional

Understand what connects and who owns it

OverviewConnectionsData flowChecksChange log

See how each connection would work

Review the proposed connection, owner and checks

Examples only · not enabled

Direct connection

Test in account

Connector or API

Scope limits

Manual exchange

Control transfer

Needs checking

No promise

Illustrative CRM interfaceAll people, organisations, dates and activity are fictional. Availability depends on verified configuration and scope.

Inside the working system

See what each part contributes.

The CRM is easier to plan when contacts, conversations, work, access and automation are treated as separate capabilities with clear responsibilities.

Capability 01

Native integrations

Connects supported external providers through dedicated HighLevel settings and authorisation flows.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Provides a maintained connection path for common services without a bespoke integration.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Capability 02

App Marketplace

Lets authorised users discover and install eligible third-party applications at the appropriate account scope.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Extends the platform while making the provider, permissions and commercial relationship visible.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Capability 03

OAuth and scopes

Grants a connected app specific permissions without sharing a user's login credentials.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Lets an administrator review what an integration can read or change before approving it.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Capability 04

Public API

Provides authenticated endpoints for supported CRM, conversations, calendars, opportunities, payments and other resources.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Allows a governed external system to read or update selected HighLevel data.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Capability 05

Webhooks

Delivers supported event notifications to a configured external endpoint.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Lets another system react to a change without repeatedly polling for it.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Capability 06

Connected app management

Shows and manages authorised app connections and their account-level installation state.

How it works: Exchanges supported data or events through an authorised connection, scope or documented interface.
Why use it: Provides a review point for removing access that is no longer needed.
Plan for: External availability, rate limits, schema changes, permissions and data-controller duties still apply.
Your team owns: An owner must approve access, monitor failures and remove connections that are no longer needed.

Integration directory

Use a status that says what the connection really is.

Payments, accounts, calendars, email, lead sources and connector tools may all be relevant. Each candidate must be classified before it is advertised.

Check during setup

Native or direct

A supported connection may be available in the platform, but account ownership, plan access, objects and sync behaviour still need testing.

Scope required

Connector or API

A connector, public API or webhook may bridge systems. Authentication, limits, mapping, monitoring and additional charges remain part of the design.

Use only after testing

Manual or controlled exchange

A controlled import or export can be safer than an untested sync. Use a manual route until the connection, mapping and failure behaviour have been tested.

Data movement

Decide which system leads before records start moving.

A connection can create duplicate records, stale values or silent gaps if both systems are treated as authoritative for the same information.

Direction

Document whether data moves into CRM, out of CRM or both ways, including which fields are excluded.

Identity and duplicates

Choose matching rules for contacts, organisations, appointments and transactions before the first live run.

Failure and removal

Make expired credentials, rejected records and disconnection visible to a named owner instead of assuming continuous success.

Across the service chain

Keep account and data responsibilities visible.

The customer, 121 and each connected supplier retain different responsibilities when information moves between systems.

121 CRM · Data responsibility chain

Customer

Lawful inputs, users, instructions and acceptance

121

Agreed configuration, access handling and documented boundaries

Connected supplier

Service operation, account terms and supplier controls

Access follows named roles

Changes retain evidence

Assurances need approval

Illustrative exampleConceptual responsibility view, not a published certification or exhaustive data-flow diagram.

Before enabling

Check permissions, costs and support across the full chain.

The platform, connector and destination provider may each have different plans, terms and operating limits.

Connection owner

Name who controls each supplier account, grants access and responds when credentials or permissions change.

Confirm separately

Commercial boundary

Confirm platform, connector, usage and supplier charges. The CRM checkout does not list integration access or running costs.

Human approval

Acceptance evidence

Test representative creation, update, duplicate, failure and removal cases, then record what was accepted by the customer.

Questions about this page

Useful answers, without the sales fog.

1. Does 121 CRM integrate with our existing software?

Potentially, but no general compatibility promise is made. 121 needs the exact product, account, plan, objects, direction, permissions, limits and support expectation before confirming a route.

2. Are integrations included in the CRM subscription?

The approved checkout does not state which integrations, connectors, API work or third-party charges are included. Confirm each required connection separately.

3. What happens if a connection stops working?

Important integrations should expose failure to a named owner and have a documented recovery or manual fallback. No universal monitoring or recovery commitment is currently approved.

Read all CRM questions

Continue the journey

Workflow automation Appointments Migration checklist

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing