Resources · Zapier integration

MOCO Zapier integrationAutomate MOCO with Zapier.

The MOCO Zapier integration gives you 39 triggers, 12 actions and 13 searches. Every trigger is instant, so a new project, invoice or lead reaches your other tools straight away, and the actions create records in MOCO from anywhere else. It runs on the free plan.

See the 64 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MOCO Zapier integration actually does

MOCO is a cloud tool for agencies and service businesses that covers time tracking, billing, resource planning, the sales funnel and the CRM. The integration links it to Zapier, so events in MOCO set off work in your other apps, and records from elsewhere land in MOCO without retyping. 64 operations in all, and MOCO itself works on the free plan.

Projects that start set up. New Project fires the moment a project appears in MOCO. Follow it with Create Task and the tasks your team logs time against are there from day one, no copying from a template.

Invoices that reach the right people. New Invoice, New Invoice Status, New Incoming Payment and New Exported Invoice (Bookkeeping) cover the life of an invoice. Send each step to your accounting tool, a sheet or a chat channel, and nobody has to ask whether a client paid.

Leads that enter MOCO on their own. Create Lead and Create Contact turn a form entry or a CRM record from another tool into a lead and a contact in MOCO, with Find Contact in front to avoid adding the same person twice.

What Zapier does not do here. Eleven of the twelve actions create something, the last one records a presence: nothing updates or deletes an existing MOCO record. None of the 13 searches has a find-or-create variant, so a missing company is not created on the fly. On the bright side, all 39 triggers are instant, so the plan interval never delays them. If you also use Make, see our MOCO Make integration page.

Vocabulary

Zapier words in one minute

Eight words come back on every Zapier screen. Here they are in plain English, once.

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, like a new invoice in MOCO. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like a new task.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's quota is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something that already exists in an app, so the steps that follow 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 it really costs

MOCO is not a premium app, so it works on the free plan. What you pay for is tasks.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • TriggersAll 39 instant, no task
  • Search or filterMakes the Zap multi-step

The trigger never costs a task, so a new invoice that starts the Zap is free. Each action that succeeds counts as one task, and an action that fails is not counted. The free plan gives you 100 tasks a month and Zaps of two steps only. With MOCO that limit bites early: a search such as Find Company in front of Create Project, a filter, or a second action all make the Zap multi-step, which needs a paid plan. The interval grid below applies to polling triggers only; it does not apply to MOCO, whose 39 triggers are all instant.

Connect

Connect MOCO to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a MOCO account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick MOCO

    Type MOCO in the search box of the dialog, select it, then click Add connection. A new tab opens, and that is where the rest of the connection happens.

  3. 03

    Sign in and grant access

    Sign in to MOCO in that tab and grant Zapier access to the account. The connection is then reused by every MOCO step in every Zap, so you only link the account once.

First Zap

Your first Zap: a starter task and a kickoff comment on every new project

GoalA project is created in MOCO: the Zap adds the first task to it and posts a comment, so the team knows where to start.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose MOCO and the New Project event, then your connection. Test it: Zapier brings back the three most recent projects of the account, so you map from a real one.

  2. 02

    Add Create Task

    Add a MOCO step with Create Task. Type the Task Name, then map the project number from the trigger into Project Identifier. Check at test time which value the trigger offers for it.

  3. 03

    Add Create Comment

    Add Create Comment, choose the Target and write the Message. With two actions the Zap is multi-step, so it needs a paid plan, and each run uses two tasks.

  4. 04

    Test each step

    Run each step once and read what came back. The test creates a real task and a real comment in MOCO, so use a project you can tidy up afterwards.

  5. 05

    Publish

    Click Publish to switch the Zap on. Each new project reaches it straight away; projects created before that moment are not picked up.

Triggers

MOCO triggers

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

1

Approved Holiday Request

Instant trigger

In Zapier“Triggers when a holiday request is approved.”

Fires when a holiday request is approved in MOCO, so the approved leave can show up in the tools your team plans with.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an approved leave should land in a shared calendar or a team channel without anyone copying it by hand.
Watch out
requests that are only submitted go through New Holiday Request instead; pick this one if only approved leave matters.
2

New Time Entry

Instant trigger

In Zapier“Triggers when a new time entry is created.”

