Resources · Make integration

1net CRM Make integrationAutomate 1net CRM with Make.

Can Make drop fresh leads straight into the right 1net CRM group? Yes. The 1net CRM Make integration gives you 2 action modules, one for groups and one for any API call. This guide is for people who know 1net CRM and are new to Make, and it walks you to a working first scenario.

Try the 1net CRM integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 1net CRM Make integration do?

The 1net CRM Make integration links your CRM account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that does a single job. On the 1net CRM side, you get two actions, so the app never starts a scenario on its own; another app or a schedule does.

Signups sorted on arrival. When someone fills in a form in another tool, the Add Lead or Subscriber to a Group module places that person in the 1net CRM group you picked. Your sales team opens the CRM and finds the new names already filed.

Event registrations in their own list. A webinar or trade show sign-up in another app can feed a dedicated 1net CRM group, which keeps attendees apart from the rest of your contacts for the follow-up.

Anything else through the API. For what the group module does not cover, Make an API Call reaches any endpoint of the 1net CRM API with the same connection. That route asks you to read the API documentation of 1net CRM first.

Know the limits before you plan. Make itself says its documentation for 1net CRM is limited because little public information about the app exists, so test every step with real data. If you are still choosing a tool, the Make review and the n8n vs Make comparison help, and the Make troubleshooting guide covers errors you may meet along the way.

Connect

How do you connect 1net CRM to Make?

  1. 01

    Add a 1net CRM module

    In your scenario, search for 1net CRM, pick one of its two modules, then click Create a connection. A connection is your 1net CRM account linked to Make once, then reused by both modules.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as your company or workspace saves time later, when you manage several accounts and need to tell them apart in the dropdown list.

  3. 03

    Authorize and save

    Depending on what 1net CRM asks for, approve access on its own page or paste the key the app gives you. Then click Save, and Make can read what your account holds.

First scenario

Build your first scenario with 1net CRM

GoalWhen a new lead arrives from another app, Make adds that person to a group in 1net CRM.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Start from your lead source

    Since 1net CRM has no trigger, the first module comes from another app, such as the form tool where your leads sign up. Connect that app as it asks.

  3. 03

    Add the 1net CRM action

    Click the + on the right of the first module, search for 1net CRM and pick Add Lead or Subscriber to a Group. Link your account with Create a connection.

  4. 04

    Map the lead data

    Fill the module fields Make shows you, dragging in the lead details that arrive from the first module. Make lists what it can read once the connection works.

  5. 05

    Test with Run once

    Click Run once, send one test lead through your source, then open each module's bubble to read the bundle it received: one bundle is one item, here one lead.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What can the 1net CRM modules do?

1net CRM gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

1net CRM1

Add Lead or Subscriber to a Group

ActionIn the docs only

This action files one person into a 1net CRM group, so every new contact lands in the segment where your team expects to find it, without anyone copying names by hand.

When to use it
after a form, a registration or a purchase in another app, when that person belongs to a precise list.
Watch out
Make's documentation for this module is thin, so run a test with one real lead and check the group in 1net CRM before switching the scenario on.
1net CRM2

Make an API Call

ActionIn the docs only

This module gives you everything else the 1net CRM API offers, using the connection you already made, so a missing module does not stop your project.

When to use it
when you need an action the group module does not cover, and you know which endpoint of the API does it.
Watch out
you write the request yourself, so keep the 1net CRM API documentation open and check the answer in the bundle after Run once.
Need help

Need help automating 1net CRM with Make?

A person reads every message.

FAQ

1net CRM and Make: common questions

01Is the 1net CRM Make integration free?
Yes, 1net CRM is a standard app, so it works on the Make Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your 1net CRM subscription is a separate matter that Make does not cover.
02What do you need to connect 1net CRM to Make?
You need a 1net CRM account and a Make account. Make's documentation lists no special prerequisite for this app. You add a 1net CRM module, click Create a connection, optionally name it, then either approve access on the 1net CRM page or paste the key the app gives you, and click Save. The same connection then serves both modules. Since Make says its documentation for this app is limited, check your account settings in 1net CRM if the window asks for something unexpected.
03Does the 1net CRM Make integration react in real time?
No, because 1net CRM has no trigger module in Make, so nothing inside the CRM can start a scenario by itself. You start the flow from another app instead, for example a form tool whose trigger fires when a lead signs up, or from the schedule on the first module, which runs every 15 minutes by default. If your lead source has an instant trigger in Make (the lightning badge), the scenario starts as soon as that app calls Make, without waiting for the schedule.
04What if a 1net CRM module you need is missing in Make?
Use the Make an API Call module. It reaches any endpoint of the 1net CRM API with the connection you already set up, so you are not limited to the group action. You need the 1net CRM API documentation to write the request. Also keep in mind that Make describes its documentation for this app as limited, owing to the lack of public information, so test each call with Run once and read the returned bundle before activating.
05Should you pick Make or n8n for 1net CRM?
It depends on the criteria that matter to you, not on a ranking. On Make, 1net CRM offers 2 action modules plus the API call, with a visual editor and a Free plan to test on. The same app often has an n8n node too, so check the one available there and compare what each covers for your case: the actions you need, how you start the flow and how usage is counted. Try your exact scenario on both before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations