Resources · Make integration

Element451 Make integrationAutomate Element451 with Make.

Can Make write into Element451 without a line of code? Yes. The Element451 Make integration gives you 10 modules, 9 actions and 1 search, fed by your other tools. Below: the connection, a first scenario, then every module in plain words.

Try the Element451 integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Element451 Make integration do for you?

The Element451 Make integration links your Element451 account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that searches or acts in an app. Element451 has no trigger in Make, so another app or a schedule starts the scenario, and Element451 receives the result.

Form replies that reach the record. A prospect answers a form in another tool. The scenario runs Find a User ID to locate that person, then Add a Note or Create Form Submission, and the answers sit in Element451 instead of someone's inbox.

Follow-ups nobody forgets. A booking or a support ticket elsewhere can become an Add a Task for whoever handles the file, or an Add an External User Event that keeps a trace of what happened outside Element451.

Data moved in bulk. Going by their names, Import Data and Export Data are the pair for exchanges with a spreadsheet or another database, where rows would otherwise be copied by hand.

One honest limit: Make's own documentation for Element451 is thin, because there isn't enough public information about the app. Modules come without field details, so test each one with Run once, and keep the Make troubleshooting guide close. If you are also weighing n8n, the n8n vs Make comparison puts both tools side by side, and the Make review covers the editor itself.

Connect

How do you connect Element451 to Make?

  1. 01

    Add an Element451 module

    In your scenario, click the + and search for Element451. Pick any module, Add a Note for instance, then click Create a connection. The connection is your Element451 account linked to Make once and reused by every Element451 module.

  2. 02

    Name the connection

    This step is optional. A clear name, such as the account or the team it belongs to, saves you from guessing later when you have more than one Element451 account to plug into your scenarios.

  3. 03

    Authorize and save

    Make then asks for access: either an Element451 authorization page or a key that Element451 gives you, to paste in the field. Finish with Save. From there, Make can list what the modules read from your account.

First scenario

Your first Element451 scenario

GoalWhen someone fills a form in another app, Make finds that person in Element451 and adds a note to their record.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Here it is your form tool, which sends each new reply as a bundle: one item passed to the next module.

  2. 02

    Add Find a User ID

    Click the + on the right of the form module, search for Element451 and choose Find a User ID. Create the connection, then map the form data that identifies the person into the fields Make shows.

  3. 03

    Write the note

    Add Add a Note after the search. Map the user ID the search returned, then the form answers. Make lists the module's fields once the connection exists, so you pick rather than guess.

  4. 04

    Test with Run once

    Click Run once, send a test reply through your form, and read the bundles each module received. If Find a User ID returns nothing, the note has nobody to attach to: fix the mapping first.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan. Then switch the scenario on and let it work.

Modules

What each Element451 module does

Element451 gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Element4511

Add a Note

ActionIn the docs only

This action writes a note into Element451 from your scenario, so context gathered elsewhere, like a form answer or a call summary, stays where your team will read it.

When to use it
right after Find a User ID, when a prospect's reply in another tool should be visible to whoever opens their file.
Watch out
the doc does not describe the module's fields, so open it once connected and check what Make asks for before mapping.
Element4512

Add a Task

ActionIn the docs only

Turn an event from another app into a to-do inside Element451. As its name says, Add a Task creates a task, which keeps the follow-up in the tool where your team already plans its work.

When to use it
when a booking, a missed call or a ticket elsewhere means someone has to act on a person's file.
Watch out
a task needs someone to find it; run the scenario once and confirm where the task shows up before switching it on.
Element4513

Add an Activity

ActionIn the docs only

You get a logged activity in Element451 without typing it. The module records an activity from your scenario, which is handy when a contact with a person happened in a tool Element451 does not see.

When to use it
choose it over Add a Note when the point is to mark that something happened, not to write a longer remark.
Watch out
Make lists no field details for it; open it once connected and look at what Make asks for before mapping.
Element4514

Add an External User Event

ActionIn the docs only

Events that happen outside Element451 can still end up in it. This action sends an external user event, which makes sense when the moment you care about lives on your website, in a webinar tool or in a payment app.

