Resources · Make integration

Immoflux Make integrationAutomate Immoflux with Make.

Stop retyping the same contact into Immoflux by hand. The Immoflux Make integration gives you 30 modules, 21 actions and 9 searches, to write and read contacts, leads, properties and requests. This page shows how to connect your account and build a first scenario.

Try the Immoflux integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Immoflux Make integration do for you?

The Immoflux Make integration links your Immoflux account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that creates, reads, updates or deletes a record. Data from your other apps can then land in Immoflux without copy and paste.

New inquiries land as leads. A form tool or a mailbox catches the inquiry, Create a Lead files it in Immoflux, and Create a Activity logs the follow-up so an agent sees it on the record.

Listings stay in sync with a spreadsheet. When a row changes in the sheet your team maintains, Update a Property pushes the new values to the property that matches, found first with Get a Property by ID.

Exports without the export button. List Contacts or List Requests hand every matching record to the next module, which can copy them into a sheet or a reporting tool.

One thing Make does not give you here: a trigger. Immoflux has no module that starts a scenario, so the flow opens on another app or on a schedule. The official documentation is also limited for this app, which is why each note below sticks to what the module name tells you. Before a big project, a Make review and a look at Make pricing help you size the plan. The same kind of app often has an n8n node too, and n8n vs Make lays out how the two tools differ.

Connect

How do you connect Immoflux to Make?

  1. 01

    Add an Immoflux module

    In your scenario, click the +, type Immoflux and pick any module, for example List Agents. Then click Create a connection. A connection is your Immoflux account linked to Make once, and every Immoflux module reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when you manage several accounts. Then either authorize Make on the Immoflux page that opens, or paste the key Immoflux gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, the fields should now fill with what Make can read from your account. If the list stays empty, the connection did not go through and needs a second try.

First scenario

Your first scenario: turn an inquiry into a lead with a follow-up

GoalWhen a prospect sends an inquiry through another app, Make creates the lead in Immoflux and logs an activity on it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module comes from the app where inquiries arrive, since Immoflux has no trigger of its own.

  2. 02

    Add Create a Lead

    Click the + to the right of that first module, search Immoflux and pick Create a Lead. Create the connection, then map the details of the inquiry into the fields Make shows.

  3. 03

    Log the follow-up

    Add Create a Activity after it. Map the lead returned by the previous module so the activity is attached to the right record, and write the note your agent should read.

  4. 04

    Test with Run once

    Send a test inquiry, then click Run once. Each module shows the bundles it received, one bundle being one item passed along. Open Immoflux and check the lead and its activity.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation, the unit Make bills on your plan.

Modules

Every Immoflux module in Make, explained

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

Immoflux1

Create a Activity

ActionIn the docs only

This module writes a new activity into Immoflux, so a call, a visit or a reminder shows up on the record without anyone typing it. It acts on one item per run.

When to use it
right after a lead or a request is created, to leave the agent a trace of what happened and what comes next.
Watch out
map the record the activity belongs to from the previous module, or it lands unattached.
Immoflux2

Create a Contact

ActionIn the docs only

You get a fresh contact card in Immoflux, filled from whatever the previous module passed along: a form answer, a signed document, a row. One contact per bundle.

When to use it
when the person is a known client or owner rather than a prospect still to qualify.
Watch out
the module simply creates. Run List Contacts first if the same person may already exist, or you end up with duplicates.
Immoflux3

Create a Lead

ActionIn the docs only

Every inquiry caught elsewhere becomes a lead in Immoflux, ready for an agent to qualify. This is usually the first Immoflux module people add.

When to use it
behind a web form, a portal notification or an email parser, when you want the prospect in the pipeline before anyone calls back.
Watch out
test it with Run once on a fake inquiry, then delete that test lead so it does not sit in the pipeline.
Immoflux4

Create a Property

ActionIn the docs only

Adds a property to Immoflux from data prepared in another tool, which saves re-entering a listing field by field.

When to use it
when your listings are drafted in a spreadsheet or a form and should reach Immoflux once they are approved.
Watch out
values such as the city or the zone may need to match what Immoflux already knows; List Cities and List Zones let you check what the account returns before you map them.
Immoflux5

Create a Request

ActionIn the docs only

Records a request in Immoflux, the kind of item you create when someone describes what they are looking for, so the team can match it later.

When to use it
when a search form or a chatbot collects a buyer's or tenant's criteria and you want them stored next to the contact.
Watch out
create or find the contact first, then map it here, so the request is not an orphan.
Immoflux6

Delete a Contact

ActionIn the docs only

Removes one contact from Immoflux for good, which keeps the base clean when a person asks to be forgotten or turns out to be a duplicate.

When to use it
at the end of a cleanup flow, after a search has isolated exactly the contact to drop.
Watch out
a delete cannot be undone from Make. Test the flow with Run once before adding this module, read the bundle the search returns, then add the delete.
Immoflux7

Delete a Lead

ActionIn the docs only

With this module, a lead disappears from Immoflux as soon as the scenario reaches it, handy for test leads and spam that slipped through a form.

When to use it
once an earlier step has flagged an obvious junk inquiry, or to clear the leads you created while testing.
Watch out
nothing brings the lead back. Be sure of the selection, and log what you delete in a sheet if you may need the trace later.
Immoflux8

Delete a Property

ActionIn the docs only

Takes a property off Immoflux entirely, not just out of view, so it stops appearing in lists and exports.

When to use it
when a listing entered twice or by mistake has to go, and the decision was made in another tool you trust.
Watch out
a property may have requests or activities around it. Check them with List Requests or List Activities before deleting, since Make cannot restore it.
Immoflux9

Delete a Request

ActionIn the docs only

Erases one request from Immoflux, which keeps agents from chasing criteria nobody holds anymore.

When to use it
when a request was created twice by a form, or the client confirmed they have stopped looking and your team prefers removal over an update.
Watch out
if you only want to mark the request as closed, Update Request is the safer move; a deletion is final.
Immoflux10

Delete an Activity

ActionIn the docs only

Drops a single activity from Immoflux, so a timeline cluttered by automated entries becomes readable again.

When to use it
your scenario logged wrong activities? Fix it first, then clear them.
Watch out
pair it with List Activities to target the right ones, and test on a single bundle first; the removed activity does not come back.
Immoflux11

Get a Activity

ActionIn the docs only

Reads back one activity from Immoflux so its details become available to the following modules, for a message, a sheet row or a decision.

When to use it
when an earlier step gave you a reference to an activity and you need what it contains, not just that it exists.
Watch out
it returns one activity, not a list. To go through several, List Activities is the right module.
Immoflux12

Get a Contact by ID

ActionIn the docs only

Hand it the ID of a contact and it returns that contact's full record, ready to map into the next module.

When to use it
when a lead, a request or another app already carries the contact's Immoflux ID and you need the details behind it.
Watch out
without an ID there is nothing to fetch. If you have no ID yet, look the person up with List Contacts first.
Immoflux13

Get a Lead by ID

ActionIn the docs only

Pulls a single lead from Immoflux by its ID, so a later step can send its details to a chat tool or a sales sheet.

When to use it
after Create a Lead or Update a Lead, when you want the stored version of the lead rather than the raw form data.
Watch out
map the ID from the module that returned it; a typed test value will break as soon as the scenario runs on real data.
Immoflux14

Get a Property by ID

ActionIn the docs only

Fetching one property by its ID gives the next modules everything Immoflux holds on that listing, for a brochure, an email or a check.

When to use it
when a request or an activity points to a property and you need its details to build a message to the client.
Watch out
it reads, nothing more. To change the listing, follow it with Update a Property.
Immoflux15

Get a Request by ID

ActionIn the docs only

Returns a single request with its content, so you can compare the criteria with a property or forward them to an agent.

When to use it
when the request ID arrives from a previous module and the scenario has to decide something based on what the client asked for.
Watch out
one ID, one request. Map it from the module that produced it rather than typing a test value.
Immoflux16

List Activities

SearchIn the docs only

This search returns the activities stored in Immoflux, each as its own bundle, so the next module handles them one after the other.

When to use it
to copy the activity log into a sheet, or to spot records nobody has followed up on.
Watch out
a search can return zero, one or many bundles, and every bundle the next module processes costs an operation.
Immoflux17

List Agents

SearchIn the docs only

Brings out the agents set up in your Immoflux account, one bundle each, so a scenario can pick who should own a new lead.

When to use it
you route inquiries by agent? Take the list from Immoflux, not from a copy someone keeps by hand.
Watch out
run it once and read the bundles to see which details each agent comes with before you build any routing on them.
Immoflux18

List Cities

SearchIn the docs only

Returns the cities your Immoflux account knows, one bundle per city, which helps when other data has to line up with them.

When to use it
before Create a Property or Create a Request, when the city typed in a form has to match an entry that already exists in Immoflux.
Watch out
the documentation says nothing about the fields returned. Test it with Run once and look at the bundle first.
Immoflux19

List Contacts

SearchIn the docs only

Searching your contacts gives you each matching person as a separate bundle, the basis for any duplicate check or export.

When to use it
before creating a contact, to see whether the person is already in Immoflux; or to feed a mailing tool with the base.
Watch out
an empty result is a valid result. Plan what the scenario should do when nothing comes back.
Immoflux20

List Counties

SearchIn the docs only

Counties recorded in Immoflux come out one by one, useful whenever an address or a search area has to fit the account's geography.

When to use it
when requests or properties arrive from a form with a free-text region that you want to check against Immoflux.
Watch out
treat it as reference data. Read the bundles once before mapping them, since the documentation gives no detail on their content.
Immoflux21

List Leads

SearchIn the docs only

Pull the leads from Immoflux into a scenario, one bundle per lead, and send them wherever your team tracks the pipeline.

When to use it
to build a report in a sheet, or to find leads that were never turned into a contact or a request.
Watch out
each lead the next modules process costs operations, so a large pipeline adds up on your plan.
Immoflux22

List Properties

SearchIn the docs only

