Resources · Make integration

7Loc Make integrationAutomate 7Loc with Make.

Can Make pick up your 7Loc data and pass it to the rest of your tools? The 7Loc Make integration gives you 1 module, a trigger that watches 7Loc data. This page is for marketers who know 7Loc and are new to Make: connect the account, build a first scenario, test it.

Try the 7Loc integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 7Loc Make integration let you automate?

The 7Loc Make integration links your 7Loc account to Make, a no-code tool where you chain apps into a scenario (the automation you build). On the 7Loc side you get exactly one module, Watch any entity data, which starts a scenario when Make finds 7Loc data to hand over to another app.

Because the app only has a trigger, every useful scenario starts in 7Loc and ends somewhere else. Three shapes are worth trying. First, a shared log: Watch any entity data opens the flow and the next module writes each item into the spreadsheet or database your team already reads. Second, a heads-up for the team: the same trigger feeds a messaging module, so nobody has to open 7Loc to spot what came in. Third, a CRM kept in step: the trigger passes each item to your CRM module, and sales work from one screen.

Now the limits, stated plainly. Make's own documentation for 7Loc is marked as limited: it lists the module but gives no description, no field list and no connection prerequisites. You will discover the fields inside the editor once your account is linked. The app has no action module and no Make an API Call module, so Make cannot write anything back into 7Loc.

New to Make? The Make training covers the editor from zero, and the Make review sums up what the platform does well and where it struggles. If 7Loc also shows up in n8n for you, the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect your 7Loc account to Make?

  1. 01

    Add the 7Loc module

    In a scenario, click the + and search for 7Loc, then pick Watch any entity data. Make asks for a connection (your 7Loc account linked once, then reused by every 7Loc module). Click Create a connection to start.

  2. 02

    Name the connection

    This step is optional, but a clear name like "7Loc marketing" helps the day you run several accounts. Make keeps the name in the connection list, so you pick the right one in a later scenario.

  3. 03

    Authorize and save

    Depending on how 7Loc handles access, you either sign in on a 7Loc page that asks you to authorize Make, or paste the key 7Loc gives you. Then click Save. The documentation lists no prerequisite, so start with the account you use daily.

First scenario

Your first scenario with 7Loc

GoalWhen Watch any entity data finds 7Loc data, Make passes each item to a module of another app.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. An empty canvas appears with a large +. Click it: that is where the first module, the one that starts everything, goes.

  2. 02

    Place the 7Loc trigger

    Search for 7Loc, choose Watch any entity data and select the connection you made earlier. Make then lists what it can read in your account, so you pick from a menu instead of typing names by heart.

  3. 03

    Add the destination

    Click the + on the right of the 7Loc module and add the app that should receive the data: a sheet, a CRM, a chat tool. Map the 7Loc values into its fields by clicking them in the panel Make shows you.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows, above each module, the bundles it received (a bundle is one item passing from module to module). Open them to confirm the right data arrived.

  5. 05

    Schedule and switch on

    Click the clock on the 7Loc module to set how often Make checks; a new scenario checks every 15 minutes by default. Then flip the switch to turn the scenario on, and it keeps running without you.

Triggers

What starts a 7Loc scenario?

1 module starts a scenario when something happens in 7Loc. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by 7Loc as soon as it happens.

7Loc1Watch any entity data

Watch any entity data

triggerIn the docs only

This trigger is your single way into 7Loc from Make: it collects 7Loc data and hands each item to the modules that follow, one bundle at a time. Make's documentation names it without describing which records it covers, so open it after connecting to see what it offers.

How it fires
scheduled, Make checks the app on the scenario's schedule. This type is inferred from the module's name, since Make gives no official description.
When to use it
whenever 7Loc data needs to reach a sheet, a CRM or a team channel without anyone copying it by hand.
Watch out
on the Free plan Make waits at least 15 minutes between two checks, so data shows up downstream with that delay.
Need help

Need help automating 7Loc with Make?

A person reads every message.

FAQ

Questions people ask about 7Loc and Make

01Is the 7Loc Make integration free?
Yes, 7Loc is a standard app in Make, so you can use it on the Free plan. That plan has real 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. Every module run counts as an operation, which is what Make tallies on your plan. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. This page quotes no price for 7Loc itself.
02What do you need to connect 7Loc to Make?
A 7Loc account and a Make account are enough to start, since Make's documentation lists no other prerequisite. You add the 7Loc module, click Create a connection, optionally name it, then either authorize Make on a 7Loc page or paste the key 7Loc provides, and click Save. The documentation for this app is marked as limited, so if the screen asks for something unexpected, check with 7Loc which credentials its account area gives you before retrying.
03Does the 7Loc Make integration trigger react instantly?
No. Watch any entity data is listed as a scheduled trigger, which means Make checks 7Loc on the scenario's schedule instead of 7Loc alerting Make the moment something happens. A new scenario checks every 15 minutes by default. On a paid plan you can shorten that interval to 1 minute; on the Free plan 15 minutes is the floor. Keep in mind the scheduled type is inferred from the module's name, because the documentation does not describe it.
04What if the 7Loc module you need is missing in Make?
It depends on what you need. The integration has one trigger and nothing else: no action, no search and no Make an API Call module, so Make cannot create or update anything inside 7Loc. If your plan relies on writing data into 7Loc, check whether another tool you use connects to it, or ask the Hack'celeration team to review the case. The documentation is limited too, so some behavior only becomes clear once you test the trigger with Run once.
05Should you use Make or n8n with 7Loc?
It depends on your criteria rather than on a winner. The same app often has an n8n node as well, so first check that 7Loc really appears there and what that node offers. In Make, you get a single scheduled trigger that sends 7Loc data to other apps, with a visual editor and a Free plan to try it. Compare which operations each tool gives you for 7Loc, the team skills you have, and where your other apps already run.
Same platform

Other docs you might need on this stack.

Browse all integrations