Resources · Zapier integration

mloflo Zapier integrationAutomate mloflo with Zapier.

The mloflo Zapier integration gives you 6 triggers, 11 actions and 0 searches. New leads, loans, contacts and tasks in mloflo can start a Zap (an automation built on Zapier), and other apps can add leads, partners, events and tasks to mloflo. It runs on the free plan.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the mloflo Zapier integration does for you

The mloflo Zapier integration links your mloflo account to Zapier, so events in mloflo can start work in other apps and other apps can write into mloflo. mloflo is a cloud CRM built for real estate businesses: leads, email marketing, the sales pipeline and reporting. On Zapier it exposes seventeen operations, all usable on the free plan.

Three results stand out. A loan board everyone can read: New Loan sends each new loan to a spreadsheet or a team chat, so people outside mloflo see the pipeline move. Calendars that feed the CRM: Add Event From Gmail in Mloflo and Add Event From Outlook in Mloflo copy meetings into mloflo, so the CRM shows what was booked even if nobody types it in. Loan files kept current from elsewhere: Update Loan in Mloflo changes an existing loan file as long as the earlier step carries its loan number.

Around those, there are triggers for borrower contacts, partner contacts, new leads and new tasks, plus actions that add contacts, leads, partners and tasks.

What Zapier does not do here: there is no search, so a Zap cannot look up a loan, a lead or a contact in mloflo before acting, and it cannot fetch a loan number on its own. There is no delete action either: a Zap can add and update, never remove.

If you are weighing platforms, see our n8n vs Zapier guide and our Make vs Zapier guide, and check that the tool you pick offers an mloflo connection.

Vocabulary

Zapier in one minute

Seven words come back on every Zapier page. Here they are once, in plain terms.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new loan in mloflo. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something for you, such as adding a partner.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Instant vs polling
An instant trigger is reported by the app the moment it happens. A polling one is checked by Zapier on a timer instead.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and then it needs a paid plan.
Cost

What mloflo Zaps really cost

mloflo is not one of the apps Zapier keeps for paid plans, so it works on the free plan.

  • TriggersNever counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Paid plan onlySecond action, filter

Triggers never cost a task. Each of the eleven actions counts as one task when it goes through, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. A second action or a filter makes it a multi-step Zap, which needs a paid plan. The grid below is how often Zapier checks polling triggers on each plan; it does not apply to mloflo, whose six triggers are all instant.

Connect

Connect mloflo to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your mloflo account linked once, then reused by every Zap step that works with mloflo.

  2. 02

    Find mloflo

    Type mloflo in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens so you can sign in to your mloflo account.

  3. 03

    Sign in and grant access

    Log in to mloflo in that tab and grant Zapier access. You need an account on mloflo, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first mloflo Zap: a loan board with a team ping

GoalEach new loan in mloflo is added as a row to a shared spreadsheet, then a message in your team chat says it is there.

  1. 01

    Create the Zap

    Start a new Zap, choose mloflo as the app and New Loan as the event, then pick your mloflo connection. The trigger is instant, so a lightning bolt shows in the editor.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent items of the connected account. Pick a real loan and read what mloflo sends before mapping anything.

  3. 03

    Add the spreadsheet row

    Add the action that writes a row and map the loan details from the test into the columns. What each loan carries is something to read at the test, not to guess.

  4. 04

    Add the chat message

    Add the message action after it. Two actions make this a multi-step Zap, so it needs a paid plan, and each new loan uses two tasks when both steps work.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When the row and the message look right, click Publish to switch the Zap on.

Triggers

mloflo triggers

6 events start a Zap when something happens in mloflo, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Add Borrower Contacts

Instant trigger

In Zapier“Triggers when a new borrower contact is added.”

Every borrower contact added in mloflo is passed to the Zap by this trigger, so the person can also appear in your mailing tool or a shared sheet without a second entry.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
borrowers should join an email list or a follow-up sheet as soon as they exist in the CRM.
Watch out
borrower contacts created before you published the Zap are never sent, so the existing list has to be moved separately.
2

Add Partner Contacts

Instant trigger

In Zapier“Triggers when a new partner contact is added.”

This one watches the other side of your network: each new partner contact in mloflo starts the Zap, which keeps partners apart from borrowers in whatever tool comes next.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
partners get their own list or their own channel, and you want each new one added there without copying it by hand.
Watch out
what a partner contact carries is best read at the test step before you map it.
3

New Loan

Instant trigger

In Zapier“Triggers when a new loan is added in mloflo.”

When a loan is added in mloflo, this trigger hands it to the Zap. It is the natural start for anything that tracks the pipeline outside the CRM, from a shared board to a team alert.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
people who never open mloflo need to see each new loan, in a spreadsheet or in the team chat.
Watch out
loans that existed before the Zap was published are not picked up, and moving that backlog is a separate job.
4

Add Task

Instant trigger

In Zapier“Triggers when a task is added in mloflo”

Each task added in mloflo reaches the Zap through this trigger, so the to-do can show up where your team actually plans its day, in a calendar or a task tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team works from another task list and mloflo tasks should land there too.
Watch out
mloflo also has an Add Task action; as a general precaution, a Zap that writes into the very place its trigger watches can set itself off again.
5

New Lead

Instant trigger

In Zapier“Triggers when a new lead is added in mloflo.”

Fires on each lead added in mloflo and passes it on, which is how a fresh lead can reach a spreadsheet, an inbox or a chat without anyone exporting it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
whoever handles first contact should hear about every new lead without keeping mloflo open all day.
Watch out
leads from before the Zap was published are not sent, so plan the switch-on moment with that in mind.
6

Update Loan for Arive

Instant trigger

In Zapier“Triggers when a loan is updated in mloflo.”

Starts the Zap when a loan is updated in mloflo, so a change on the file can travel to the tools that keep their own copy of it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
another tool or a shared sheet tracks loan progress and has to reflect each update made in mloflo.
Watch out
the name points to Arive, but mloflo describes it as firing on a loan update in mloflo; check at the test step what an update sends.
Actions

mloflo actions

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

1

Add Contacts

Action

In Zapier“Handles adding of contacts from services to our app.”

Adds contacts to mloflo from another service, so people captured elsewhere end up in the CRM without retyping.

When to use it
contacts collect in another app first and belong in mloflo.
Watch out
the editor shows which fields it expects, so read them there and run the test before publishing.
2

Add Event From Gmail in Mloflo

Action

In Zapier“Add Event in mloflo when a new event from Gmail is added”

Copies a calendar event into mloflo, built for events that start in Gmail, so those meetings are visible in mloflo too.

When to use it
appointments start as Gmail events and should be visible in the CRM.
Watch out
Event Title, Start Date Time and End Date Time are required, and both dates expect the format 2024-02-13T13:30:00+05:30.
3

Add Event From Outlook in Mloflo

Action

In Zapier“Add Event in mloflo when a new event in outlook is added”

The Outlook counterpart: it adds an event to mloflo when the meeting was created in Outlook.

When to use it
your team schedules in Outlook and the CRM should still show every appointment.
Watch out
Event Title, Start Date Time and End Date Time are required; check at the test that the dates arrive in a form mloflo accepts.
4

Add Lead V2

Action

In Zapier“Adds a Lead to Mloflo”

Puts a lead into mloflo from data another app already holds, one of two lead actions on this app.

When to use it
leads arrive from a form or another tool and should start their life in mloflo.
Watch out
V1 and V2 share the same description, so compare their fields in the editor and test before choosing one.
5

Add Lead V1

Action

In Zapier“Adds a Lead to Mloflo”

The other lead action, which creates the lead and ties it to a lead or loan identifier you supply.

When to use it
the source system already gives each lead or loan a unique id you want carried into mloflo.
Watch out
Borrower Email, Lead/Loan Id and Borrower First Name are all required.
6

Add Partner Lead Contact

Action

In Zapier“Adds a partner lead into the pipeline in Mloflo”

Drops a partner lead into the mloflo pipeline, so a partner collected in another tool is tracked in the pipeline like any other lead.

When to use it
partner contacts are collected in a form or a sheet before reaching the CRM.
Watch out
First Name and Email are required.
7

Add Partner

Action

In Zapier“Adds a Partner to Mloflo”

Creates a partner record in mloflo, with its affiliations and where it came from.

When to use it
you sign up partners outside mloflo and want each one recorded with its source.
Watch out
First Name, Partner Affiliations and Source are all required, so the earlier step has to carry the three values.
8

Add Task

Action

In Zapier“Handle task addition to mloflo on task creation”

Creates a task in mloflo when a task is created in a connected app, so follow-ups planned elsewhere also live in the CRM.

When to use it
to-dos start in another tool and you want them visible in mloflo too.
Watch out
it offers a Reminder Status field; read at the test what mloflo does with your value.
9

Task List

Action

In Zapier“Handles adding of list from the services to our app.”

Adds a list from another service to mloflo; the name points to tasks, and the editor shows what it expects.

When to use it
a list kept in another tool should reach mloflo without being retyped.
Watch out
mloflo's own description is short, so run the test and check what it created before you publish.
10

Update Loan in Mloflo

Action

In Zapier“Updates a loan file in mloflo”

Changes an existing loan file in mloflo, so progress recorded in another tool lands on the right file.

When to use it
loan updates are made outside mloflo and the CRM must stay current.
Watch out
Loan Number, which identifies the file, and Borrower First Name are required; with no search here, the number has to come from an earlier step.
11

Update Task

Action

In Zapier“This action handles the updation of task in our app with respect to the connected app”

Updates an existing task in mloflo from a change made in the connected app, so the copy in mloflo follows that change.

When to use it
a task changes in another tool and mloflo should follow.
Watch out
check at the test which task it touched before publishing, since nothing on this app lets a Zap search for one first.
When it breaks

When an mloflo Zap breaks

Zapier links no help article to mloflo, so the limits below are the ones every Zap shares, plus the required fields that stop actions.

Rule them out one by one before you suspect mloflo itself. When something looks off, see our Zapier troubleshooting guide.

  • The past is not replayed

    A Zap only reacts to what happens after it is switched on. Loans, leads and contacts already in mloflo are not picked up; moving them is a separate job.

  • A sudden batch can be held back

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

  • Loops eat tasks

    As a general precaution, a Zap that writes into the very place its own trigger watches can set itself off again and again and burn through tasks fast.

  • A required field is empty

    Several actions refuse to run without their required fields, such as the Loan Number of Update Loan in Mloflo. Check the earlier step's test result first.
Need help

Need help automating mloflo with Zapier?

A person reads every message.

FAQ

mloflo Zapier integration: common questions

01Is the mloflo Zapier integration free?
Yes. mloflo is not one of the apps Zapier keeps 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. Sending every new loan to a spreadsheet fits. Sending it to a spreadsheet and then pinging the team chat does not, because two actions make a multi-step Zap, and that needs a paid plan. The same goes for a Zap with a filter.
02How many tasks does an mloflo Zap use?
One per action that goes through, and nothing for the trigger. A new loan written to a spreadsheet costs one task; add a chat message and it costs two. A calendar event copied into mloflo with Add Event From Gmail in Mloflo is one task too. An action that fails, for example because a required field is empty, is not counted against your plan. Keep in mind that a few apps and a few actions take more than one task when they complete, so check your count after the first runs.
03Do mloflo triggers work in real time?
Yes. All six mloflo triggers are instant: the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan. The polling interval of the plans, 15 minutes on the free one, does not apply to any of them. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is an easy way to confirm it. The type is set by the app and cannot be changed from the editor.
04What does it take to connect mloflo to Zapier?
An account on mloflo, plus read or write access on anything you do not own yourself and want the Zap to touch. The steps are short: open Apps in Zapier, click + Add connection, search for mloflo and pick it, click Add connection, sign in to mloflo in the tab that opens, then grant Zapier access. Every Zap step that uses mloflo then reuses that connection, so you only go through this once, whichever of the seventeen operations you use.
05Why does Update Loan in Mloflo fail?
Look at its two required fields first. Update Loan in Mloflo needs a Loan Number, which identifies the loan file, and a Borrower First Name. mloflo has no search on Zapier, so a Zap cannot look the number up halfway through: it has to come from an earlier step, already filled in. Open that step's test result and check the number is really there before you blame mloflo. A failed action does not cost a task, but the loan file stays as it was.
06What if the mloflo operation you need is not there?
Then Zapier cannot do it with mloflo today. mloflo's page on Zapier shows the current list: six triggers and eleven actions, with no search and no delete. So a Zap cannot find an existing loan or contact, and it cannot remove anything from mloflo. If your process depends on one of those, check whether another automation tool offers an mloflo connection with that operation before you build around the gap.
07Zapier, Make or n8n for mloflo?
Decide on criteria, not on a ranking. Coverage: Zapier offers six triggers and eleven actions for mloflo, ready to use; check whether Make or n8n has an mloflo connection at all, and which operations it includes. Speed: on Zapier every mloflo trigger is instant, so the plans' polling interval does not apply. Steps: a two-step Zap fits Zapier's free plan, while a filter or a second action needs a paid plan. Weigh those three points against how your loan process actually runs.
Same platform

Other docs you might need on this stack.

Browse all integrations