# Make CRM integration | 121 CRM > Understand how Make may connect with 121 CRM, including the documented data flow, permissions, limitations, testing and ownership needed. A useful decision about connecting Make begins with the real data flow, not a logo on an integrations page. This Make guide explains the documented method, practical setup or migration sequence, important limits and the acceptance checks a small business should complete before relying on it. ## A connection with a named job Fictional example using Bramble Heating; supplier capability is documented, while account availability and 121 service scope still need agreement for each customer. ## Capabilities explained ### 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 a business would use it:** Provides a maintained connection path for common services without a bespoke integration. **Limitations:** External availability, rate limits, schema changes, permissions and data-controller duties still apply. **Human responsibility:** An owner must approve access, monitor failures and remove connections that are no longer needed. ### 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 a business would use it:** Lets another system react to a change without repeatedly polling for it. **Limitations:** External availability, rate limits, schema changes, permissions and data-controller duties still apply. **Human responsibility:** An owner must approve access, monitor failures and remove connections that are no longer needed. ### Triggers Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Lets follow-up begin from a business event instead of waiting for someone to remember. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ### Testing and execution logs Supports test runs and operational evidence used to diagnose why a record did or did not follow a path. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Gives a human a way to verify automation and investigate exceptions. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ### Users, roles and permissions Controls whether a user acts at agency or sub-account level and which supported areas they can access. **How it works:** Controls agency or sub-account configuration that determines access, packaging, governance or billing. **Why a business would use it:** Limits day-to-day access to the work a person actually needs to perform. **Limitations:** Availability and control depth depend on agency plan, role and current account configuration. **Human responsibility:** An authorised administrator must review, approve and audit material changes. ## How the Make connection currently works The provider documentation reviewed on 11 October 2026 describes this route: Use tested webhooks or a maintained connector scenario to move a defined payload between HighLevel and another service. Treat the Make method as a starting boundary, because permissions, editions and configured options can change the actual result. ### What the current documentation supports HighLevel documents inbound and outbound webhook patterns compatible with automation platforms such as Make. For Make, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### Another supported part of the documented scope A scenario can transform fields and call a supported destination action. For Make, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### A practical business question Which single customer or team action should become easier because Make is connected? If the answer is unclear, the business is not ready to approve access. ## A controlled way to connect Make Use a bounded, reversible Make test before any live change; this sequence is practical guidance, not a promise that 121 has access to either account or that every step is included in a 121 package. ### 1. Name the business event Start with one event that matters, such as a booking, message, payment or status change. Do not connect Make merely because a connector exists; apply that check to the documented Make route. ### 2. Grant the minimum access Use an account owned by the business, record who can reconnect or revoke it, and approve only the permissions needed for the documented flow; apply that check to the documented Make route. ### 3. Test both the happy path and failure Use fictional data to confirm the expected record, owner, timestamp and next action. Then revoke a permission or use invalid data in a safe test to see how the failure becomes visible; apply that check to the documented Make route. ### 4. Monitor the live boundary Assign an owner for failed runs, expired tokens, duplicates, provider changes and usage charges. Review the connection when either supplier changes its terms or data model; apply that check to the documented Make route. ## How Bramble Heating could test the decision Bramble Heating is a heating and service team. Its fictional Make records and narrow acceptance test demonstrate the method without implying a live connection or customer result. ### The operating need The team needs one Make event to create a visible, owned action without retyping or leaving credentials with an individual. ### The trial Bramble Heating wants Make to support one clear handover. The team connects a non-production test where available, sends one fictional event through the documented path and checks the resulting contact, timestamp, owner and next action before enabling wider use. ### The evidence Bramble Heating's reviewer keeps the Make source count, test input, mapped output, timestamps, owner, exception log and configured-permission evidence; a pass means this agreed scenario behaved as expected, not that every future scenario is guaranteed. ### The decision Bramble Heating names an owner to accept, revise or reject the Make design; anything unexplained remains outside live use until it has a documented rule, monitoring route and human response. ## What to check before relying on Make Make documentation establishes general capability, not customer-specific availability, commercial inclusion or a 121 migration commitment; put those boundaries in the decision rather than small print after go-live. ### What the connection or export does not solve Connector modules and external-app coverage change independently of HighLevel. ### A second boundary to plan around Operations, retries and premium-action usage can create charges and duplicate effects unless tested. ### Account and commercial boundary Confirm the relevant HighLevel, Make and connector plans, permissions, usage charges and supplier terms in the customer's own accounts. This Make page does not claim that integration or migration work is included in the 121 subscription. ### Live acceptance still required Before live Make use, confirm an owned connection, run a representative test, reconcile results and record failure handling; no live account test was performed for this public guide, so those checks remain customer-specific implementation work. ## Frequently asked questions ### Is the Make integration included with every 121 CRM account? Not necessarily. The supplier documents a general platform capability, but the relevant HighLevel feature, Make plan, permissions, connector and usage charges must be confirmed for the customer's own configuration. ### What data moves through the Make connection? HighLevel documents inbound and outbound webhook patterns compatible with automation platforms such as Make. A scenario can transform fields and call a supported destination action. The exact fields and direction should be confirmed in a test because configured options and provider changes can alter the result. ### What happens when the Make connection fails? The design should expose failed runs, revoked permissions, expired tokens or rejected data to a named owner. Test the failure path safely, record retry and duplicate rules, and keep a manual recovery route. ### Does 121 promise to configure or support the Make connection? This guide explains the documented capability and a sensible acceptance method. Any 121 configuration, migration, monitoring or support commitment must be agreed explicitly for the customer and is not created by this page. ## Related CRM pages - [/crm/integrations](https://121.direct/crm/integrations) - [/crm/security-data](https://121.direct/crm/security-data) - [/crm/guides/crm-vendor-due-diligence](https://121.direct/crm/guides/crm-vendor-due-diligence) - [/crm/integrations/shopify](https://121.direct/crm/integrations/shopify) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.