MOCO Make integrationAutomate MOCO with Make.

This action writes a comment in MOCO for you, so a status update or a note from another tool ends up where the project team reads it.

Create a Company adds a customer or supplier to MOCO from data arriving elsewhere, which spares you retyping names and addresses after a deal is signed.

Need a person in MOCO without typing them in? This module creates the contact from the bundle it receives, for example a sign-up or a business card scan.

A lead in MOCO is a sales opportunity, and this action opens one from outside data so your sales pipeline fills itself.

Create an Invoice drafts a billing document in MOCO from data your scenario already holds, which removes a copy step between the sale and the bill.

This module records money received against a MOCO invoice, so the invoice reflects payments captured by your bank feed or payment tool.

Attendance can reach MOCO without anyone opening it: Create a Presence logs a presence entry for a team member from another source.

Create a Project opens a new project in MOCO from a signed quote or a request, so the team can log time on it straight away.

Costs spent for a client can be attached to the right MOCO project through this action, without anyone keying receipts in twice.

This action records a purchase in MOCO, which keeps company spending in the same place as projects and invoices.

Create a Task on a Project adds a to-do to a chosen MOCO project, which turns a request coming from email or a form into planned work.

Onboarding someone? This action creates their MOCO user account from your HR tool or a hiring form, so they can start logging time on day one.

Delete a Comment removes a selected comment from MOCO, which helps when an automated note was posted by mistake or is out of date.

When a payment was recorded in error, this module removes it from the MOCO invoice so the balance is correct again.

This action erases a presence entry from MOCO, for example a duplicate created by a check-in system that fired twice.

Delete a Project Expense removes a cost from a MOCO project, handy for undoing an expense that was pushed there by mistake.

Removing a task that is no longer needed keeps a MOCO project readable, and this action does it from inside a scenario.

With this module a purchase recorded in MOCO can be withdrawn, for instance when an order was cancelled before being paid.

Delete a User takes a staff account out of MOCO, which closes the loop of an offboarding flow started in your HR tool.

Get a Comment fetches one comment by its ID, so a later module can quote its text or route it to the right person.

Pull the full record of one company into your scenario with this module, so the details your other tools need are at hand.

This action reads one MOCO contact, so an email or a CRM update further down uses up-to-date details.

Get a Lead brings back everything MOCO holds on one sales opportunity, which is useful before a decision step in your scenario.

Reading a single invoice from MOCO hands your scenario everything MOCO knows about it, ready to map into the next modules.

One payment, fully read: this module returns the details of a single invoice payment so you can confirm it or report on it.

Get an Invoice PDF gives you the invoice as a file, ready to attach to an email, store in a folder or send to your accountant.

This action reads one attendance entry from MOCO, so a scenario can check its times before copying them elsewhere.

Get a Project returns the full record of one MOCO project, the detail your scenario needs to name a folder or brief a channel.

Looking at one cost in detail? This module fetches a single project expense from MOCO so you can route or report on it.

This action reads one task of a MOCO project, which lets your scenario check its state before notifying someone.

Get a Purchase fetches a single purchase record from MOCO, handy for approval flows that need the full picture before anyone decides.

Categories sort purchases in MOCO, and this module reads one of them, which helps your scenario label or route spending.

This module returns the MOCO profile of one staff member, so later steps can address the right person in a message.

Make an API Call is the open door of this app: it calls any endpoint of the MOCO API with the connection you already set up.

Update a Comment rewrites an existing comment in MOCO, so an automated note can stay accurate as the situation changes.

Keep company records in MOCO in step with your CRM: this action changes an existing company with the new details it receives.

A new phone number or job title can reach MOCO on its own through this module, which edits an existing contact.

This module moves a MOCO sales opportunity forward by editing it, for example after a call logged in another tool.

When a recorded payment was entered with a mistake, Update an Invoice Payment fixes it in MOCO without deleting and recreating it.

Update an Invoice Status changes where a MOCO invoice stands, so its state follows what happened in your mailbox or bank.

Update a Presence fixes an existing presence in MOCO without opening the app: your scenario edits the entry it points to and leaves the others alone.

Update a Project keeps a MOCO project in step with the rest of your stack. You pick the project, change what moved, and the record in MOCO reflects it right away.

Update a Project Expense corrects a project expense after the fact, as long as nobody has billed it yet. Make edits the line in MOCO so the project figures stay accurate.

Update a Project Task changes a task that already sits on a project, so the plan in MOCO matches what the team actually agreed on elsewhere.

Update a Purchase Status moves a purchase to a new status in MOCO. Only the status changes here, which makes it a clean step at the end of an approval flow.

Update a User edits a staff member's record in MOCO so that the people data stays the same across your tools.

List Comments brings back every comment MOCO holds as separate bundles, one item per comment that flows to the next module.

List Companies pulls the list of companies stored in MOCO so the rest of the scenario can loop over them, one bundle per company.

List Contacts returns the contacts in MOCO, each as its own bundle ready for mapping into your mailing tool or CRM.

List Invoice Payments lists the payments recorded against invoices, so you can see what came in without exporting anything from MOCO.

List Invoices gives you the invoices in MOCO as individual bundles, the starting point for any follow-up or reporting flow.

List Leads collects the leads stored in MOCO, one bundle each, so your sales pipeline can be mirrored or checked elsewhere.

List Presences reads the presence entries in MOCO and hands them over as bundles you can sum, filter or copy into another tool.

List Project Expenses shows the expenses booked on projects, each as a bundle you can route into a report or an approval step.

List Projects returns the projects in MOCO so the scenario can act on each one in turn, the usual first step of a bulk update.

List Project Tasks lists the tasks that live on projects, giving each one to the next module as a separate bundle.

List Purchase Categories fetches the purchase categories defined in MOCO, handy when another module needs one of them and you would rather map it than type it.

List Purchases returns the purchases recorded in MOCO as bundles, so approvals, reminders or exports can run on each one.

List Users brings back the staff members set up in MOCO, one bundle per person, ready for mapping into other tools.