Starts a Zap each time a new time entry is created in MOCO, so the hours logged can feed a sheet, a report or an alert outside MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a running log of hours in a spreadsheet and want each new entry added to it without copying.
Watch out
each Zap run that completes an action costs a task, so compare the number of entries your team logs with your plan first.
3

New Comment

Instant trigger

In Zapier“Triggers when a new comment is created.”

Reacts to every new comment created in MOCO, letting a remark left on a record travel to the place where your team actually reads messages.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
comments get missed inside MOCO and you would rather see them in a chat channel.
Watch out
as a general precaution, a Zap that writes comments back into MOCO while this trigger listens can start itself again; add a filter if you build one.
4

New Company

Instant trigger

In Zapier“Triggers when a new company is created.”

Kicks off a Zap as soon as a company is added in MOCO. Zapier highlights it among the popular MOCO triggers, and it is the natural start for keeping other client lists in step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new client in MOCO should also exist in your mailing tool or your accounting software.
Watch out
edits to an existing company do not count here; Updated Company covers those.
5

New Contact Person

Instant trigger

In Zapier“Triggers when a new contact person is created.”

Runs when a contact person is created in MOCO, so the people behind your clients can be copied to the other tools that need their details.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new contact in MOCO should be added to a newsletter list or to a sales tool used by another team.
Watch out
test it with a real contact and check which values come back before you map them, since the next app may expect fields MOCO did not fill.
6

New Client

Instant trigger

In Zapier“Triggers when a new client is created.”

Watches for new clients in MOCO, so the work that follows a new client can start in your other apps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new client should get a welcome message or a shared folder, prepared without anyone remembering to do it.
Watch out
New Company and New Client are two separate triggers; run a test on each to see which one matches the moment you care about in your account.
7

New Lead

Instant trigger

In Zapier“Triggers when a new lead was created.”

A new lead created in MOCO's sales funnel starts this Zap, the starting point for any follow-up handled outside MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a ping in a chat channel, or a row in a pipeline sheet, each time a lead appears.
Watch out
as a general precaution, a Zap that writes leads where its own trigger watches can start itself again; check where each Zap writes before you switch several on.
8

New Expense

Instant trigger

In Zapier“Triggers when an expense is created.”

Picks up each new expense created in MOCO, so costs logged by the team can be mirrored in your finance tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new expense should be listed in a shared spreadsheet without exporting from MOCO.
Watch out
MOCO also has a separate New Recurred Expense trigger; test both to see which expenses each one brings back.
9

New Holiday Request

Instant trigger

In Zapier“Triggers when a new holiday request is created.”

Triggers on every new holiday request in MOCO, before it is approved, which helps when someone has to review 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
you want a message each time a request waits for a decision, instead of checking MOCO.
Watch out
a request seen here is not approved yet; to publish only confirmed leave, use Approved Holiday Request.
10

New Invoice

Instant trigger

In Zapier“Triggers when a new invoice is created.”

An invoice created in MOCO sets this Zap off. Zapier puts it forward among the main MOCO triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each new invoice should be logged in a finance sheet or announced in a team channel.
Watch out
creation is not payment; to react when money arrives, use New Incoming Payment, and New Invoice Status for status changes.
11

New Exported Invoice (Bookkeeping)

Instant trigger

In Zapier“Triggers when a new invoice is exported (for the bookkeeping).”

Fires when an invoice is exported for bookkeeping in MOCO, a different moment from the day it was created.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each exported invoice should reach the tool where your bookkeeping is done, rather than travel by email.
Watch out
only exported invoices start this Zap; an invoice that is created but never exported will not show up here.
12

New Incoming Payment

Instant trigger

In Zapier“Triggers when a new incoming payment is created.”

Reacts when a new incoming payment is recorded in MOCO, so the news can travel on to whoever is waiting for 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
your team should hear about each incoming payment in a chat channel, without opening MOCO.
Watch out
as a general precaution, a Zap that records payments in MOCO while this trigger listens can start itself again; check how your Zaps feed each other.
13

New Invoice Status

Instant trigger

In Zapier“Triggers when the status of an invoice is changed.”

Follows invoice status changes in MOCO and starts a Zap whenever one moves, which lets you react to each stage rather than only to creation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a different follow-up depending on the new status, with a filter in front of each action.
Watch out
every change starts the Zap, so a filter on the status keeps your task count in check; filters need a paid plan.
14

New Offer

Instant trigger

In Zapier“Triggers when a new offer is created.”

Fires each time a new offer is created in MOCO, so it can be tracked or shared beyond MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new offer should be listed in a tracking sheet or posted in a team channel.
Watch out
changes to an offer go through Updated Offer, so a Zap built here sees each offer once, at creation.
15

New Planning Entry

Instant trigger

In Zapier“Triggers when a new Planning Entry is created.”

Each new planning entry created in MOCO starts this Zap, so your other tools can follow MOCO's resource planning.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new planning entries should show up in a calendar tool without anyone checking MOCO.
Watch out
later changes to the same entry come through Updated Planning Entry, so a calendar Zap needs both to stay accurate.
16

New Presence

Instant trigger

In Zapier“Triggers when a new Presence is created.”

Each new presence created in MOCO starts this Zap, so the record can be shared outside MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a spreadsheet of presences and want each new one added to it without retyping.
Watch out
as a general precaution, a Zap that writes presences into the account this trigger watches can start itself again; check where each Zap writes.
17

New Project

Instant trigger

In Zapier“Triggers when a new project is created.”

Creating a project in MOCO launches this Zap. It is one of the triggers Zapier highlights for this app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new project should get a starter task, a shared folder or a channel in your chat tool.
Watch out
projects that already existed before you publish are not picked up; only new ones start the Zap.
18

New Project Assignment

Instant trigger

In Zapier“Triggers when a person is assigned to a project.”

Triggers when a person is assigned to a project in MOCO, a good moment to pass on what they need for 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
a person newly assigned to a project should get a welcome message with the essentials, sent for you.
Watch out
test it with a real assignment to see who and which project come back before mapping a message around them.
19

New Project Budget Alert

Instant trigger

In Zapier“Triggers when a project budget alert event has happened.”

When a project budget alert event happens in MOCO, this Zap turns a warning that could sit unnoticed in the app into a message someone actually reads.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want to hear about project budget alerts in a chat channel or by email.
Watch out
test it with a real alert and check what comes back before you build a message around it.
20

New Purchase

Instant trigger

In Zapier“Triggers when a new purchase is created.”

Each new purchase created in MOCO sets this Zap going, so it is visible outside MOCO as soon as it is entered.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new purchase should be posted for review or logged in a finance sheet.
Watch out
edits to a purchase come through Updated Purchase and payments through New Outgoing Payment, so pick the moment that matters.
21

New Outgoing Payment

Instant trigger

In Zapier“Triggers when a new outgoing payment is created.”

A new outgoing payment created in MOCO is the event here, so the records you keep elsewhere can reflect 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
a cash-flow sheet outside MOCO should get a line for each outgoing payment.
Watch out
as a general precaution, a Zap that records outgoing payments in MOCO while this trigger listens can start itself again; check how your Zaps feed each other.
22

New Recurred Expense

Instant trigger

In Zapier“Triggers when an expense is recurred.”

An expense that recurs in MOCO starts this Zap, so each recurrence can be tracked outside MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a cost that repeats on a project should appear in your cost tracking each time, without a manual entry.
Watch out
MOCO has a separate New Expense trigger; test both to see which expenses each one brings back.
23

New Sales Activity

Instant trigger

In Zapier“Triggers when a new sales activity has happened.”

Runs whenever a new sales activity happens in MOCO, so the sales work is visible to people who do not open MOCO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a feed of sales activity in a chat channel to follow the pipeline at a glance.
Watch out
every activity is a run, and each completed action costs a task, so mind your monthly quota.
24

New Task

Instant trigger

In Zapier“Triggers when a new task is created.”

Every new task created in MOCO launches this Zap, so the tasks of a project can be copied to where your team works.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new project tasks should be copied to the to-do tool your team uses day to day.
Watch out
as a general precaution, a Zap that creates tasks where its own trigger watches can restart itself, so check before chaining Zaps.
25

New User

Instant trigger

In Zapier“Triggers when a new User is created.”

User accounts created in MOCO set this Zap off, a sign that someone has joined the team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new MOCO user should also get accounts or a welcome message in your other tools, prepared without anyone remembering to do it.
Watch out
changes to an existing user come through Updated User; this trigger sees each user only once, when the account is created.
26

Archived Project

Instant trigger

In Zapier“Triggers when a project is archived.”

Archiving a project in MOCO triggers this Zap, the point where the surrounding tools can be tidied up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
archiving a project should close its chat channel, flag its folder or post a wrap-up message for you.
Watch out
a project brought back later goes through Unarchived Project, so a cleanup Zap may need a counterpart.
27

Unarchived Project

Instant trigger

In Zapier“Triggers when a project is made active again.”

Bringing an archived project back to active in MOCO starts this Zap, the signal that work has restarted on 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
a reopened project should warn its former team, or restore what your cleanup Zap closed when it was archived.
Watch out
this trigger only sees projects coming back from the archive; brand new projects go through New Project.
28

Updated Time Entry

Instant trigger

In Zapier“Triggers when a time entry was updated.”

Corrections to a logged time entry in MOCO, a new duration or a fixed description, set this Zap off so any report built from them stays right.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a time log kept outside MOCO must stay right when someone fixes a duration or a description.
Watch out
to update rather than duplicate, the other app must let the Zap find the earlier line; check that before you rely on it.
29

Updated Company

Instant trigger

In Zapier“Triggers when a company was updated.”

Fires whenever a company record is edited in MOCO, keeping copies of that company in other tools from going stale.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
changes made to a company in MOCO should reach your accounting or mailing tool.
Watch out
every edit starts the Zap, even a small one, so a filter on the field that matters keeps tasks down; it needs a paid plan.
30

Updated Contact Person

Instant trigger

In Zapier“Triggers when a contact person was updated.”

Edits to a contact person in MOCO start this Zap, so the copies of that contact stored elsewhere can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
MOCO is your reference for client contacts and other tools should mirror it.
Watch out
the receiving app needs a way for the Zap to find the existing contact, otherwise you risk creating a second copy instead of updating.
31

Updated Lead

Instant trigger

In Zapier“Triggers when a lead was updated.”

Leads move through MOCO's sales funnel, and each update to one starts this Zap, so you follow a lead after its creation too.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a pipeline sheet outside MOCO should reflect each change to a lead.
Watch out
every edit starts a run, so put a filter in front of the action to react only to the change you care about.
32

Updated Expense

Instant trigger

In Zapier“Triggers when an expense was updated.”

Reacts to edits on an existing expense in MOCO, so a corrected amount or title does not leave your finance sheet out of date.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you mirror expenses outside MOCO and need the copy to follow each correction.
Watch out
pair it with a way to find the earlier line in the other tool; Find Expense helps on the MOCO side, but needs a Project.
33

Updated Invoice

Instant trigger

In Zapier“Triggers when an invoice was updated.”

Each update to an invoice in MOCO launches this Zap, so a copy kept elsewhere can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a billing tracker outside MOCO must keep the latest version of each invoice.
Watch out
run a test after a real edit to check what comes back before you decide between this trigger and New Invoice Status.
34

Updated Offer

Instant trigger

In Zapier“Triggers when an offer was updated.”

Updating an offer in MOCO sets this Zap going, so a copy kept elsewhere stays in sync.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you track offers in a shared sheet and need every change there.
Watch out
each update counts as a new run, so an offer edited several times sets the Zap off several times; budget tasks accordingly.
35

Updated Planning Entry

Instant trigger

In Zapier“Triggers when a Planning Entry was updated.”

Planning entries updated in MOCO are the event here, so the change reaches the tools that rely on that planning.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a calendar fed by New Planning Entry should follow later changes too.
Watch out
to move the right calendar event, the Zap must find the one created earlier; Find Planning Entry works on the MOCO side and asks for a Project and a User.
36

Updated Presence

Instant trigger

In Zapier“Triggers when a Presence was updated.”

Updating a presence in MOCO starts this Zap, so the copies kept elsewhere can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep presences in a spreadsheet and want it corrected whenever MOCO is.
Watch out
test with a real change and check what comes back; the receiving sheet needs a way to find the row to update rather than adding a new one.
37

Updated Project

Instant trigger

In Zapier“Triggers when a project was updated.”

Project edits in MOCO, from a renamed title to a new leader, set this Zap off so the tools built around that project do not drift.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a project list kept in another tool should follow every change made in MOCO.
Watch out
archiving and unarchiving have their own triggers; use those when the status is the only thing you care about.
38

Updated Purchase

Instant trigger

In Zapier“Triggers when a purchase was updated.”

Purchases updated in MOCO launch this Zap, so the copies in your other finance tools stay correct.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
purchases are reviewed in another tool and every change must reach it.
Watch out
a payment is a different event, New Outgoing Payment, so this trigger alone does not tell you a purchase was paid.
39

Updated User

Instant trigger

In Zapier“Triggers when a User was updated.”

Changes to a MOCO user start this Zap, keeping user details aligned across the tools your team uses.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team directory outside MOCO should follow updates to MOCO users.
Watch out
the other app needs a way to find the matching person; Find User covers the MOCO side, but only returns active users.
Actions

MOCO actions

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

1

Create Time Entry

Action

In Zapier“Create a new time entry.”

Logs a time entry in MOCO for a user on a project, with a date, a task, a description and a duration given in seconds.

When to use it
time tracked in another tool should end up in MOCO without retyping.
Watch out
the duration goes in Seconds, not hours, and the description needs at least 3 characters.
2

Create Comment

Action

In Zapier“Creates a new Comment.”

Posts a comment in MOCO on the target you choose, with the message built from earlier steps of the Zap.

When to use it
a note from another tool, such as a client reply, should sit next to the matching record in MOCO.
Watch out
Target and Message are both required; as a general precaution, a Zap started by New Comment that writes comments can restart itself.
3

Create Contact

Action

In Zapier“Creates a new contact person.”

Creates a contact person in MOCO from a first name and a last name, plus whatever else the earlier steps carry. It is one of the actions Zapier puts forward.

When to use it
a new contact in your mailing tool or CRM should also exist in MOCO.
Watch out
put Find Contact in front if duplicates are a risk, and test with a real person first.
4

Create Company

Action

In Zapier“Creates a new company (customer only).”

Adds a company to MOCO as a customer, with a name, a currency and the user responsible for that client. Zapier features it among MOCO's main actions.

When to use it
a deal won in another sales tool should open the client record in MOCO for you.
Watch out
it creates customers only, and the responsible User must already exist in MOCO.
5

Create Expense

Action

In Zapier“Creates a new Expense.”

Adds an expense to a MOCO project with its title, date, quantity, unit, price and cost, and says whether it is billable and counted in the budget.

When to use it
costs entered in a spending tool should reach the right MOCO project.
Watch out
nine fields are required, and Billable only matters on time and material projects.
6

Create Incoming Payment

Action

In Zapier“Creates a new incoming payment.”

Records money received in MOCO with a total, a date and a currency, and can flag it as a partial payment.

When to use it
a payment confirmed in another tool should also be recorded in MOCO.
Watch out
as a general precaution, a Zap started by New Incoming Payment that writes payments can restart itself; check what your other Zaps do.
7

Create Lead

Action

In Zapier“Creates a new lead.”

Adds a lead to MOCO's sales funnel with a name, an estimated amount, a currency and a reminder date. Zapier lists it among the featured MOCO actions.

When to use it
a request from your website form should become a MOCO lead without anyone retyping it.
Watch out
Amount and Reminder Date are required, so the form must provide them or the Zap must set a fixed value.
8

Create Project

Action

In Zapier“Creates a new Project.”

Opens a new project in MOCO for an existing company, with a name, a currency, a billing method and a project leader.

When to use it
a signed quote or a won lead should become a project without someone setting it up by hand.
Watch out
Company, Billing By and Leader are required, so the company and the leader must exist first; Find Company can fetch the first.
9

Create Purchase

Action

In Zapier“Creates a new Purchase.”

Records a purchase in MOCO with its supplier, creator, date, payment method, title, total and tax rate.

When to use it
purchases entered in another tool should be logged in MOCO without retyping.
Watch out
Tax (%) and Tax included in Total? are both required, so decide how the source tool states its amounts before mapping.
10

Create Outgoing Payment

Action

In Zapier“Creates a new outgoing payment.”

Adds a new outgoing payment to MOCO, with only a date, a total and a currency required.

When to use it
a transfer confirmed in your banking tool should also be recorded as an outgoing payment in MOCO.
Watch out
Currency is required, so map it from the banking tool or set a fixed value, then check it on the first test.
11

Create Task

Action

In Zapier“Creates a new project task.”

Adds a task to a MOCO project, identified by its project number, and can mark it as active for time tracking and billable by default.

When to use it
every new project should start with the same standard tasks.
Watch out
Project Identifier expects the MOCO project number; check at test time that you map that value and not the project name.
12

Record Presence

Action

In Zapier“Record a new presence.”

Records a new presence in MOCO for the user you choose, with User as the only required field.

When to use it
an event in another tool, such as a form entry, should be recorded as a presence in MOCO.
Watch out
check at test time that the right person gets the presence, since nothing else is required to tell them apart.
Searches

MOCO searches

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

A search step looks up a record that already exists in MOCO and hands it to the next steps. MOCO's 13 searches sit at the bottom of the action-event list, under the SEARCH heading. Each one makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not a single clean match.

1

Find Time Entry

Search

In Zapier“Finds an existing Time Entry.”

Looks up an existing time entry in MOCO for a given project and user, so a later step can work with it.

When to use it
a Zap needs the hours already logged by someone on a project before it acts.
Watch out
Project and User are both required, so the Zap must already know them.
2

Find Company

Search

In Zapier“Finds an existing Company.”

Fetches an existing company from MOCO so the next steps can attach records to it.

When to use it
before Create Project, to give the new project the right Company.
Watch out
if no company matches, the Zap stops by default; decide with the first setting whether it should carry on.
3

Find Contact

Search

In Zapier“Finds an existing Contact.”

Retrieves a contact person who already exists in MOCO.

When to use it
in front of Create Contact, to avoid adding the same person twice, or to pull a contact's details into a message.
Watch out
whether the search wants the exact value or something close is decided by MOCO; test it with a real name.
4

Find Lead

Search

In Zapier“Finds an existing lead.”

Finds an existing lead in MOCO's sales funnel and passes it on to the next steps of the Zap.

When to use it
a reply in another tool should add a comment to the lead it belongs to.
Watch out
with several matching leads, the default keeps only the first one; check the third setting if that is a risk.
5

Find Expense

Search

In Zapier“Finds an existing Expense.”

Expenses already logged on a MOCO project can be pulled in with this search, so their details feed a later step.

When to use it
a finance sheet needs the MOCO version of an expense that was just edited.
Watch out
Project is required, so this search only works when the Zap already knows which project to look in.
6

Find Invoice

Search

In Zapier“Finds an existing Invoice.”

Retrieves an existing invoice from MOCO, for when a Zap starts somewhere else but needs the invoice behind it.

When to use it
a payment confirmed in another tool should be matched to its MOCO invoice before anything is recorded.
Watch out
test it with a real invoice to see which value it searches on before mapping.
7

Find Offer

Search

In Zapier“Finds an existing Offer.”

Fetches an offer that already exists in MOCO, so later steps can read or reference it.

When to use it
an event in another tool should be traced back to its offer in MOCO.
Watch out
when nothing matches, the Zap stops by default unless you switch on the first setting.
8

Find Planning Entry

Search

In Zapier“Finds an existing Planning Entry.”

Planning entries that already exist in MOCO come back through this search, for a given project and user.

When to use it
a calendar Zap needs the MOCO booking behind an event before it moves anything.
Watch out
Project and User are both required inputs, so map them from earlier steps.
9

Find Project

Search

In Zapier“Finds an existing project.”

Projects that already exist in MOCO come back through this search, often the missing link before a task, an expense or a time entry can be created.

When to use it
in front of Create Time Entry when the other tool only knows the project by name.
Watch out
how close a match MOCO accepts is up to MOCO; test with a real project name.
10

Find Purchase

Search

In Zapier“Finds an existing Purchase.”

Looks up a purchase that already exists in MOCO.

When to use it
a payment made in your banking tool should be matched with its purchase before Create Outgoing Payment runs.
Watch out
with several matches the default keeps the first one, which may not be the purchase you meant.
11

Find Purchase Category

Search

In Zapier“Finds an existing purchase category.”

Purchase categories defined in MOCO are retrieved here, so a purchase created later in the Zap can be filed correctly.

When to use it
purchases from another tool carry a category label that must match a MOCO category.
Watch out
the category must already exist; this search never creates one.
12

Find Task

Search

In Zapier“Finds an active Task for a Project.”

Finds an active task within a MOCO project, by project and task name.

When to use it
before logging time, to point the entry at the right task.
Watch out
it only returns active tasks, and both Project and Task Name are required.
13

Find User

Search

In Zapier“Finds an existing active user.”

Active users of your MOCO account come back through this search, so actions that need a User or a Leader can get one.

When to use it
in front of Create Project, to set the Leader from a value carried by an earlier step; check at test time which value it searches on.
Watch out
inactive users are not returned, so test with an active one.

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 depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns a search into a find-or-create: it then asks for the fields needed to create the missing item. None of the 13 MOCO searches offers it, so a missing record is never created on the fly.
  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 hand all of them on at once.
When it breaks

When the MOCO Zap breaks

Zapier attaches no help article to MOCO, so the risks below are the ones every Zap shares, with MOCO's 39 triggers and 12 actions in mind.

These limits come from Zapier itself and apply to every app, MOCO included. If one of them gets in your way, start with our Zapier troubleshooting guide.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you publish it. Projects, invoices or leads that already existed are not picked up; moving that backlog is a separate job.

  • A Zap that sets itself off

    As a general precaution, a Zap that writes into the very place its own trigger watches can start itself again and again, and burns through your task count fast.

  • Flood protection on big batches

    When a trigger suddenly sends a huge batch, after a bulk import or a migration into MOCO for instance, Zapier's flood protection can hold those items back.
Need help

Need help automating MOCO with Zapier?

A person reads every message.

FAQ

MOCO Zapier integration: questions people ask

01Is the MOCO Zapier integration free?
Yes. MOCO is not a premium app, so it runs on the free Zapier 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 creates a task for every new project fits within that. The catch with MOCO is that many useful Zaps need a search first, such as Find Company before Create Project, and a search makes the Zap multi-step, which needs a paid plan.
02How many tasks does a MOCO Zap use?
One task per action that succeeds, and nothing for the trigger. A new invoice that starts the Zap is free; the message or the row that follows costs one task. A Zap with Create Task and Create Comment uses two tasks per new project. An action that fails is not counted against your plan. With 39 triggers, watch the Updated triggers in particular: each update to a record starts a new run, and every run that completes an action uses tasks.
03Does MOCO work in real time on Zapier?
Yes, on every trigger. All 39 MOCO triggers are instant: the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan. The interval grid that delays polling triggers on the free plan does not apply to any of them. In practice, a budget alert or a new lead reaches your chat channel as soon as MOCO raises it. In the editor, a lightning bolt marks these instant triggers.
04What do you need to connect MOCO to Zapier?
A MOCO account, plus read or write access on anything you do not own yourself and want the Zap to touch. Open the Apps page of your Zapier account, click + Add connection, pick MOCO, then sign in in the tab that opens and grant Zapier access. Before building, check that the account can see the records your actions point to, such as the companies, users and projects that Create Project or Create Time Entry require.
05Why does Create Time Entry log the wrong duration?
Because the field is Seconds, not hours. Create Time Entry asks for the duration of the time entry in seconds, so a value of 2 coming from a tool that counts hours ends up as two seconds in MOCO. Convert the duration in the source tool and check the result on the first test. The same action also requires a User, a Project, a Date, a Task Name and a Description of at least 3 characters.
06What if the MOCO operation you want is not on Zapier?
Then this integration cannot do it. The app page of MOCO on Zapier shows the current list: today 39 triggers, 12 actions and 13 searches. The gap you will notice first is updating: every action creates a record or a presence, none edits or deletes one. If that is what you need, check whether the other app of your Zap can hold the change, or compare tools on that precise point.
07Zapier, Make or n8n for MOCO?
Pick by criteria, not by a winner. Start with coverage: on Zapier you get the 64 operations described here, and a Make integration also exists for MOCO. Then look at volume, since every successful action is a task on Zapier and MOCO offers 39 triggers. Speed is not a reason to switch, because all MOCO triggers are instant on Zapier. Finally, consider who maintains the Zaps: the other tools ask for more technical comfort in exchange for more control.
Same platform

Other docs you might need on this stack.

Browse all integrations