Resources · Zapier integration

Mobilia Zapier integrationAutomate Mobilia with Zapier.

Mobilia on Zapier gives you 4 actions, 3 searches and 0 triggers. The Mobilia Zapier integration pushes leads, clients, tasks and visits into the CRM from your other tools, but something outside Mobilia always has to start the Zap.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mobilia Zapier integration does

It links Mobilia, a real estate CRM in Spain with built-in AI features, to the other apps you work with. Each automation, called a Zap, starts on an event in another app and then writes into Mobilia: a new client, a lead, a task or a visit. It can also look up an agent or a client first.

A lead for every web enquiry. A form on your site collects a request, and Create Lead files it in Mobilia with its operation type, status and source already set, so nobody retypes it.

A visit booked against the right agent. Create Visit files the viewing under one agent, through the required IdAgent field, and it can email the property owner once the visit is completed. When your source only knows the agent by email, Search Agent by Email finds them in Mobilia; check at test what it returns before you use it.

The caller's record, ready for the next step. Search Client by Phone pulls up the client behind a phone number logged in another tool and hands that record to whatever step comes next, with no email address needed.

What Zapier does not do here. Mobilia has no trigger on Zapier: nothing that happens inside the CRM can start a Zap. There is also no action to update or delete a record, only the four that create one. To weigh other tools, see our n8n vs Zapier guide and our Make vs Zapier guide.

Vocabulary

Zapier in one minute

Eight words you will meet in the editor, in plain terms.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap; once the Zap is on, Zapier waits for it. Mobilia has none, so yours comes from another app.
Action
What the Zap does once started: the step that writes, sends or moves something for you, like creating a lead in Mobilia.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those and nothing else.
Polling vs instant trigger
A polling trigger is checked on a timer for new items. An instant trigger is reported by its own app the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app, here an agent or a client, so the next steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a Mobilia Zap really costs

Zapier bills tasks, and with Mobilia only the actions that succeed decide the bill. The trigger, which sits in another app, never costs a task.

  • Mobilia on the free planYes, not reserved for paid plans
  • Free plan tasks100 per month
  • Free plan Zap size2 steps: one trigger, one action
  • Search or filterMulti-step Zap, paid plan

Each Mobilia action that goes through counts as one task; one that fails counts for nothing. Checking for new data is free, however often Zapier looks. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. Add a filter or a search and it becomes multi-step, which needs a paid plan. A few apps and actions take more than one task. The interval grid below applies to the polling trigger of the app that starts your Zap, since Mobilia has no trigger to check. To compare plans, see our Zapier review.

Connect

Connect Mobilia to Zapier

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens with a search box where you find any app Zapier supports by its name.

  2. 02

    Pick Mobilia and confirm

    Type Mobilia, select it in the results, then click Add connection. A new tab opens, where you sign in to Mobilia with the account you use for the CRM.

  3. 03

    Grant access

    Allow Zapier to access the account. You need an account on Mobilia, plus read or write access on anything you do not own yourself and want the Zap to touch. Every Mobilia step then reuses this connection.

First Zap

Your first Zap: form entry to Mobilia lead

GoalTurn the form entries you care about into leads in Mobilia, with the source already filled in.

  1. 01

    Create the Zap and set the trigger

    Create a Zap and pick your form tool as the trigger app, with its new-entry event. Mobilia has no trigger, so the start always comes from another app like this one.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries from the connected account, so you map fields from a real entry rather than an empty template.

  3. 03

    Add the filter

    Add a Filter step from the plus icon, then fill its three boxes: the field to look at, the rule and the value. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Lead

    Choose Mobilia, then Create Lead. Map Name from the form and set the other required fields: Operation Type, Status and Lead Type, where Web matches an entry from your site.

  5. 05

    Test, then publish

    Test the Mobilia step and read what came back before going further. When it looks right, click Publish to switch the Zap on.

Actions

The 4 Mobilia actions

Mobilia gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Client

Action

In Zapier“Creates a client in CRM”

Adds a person to your Mobilia client base from whatever app holds their details, with only the full name required.

When to use it
a contact form or a spreadsheet row should become a client record without anyone retyping it.
Watch out
Owner marks the person as an owner and Buyer/Renter as a buyer or renter; decide both at mapping rather than leaving them to chance, then read the result at test.
2

Create Lead

Action

In Zapier“Creates a Lead in the CRM”

Files a new lead in the CRM, tagged with the way it reached you: a call, an email, a property visit, the web or another source.

When to use it
enquiries land in another tool and you want each one tracked in Mobilia.
Watch out
four fields are required here (Name, Operation Type, Status and Lead Type), so map all four before you run the test.
3

Create Task

Action

In Zapier“Create a Task in CRM”

Puts a task on the books in Mobilia for one agent, with a subject, a status, a type and a start date.

When to use it
something logged in another app means a teammate has to follow up.
Watch out
IdAgent, the agent who creates the task, is required, and a Synchronize option links the task to external calendars.
4

Create Visit

Action

In Zapier“Create a Visit in CRM”