All the properties this search finds arrive as separate bundles, ready to be written to a sheet, a site or a newsletter tool.

When to use it
when another channel needs your listings and you prefer Immoflux as the single place where they are edited.
Watch out
the search does not know what changed since the last run. Store what you already sent, or you will push the same properties again.
Immoflux23

List Requests

SearchIn the docs only

Here you collect the requests saved in Immoflux, each one ready to be matched, counted or forwarded by the modules that follow.

When to use it
after Create a Property, to find requests worth notifying about the new listing.
Watch out
matching criteria is your logic, not the module's. Decide how a request and a property count as a match before any email goes out.
Immoflux24

List Zones

SearchIn the docs only

Lists the zones defined in Immoflux, so a scenario can work with the same areas your team uses for properties and requests.

When to use it
when leads or requests should be routed by area and you want the zone list from Immoflux rather than a hardcoded copy.
Watch out
look at a test bundle before relying on it; the documentation does not describe what a zone contains.
Immoflux25

Make an API Call

ActionIn the docs only

Calls any endpoint of the Immoflux API with the connection you already set up, for everything the other Immoflux modules leave out.

When to use it
when you need an object or an action that no listed module covers, and the Immoflux API offers it.
Watch out
you write the request yourself, so you need the Immoflux API reference at hand. The Make documentation for this app does not describe the endpoints.
Immoflux26

Update Request

ActionIn the docs only

Changes an existing request in Immoflux, so the criteria your agents work from stay current when the client revises them.

When to use it
when a follow-up form, an email or a call note brings new information about what the client wants.
Watch out
you need the request's reference first, usually from List Requests or Get a Request by ID. Note that its name is written without the usual article in Make.
Immoflux27

Update a Activity

ActionIn the docs only

Edits an activity already in Immoflux, so it reflects what happened once the matching task moves in another tool.

When to use it
when your team completes tasks in a calendar or a task app and you want the Immoflux timeline to reflect it.
Watch out
map only the fields you mean to change, then check the result with Run once before switching the scenario on.
Immoflux28

Update a Contact

ActionIn the docs only

Keeps a contact card current: fresher details captured elsewhere reach Immoflux without anyone opening the record.

When to use it
after List Contacts found the person, when a form or another CRM brings fresher details.
Watch out
if the search returns several contacts, the update runs once per bundle. Narrow the search down to one before this step.
Immoflux29

Update a Lead

ActionIn the docs only

Moves a lead forward in Immoflux by changing its data, so the pipeline reflects what happened in a call tool or an email thread.

When to use it
when a prospect replies, books a visit or gets qualified in another app, and the lead should show it.
Watch out
keep the lead ID from Create a Lead or List Leads; without it Make cannot tell which lead to change.
Immoflux30

Update a Property

ActionIn the docs only

Rewrites the values of a property already in Immoflux, so a change made in your reference file reaches the listing without retyping.

When to use it
when the reference version of your listings lives in a sheet or a form and Immoflux should follow it.
Watch out
an empty mapped value may overwrite what was there. Test on one property with Run once and compare before and after.
Need help

Need help automating Immoflux with Make?

A person reads every message.

FAQ

Questions people ask about Immoflux and Make

01Is the Immoflux Make integration free?
Yes, Immoflux is a standard app in Make, so it works from the Free plan. That plan has limits worth knowing: 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) bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month, one operation being one module run on one bundle.
02What do you need to connect Immoflux to Make?
An Immoflux account and access to its authorization or its key. The Make documentation for Immoflux lists no prerequisite and no dedicated connection steps, so the generic flow applies: add any Immoflux module, click Create a connection, name it if you want, authorize Make on the Immoflux page or paste the key Immoflux gives you, then click Save. The connection is created once and reused by all 30 modules. If the module fields stay empty afterwards, the connection failed and should be recreated.
03Does the Immoflux Make integration work in real time?
Not on its own. Immoflux has no trigger in Make, neither scheduled nor instant, so no module watches Immoflux for changes. You start the scenario another way: with the trigger of another app, such as a form tool that calls Make through a webhook as soon as someone submits, or with a schedule on the first module, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, on paid plans 1 minute. The Immoflux modules then act inside that run.
04What if the Immoflux module you need is missing in Make?
Use Make an API Call. It is part of the 30 Immoflux modules and can reach any endpoint of the Immoflux API with the same connection, so an object or an action without a dedicated module is still within reach. You will need the Immoflux API reference, because Make's documentation for this app is limited and does not describe the endpoints. The other option is to handle that part in another app of your scenario and keep Immoflux for the records the dedicated modules cover.
05Should you use Make or n8n for Immoflux?
It depends on which tool your team already runs. In Make, Immoflux comes with 30 ready modules: 21 actions and 9 searches, plus Make an API Call for the rest, and no trigger. Many apps also have an n8n node, so check whether Immoflux has one before choosing, and compare the modules each side offers for the records you care about. If you already build scenarios in Make, staying there keeps every connection in one place. Neither choice is better by default; what matters is coverage for your case.
Same platform

Other docs you might need on this stack.

Browse all integrations