Becon Make integrationAutomate Becon with Make.
Can Make pull your Becon data into the rest of your stack? The Becon Make integration gives you 12 modules, 6 actions and 6 searches, all without code. This guide shows you how to link your account, build a first scenario and pick the right module.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Becon Make integration let you do?
The Becon Make integration lets Make read your Becon account inside a scenario, which is the automation you build in Make as a chain of modules. A module is one brick of that chain. Becon brings 12 of them: searches that return lists and actions that fetch one record, ready to pass on to your other tools.
A company directory that stays in sync. Start with List Companies, then feed each company into List Company Contacts. Every contact travels as a bundle, meaning one item passed from a module to the next, so the following module can write it into a sheet or a CRM.
An org chart you can reuse. List Company Departments and List User Departments tell you how teams are split, and Get Department Templates fetches the templates attached to a department. Useful when a routing rule depends on who owns what.
A clean user record. Get User Profile and Get User Phone Numbers bring back the details of one user, handy before an onboarding message or a call list.
Know the limit before you start: Make itself flags its Becon documentation as limited, because too little public information exists about the app. Field names become visible only once your connection is live. When a listed module stops short, Make an API Call reaches any endpoint of the Becon API with the same connection. The Make troubleshooting guide helps when a run fails, Make training covers the editor from scratch, and n8n vs Make sets the two tools side by side if you are still choosing.
How do you connect Becon to Make?
- 01
Add a Becon module
In your scenario, click the + and search for Becon. Pick any of its modules, then click Create a connection. A connection is your Becon account linked to Make once and reused by every Becon module afterwards.
- 02
Name it and authorize
Give the connection a name if you run several Becon accounts, for example one per client. Then authorize Make on the Becon page that opens, or paste the key Becon gives you, depending on what the window asks for.
- 03
Save and check
Click Save. Make now lists the Becon objects it can read directly inside the module fields. If those lists appear, the connection works.
Your first scenario with Becon
GoalWhen the scenario runs on its schedule, Make lists your Becon companies and pulls the contacts of each one.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + to place the first module. Becon has no trigger, so the scenario will start from its schedule.
- 02
Add List Companies
Search for Becon, pick List Companies and select your connection. This search returns every company as a separate bundle, so the rest of the scenario handles them one at a time.
- 03
Chain List Company Contacts
Click the + on the right of the first module and add List Company Contacts. Map the company from the previous module into it, so each company brings back its own contacts.
- 04
Test with Run once
Click Run once. Then read the bundles each module received. Each module run on a bundle counts as one operation on your Make plan.
- 05
Schedule and switch on
Click the clock on the first module. A new scenario runs every 15 minutes by default, and you can change that. Then switch the scenario on and add the module that should receive the contacts.
What each Becon module does
Becon gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Get Department Templates
ActionIn the docs onlyYou get the templates tied to one department, so a message or document can match the team it comes from. It acts on a single department at a time.
Get Property Map
ActionIn the docs onlyThis one hands you the property map of your Becon account, a useful reference before you match your data with the fields of another app.
Get User Phone Numbers
ActionIn the docs onlyPick this to retrieve the phone numbers stored for one Becon user, ready to feed a call list or a text message sent from another app in the same scenario.
Get User Profile
ActionIn the docs onlyReturns the profile of one user, a single bundle you can use to personalize whatever comes next, such as a welcome email or a record in your HR sheet.
Get a Contact
ActionIn the docs onlyFetch a single contact, which is lighter than listing a whole company when you already know who you want.
List Companies
SearchIn the docs onlyYour starting point for most Becon flows: it lists the companies in your account and sends each one on as its own bundle.
List Company Contacts
SearchIn the docs onlyBrings back the people attached to one company, each as a separate bundle, so you can copy a whole team into another tool in a single pass.
List Company Departments
SearchIn the docs onlyShows how a company is split into departments, one bundle per department, which helps when a rule depends on the team rather than on the person.
List Company Properties
SearchIn the docs onlyGives you the properties defined for a company, useful to understand which data you can move before you map anything into another app.
List Templates
SearchIn the docs onlyCollects every template available in your account, one bundle each, so you can review or archive them elsewhere without opening Becon.
List User Departments
SearchIn the docs onlyTells you which departments a given user belongs to, returned as one bundle per department, a quick way to route a request to the right team.
Make an API Call
ActionIn the docs onlyThe fallback for anything the other 11 modules miss: it calls any endpoint of the Becon API using the connection you already created, with no extra login.
Need help automating Becon with Make?
A person reads every message.