Books a property visit in Mobilia for a given agent, with its operation type and the date and time it starts.

When to use it
a viewing gets arranged elsewhere and should show up in the CRM too.
Watch out
the start date expects YYYY-MM-DD HH:MM:SS, Send Email to Owner is required and set to False by default, and Google Calendar sync only works once it is set up in Mobilia.
Searches

The 3 Mobilia searches

3 search steps look for data that already exists in Mobilia, so a later step can use it.

A search step looks up an agent or a client already in Mobilia and hands that record to the steps that follow. In the editor, searches sit at the bottom of the action list, under the SEARCH heading. Three settings decide what happens when the result is not a single clean match.

1

Search Agent by Email

Search

In Zapier“Search an Agent in CRM by Email”

Finds a member of your Mobilia team from an email address, so a later step can work with that agent's record.

When to use it
the event that starts your Zap names an agent by email address, not by anything Mobilia uses internally.
Watch out
before you map anything from it into IdAgent on Create Task or Create Visit, check at test what the search actually returns.
2

Search Client by Email

Search

In Zapier“Search a Client in CRM by Email”

Looks for an existing client in the CRM using the email address you give it.

When to use it
a message or a form reply comes in and you want the matching client record for the next step.
Watch out
Mobilia, not Zapier, decides whether the address must match exactly or only closely, so try a real address at test.
3

Search Client by Phone

Search

In Zapier“Search a Client in CRM by Phone”

Pulls up a Mobilia client from a phone number instead of an email address.

When to use it
your source records callers by number, with no email to go on.
Watch out
Mobilia, not Zapier, decides how closely the number must match, so check at test that the number you send finds the client you expect.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create that asks for the fields needed to create the missing item. Mobilia exposes no find-or-create variant on Zapier.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Mobilia Zap breaks

Zapier attaches no help article to Mobilia, so the cases below are the general limits every Zap runs into.

  • No backlog pickup

    A Zap only reacts to what happens after you switch it on. Entries that existed before never reach Mobilia; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the place its own trigger watches can start itself again and again and burn through tasks. Keep the trigger's source apart from where it writes.

  • Bulk batches held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.

  • One item, one run

    On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help

Need help automating Mobilia with Zapier?

A person reads every message.

FAQ

Mobilia and Zapier: frequent questions

01Is the Mobilia Zapier integration free?
Yes. Mobilia is not reserved for paid plans, so it works on the free plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. A Zap that sends a form entry straight into Create Lead fits. A Zap that runs Search Client by Email first, or adds a filter, becomes multi-step and needs a paid plan. Since Mobilia has no trigger, one of your two free steps always belongs to another app.
02How many tasks does a Mobilia Zap use?
One per Mobilia action that succeeds. The trigger in your other app costs nothing, and neither does Zapier checking for new data, however often it looks. A Zap that runs Create Client and then Create Lead uses two tasks per run when both work; if Create Lead fails, only one is counted. A few apps and actions take more than one task when they complete, so keep an eye on your count after the first runs.
03Does Mobilia work in real time with Zapier?
It depends on the other app, because Mobilia has no trigger of its own. If that app's trigger is instant, it reports the event to Zapier itself and the Mobilia step runs straight away, whatever your plan; the editor shows a lightning bolt on those Zaps. If it is a polling trigger, Zapier checks it at an interval set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Paid plans can also run a check by hand.
04What does connecting Mobilia to Zapier require?
An account on Mobilia, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once from the Apps page with + Add connection: you sign in to Mobilia in the tab that opens and grant Zapier access. Every Mobilia step then reuses it. If your Zaps will create tasks or visits, the agents they point to must exist in that account, since IdAgent is required on both actions.
05Why does Create Task ask for an agent ID?
Because IdAgent is a required field on Create Task, and on Create Visit as well: the task has to belong to an agent who exists in your Mobilia account. Your source app may only know that agent by email address. Search Agent by Email can find the agent from it, but check at test what the search returns before you map anything into IdAgent. If the address belongs to nobody in Mobilia, the search finds nothing and, on its default setting, the Zap stops there. The extra search step makes the Zap multi-step, so it needs a paid plan.
06What if the Mobilia operation you need is not available?
Open the Mobilia page on Zapier, which shows the current set of operations. Today that is four actions (Create Client, Create Lead, Create Task, Create Visit) and three searches, with no trigger and no way to update or delete a record. When the event you want to react to happens inside Mobilia, Zapier cannot start from it. Start from the app where the information first appears, such as your form or your inbox, and let Mobilia receive the result.
07Zapier, Make or n8n for Mobilia?
Decide by criterion, not by brand. On Zapier, Mobilia gives you seven operations, all of them writing or looking up data in the CRM, billed per successful action, and usable on the free plan as long as a Zap stays at two steps. If your process needs a search or a filter in every Zap, count a paid plan in. For Make or n8n, the first check is whether either one offers a Mobilia connector with the operations you need; this page covers Zapier only.
Same platform

Other docs you might need on this stack.

Browse all integrations