When to use it
when another app fires as a person does something there, and you want that trace inside Element451.
Watch out
the doc gives no field detail; run it once and check where the event lands in Element451.
Element4515

Create Conversation

ActionIn the docs only

Open a conversation in Element451 straight from a scenario. The benefit is that an exchange started in another channel gets a place in Element451, where the rest of the team can pick it up.

When to use it
a message arrives through a chat tool or a contact form, and the reply should happen from Element451.
Watch out
the doc says nothing about which channels this module covers, so test a single run on your own account before relying on it.
Element4516

Create Form Submission

ActionIn the docs only

Answers collected by a form tool other than Element451 can be recorded as a form submission in Element451. That keeps every reply in the same place, whatever tool the person filled in.

When to use it
pick it over Add a Note when the answers should count as a real submission, not as free text on the record.
Watch out
the doc lists no fields for it; connect first, then look at what Make offers to fill before mapping.
Element4517

Export Data

ActionIn the docs only

Need Element451 data somewhere else? Export Data is the module whose name points to pulling data out of Element451, so another module in the scenario can send it to a spreadsheet or a reporting tool.

When to use it
when a report or another database has to be fed with what Element451 holds.
Watch out
each module run counts as an operation on your Make plan, and the doc gives no detail on what the export contains; inspect the output bundle with Run once.
Element4518

Find a User ID

SearchIn the docs only

The only search of the app returns the ID of a user in Element451, which, judging by the module names, is how you point the other modules at the right person.

When to use it
place it first after your trigger, then map its result into Add a Note, Add a Task or Add an Activity.
Watch out
a search can return zero, one or several bundles. Zero means the next modules have no one to work on, so add a filter or a fallback.
Element4519

Import Data

ActionIn the docs only

Going the other way from Export Data, Import Data sends records into Element451 from your scenario, so rows collected in a spreadsheet or another app stop being retyped by hand.

When to use it
choose it when a batch of records has to arrive together, rather than one note or task at a time.
Watch out
Make's documentation lists no fields or formats for this module. Try a small test file with Run once before sending a large batch.
Element45110

Make an API Call

ActionIn the docs only

When none of the nine other modules covers your case, Make an API Call reaches any endpoint of the Element451 API, with the same connection you already created.

When to use it
for an action the list does not offer, once you know which endpoint you need.
Watch out
this module asks you to know the API. Make gives no Element451 detail for it, so check the endpoint and test with Run once before wiring the rest of the scenario.
Need help

Need help automating Element451 with Make?

A person reads every message.

FAQ

Questions about Element451 and Make

01Is the Element451 Make integration free?
Yes. Element451 is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits per month, one operation for each module run on one bundle. This page gives no price, for Make or for Element451.
02What do you need to connect Element451 to Make?
An Element451 account and a Make account are enough to start. Make's documentation lists no prerequisite and no steps specific to Element451. You follow the generic path: add an Element451 module, click Create a connection, optionally name it, authorize Make on the Element451 page or paste the key Element451 gives you, then click Save. That connection is created once and reused by all 10 modules. If the window asks for something the steps do not mention, test one module with Run once before building more.
03Does Element451 trigger Make scenarios in real time?
No. Element451 has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. Two ways around it. Either another app starts the flow: an instant trigger in that app calls Make through a webhook as soon as something happens, and the Element451 modules follow. Or you use the schedule on the first module: a new scenario runs every 15 minutes by default, and paid plans go down to 1 minute. In both cases Element451 is the destination of the scenario, not its starting point.
04What if an Element451 module is missing in Make?
Use Make an API Call. It is the tenth module of the app, and it can call any endpoint of the Element451 API with the connection you already have, so you do not create a second one. The catch is knowledge: you need to know which endpoint does what you want. Make's documentation for Element451 is limited, since there is not enough public information about the app, so expect to test each call with Run once and read the returned bundle before you trust it in a live scenario.
05Make or n8n for Element451?
It depends on what you need to do in Element451. In Make, the app offers 10 modules: 9 actions and 1 search, plus Make an API Call for the rest, and no trigger. The same app often has an n8n node too. Before you choose, list the actions your process needs, then check that the tool you consider covers each of them, and how it would start the flow since Element451 cannot. There is no winner to name here, only a fit with your process and with the tool your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations