Benetics AI Make integrationAutomate Benetics AI with Make.
Can Make open projects and tasks in Benetics AI for you? The Benetics AI Make integration gives you 8 action modules and no trigger. This page shows how to link your account, build a first scenario and pick the module that fits each job.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Benetics AI Make integration do?
The Benetics AI Make integration lets a Make scenario, the automation you build as a chain of modules, act on your Benetics AI account. Each module is one brick of that chain. Going by their names, since Make gives them no description, the 8 modules create projects and tasks, upload documents and plans, and look up users. All of them are actions, so another app or a schedule has to start the scenario.
Projects that open themselves. When a new job is confirmed in the tool your sales team uses, Create a Project can set up the matching project in Benetics AI, and Create a Task can add its first to-do right after.
Files where the crew expects them. A plan or a report received somewhere else can reach Benetics AI through Upload a Plan or Upload a Document, so nobody downloads and re-uploads it by hand.
A fallback for the rest. Get a User, as its name suggests, brings one user's details into the scenario, and Make an API Call reaches the parts of the Benetics AI API that the other modules leave out, with the same connection.
Know this before you start: Make states that it cannot fully document Benetics AI yet, because too little public information exists about the app. Test every module with Run once before relying on it. The app may also have an n8n node; the n8n vs Make page explains how the two tools differ, Make pricing covers the plans, and Make training helps if the editor is new to you.
How do you connect Benetics AI to Make?
- 01
Add a Benetics AI module
In your scenario, click the +, type Benetics AI in the search box and pick any of its modules. The connection, which is your Benetics AI account linked to Make once, starts from that first module and is then reused by every other one.
- 02
Create the connection
Click Create a connection. Make lets you give it a name. That step is optional, but a clear name saves confusion later if you ever link a second Benetics AI account to Make.
- 03
Authorize and save
Depending on what Make asks, either approve access on the Benetics AI page that opens, or paste the key Benetics AI gives you. Then click Save, and the module can talk to your account.
Your first scenario with Benetics AI
GoalWhen a new job is confirmed in another app, Make creates the project in Benetics AI and adds its first task.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. The first bubble belongs to the app where jobs get confirmed, such as your CRM or a form tool, because Benetics AI has no trigger.
- 02
Add Create a Project
Click the + to the right of that first module, search Benetics AI and choose Create a Project. Create the connection, then map the job details from the first module into the fields Make shows.
- 03
Chain Create a Task
Add Create a Task after it. Map data from the previous module, such as the project it just created if Make lists it, then describe the task every new job should start with.
- 04
Test with Run once
Click Run once and confirm one real job in the first app. Each module then shows the bundles it received, a bundle being one item passed along, so you can see what Benetics AI sent back.
- 05
Schedule and switch it on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Every module run is one operation, the unit Make counts on your plan.
What each Benetics AI module does
Benetics AI gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Project
ActionIn the docs onlyA new project in Benetics AI, created by your scenario instead of by hand: that is what the name Create a Project promises, since Make gives it no official description. It is usually the first Benetics AI step of a flow.
Create a Task
ActionIn the docs onlyYou get a to-do inside Benetics AI that nobody had to type, which is the job its name gives Create a Task. Pair it with Create a Project when every new project opens with the same first step, so nobody has to remember it.
Get a User
ActionIn the docs onlyDetails about one Benetics AI user, brought into the scenario so the next module can use them. That reading comes from the module's name alone, as Make publishes no description for Get a User.
Make an API Call
ActionIn the docs onlyAccess to whatever the Benetics AI API offers beyond the seven named modules, through the connection you already set up. Make an API Call is the way out when no module in the list matches your need.
New Project Events
ActionIn the docs onlyA look at what happens on your Benetics AI projects, if the name holds true. Make files New Project Events as an action, not a trigger, and gives it no description, so it cannot start a scenario on its own.
New Task Events
ActionIn the docs onlyTask activity from Benetics AI, pulled into your scenario, is what New Task Events suggests. Like its project counterpart, Make lists it among actions with no official description, which leaves its exact output to discover.
Upload a Document
ActionIn the docs onlyFiles sent straight from your scenario into Benetics AI, so documents stop travelling by email. That is the promise of Upload a Document, which Make leaves undescribed; it would take the file from an earlier module.
Upload a Plan
ActionIn the docs onlyPlans reach Benetics AI through their own module, kept apart from Upload a Document. Make does not explain the difference, so the name is your only guide: Upload a Plan is probably meant for drawings rather than general paperwork.
Need help automating Benetics AI with Make?
A person reads every message.
