Resources · Make integration

Moxie Make integrationAutomate Moxie with Make.

Tired of retyping the same client into Moxie after every signed deal? The Moxie Make integration gives you 20 modules: one instant trigger, 13 actions and 6 searches. This guide shows freelancers and small agencies how to link the account and run a first scenario.

Try the Moxie integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Moxie Make integration do for you?

The Moxie Make integration links your Moxie workspace to Make, a no-code tool where you chain apps together. Moxie can alert Make the moment an event happens, and Make can create clients, projects, invoices, expenses or time entries in Moxie for you, with no code and no API knowledge.

A new lead becomes a real client file. When someone fills in a form on your site, Make can run Create a Client, then Create an Opportunity, so the prospect lands in your sales pipeline instead of your inbox.

Money gets recorded where it belongs. Search Payable Invoices finds the open invoice, and Apply a Payment to an Invoice marks it as paid when a payment tool confirms the transfer. Receipts can follow the same path with Create an Expense.

Work gets logged without copy and paste. A timer in another tool can feed Create a Time Entry, and a message from a client can open a ticket with Create a ticket.

Make only knows what the module list shows. For anything else, the Make an API Call module reaches the Moxie API with the same connection. The Moxie documentation on the Make side is AI-generated and flagged as possibly inaccurate, so test each module with Run once before trusting it. If you are weighing tools, read the n8n vs Make comparison, check Make pricing, or follow the Make training to go further.

Connect

How do you connect your Moxie account to Make?

  1. 01

    Copy your API key in Moxie

    In Moxie, open Workspace settings, then Connected Apps and Integrations. Click Enable Custom Integration. Moxie shows an API key and, just below it, a Base URL. Copy both: Make asks for the pair.

  2. 02

    Add a Moxie module in Make

    In your scenario, add any Moxie module and click Create a connection. A connection is your Moxie account linked to Make once and reused by every Moxie module. The Connection name field is optional; a clear name helps if you run several workspaces.

  3. 03

    Paste the credentials and save

    Paste the API key and the Base URL you copied, then save. Make now reaches your workspace, and the module fields can list what they read from Moxie. You need an active Moxie account for this to work.

First scenario

Build your first scenario: form lead to Moxie project

GoalWhen a prospect submits a form in another app, Make creates the client in Moxie and opens a project for them.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. A scenario is the automation you build: a chain of modules, each one a single brick.

  2. 02

    Pick the form app as the starting point

    Search your form tool by name and choose its trigger for new submissions. Link that account through its own connection. Each submission becomes a bundle, one item passed to the next module.

  3. 03

    Add Create a Client

    Click the + on the right, search Moxie, pick Create a Client and select your Moxie connection. Map the name and email from the form bundle into the client fields.

  4. 04

    Chain Create a Project

    Add Create a Project after it and map the client created one step earlier. The new project now belongs to the right client without you touching Moxie.

  5. 05

    Test with Run once

    Click Run once, then submit a test entry in your form. Open the bubble above each module to read the bundles it received and check the client and project in Moxie.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Turn the scenario on and it keeps running.

Triggers

What starts a Moxie scenario

1 module starts a scenario when something happens in Moxie. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Moxie as soon as it happens.

Moxie1Watch Events

Watch Events

Instant trigger

In Make“Gets instant notifications about new events.”

Watch Events hands you a live feed of what happens in your Moxie workspace, so a scenario can react to new events without you polling anything. Each event reaches Make as one bundle you can route to Slack, a spreadsheet or another Moxie module.

How it fires
instant. Moxie calls Make through a webhook as soon as the event happens, shown by the lightning badge on the module.
When to use it
when you want a notification or a follow-up step the moment something changes in Moxie, rather than waiting for a check.
Watch out
create the webhook before the connection, and avoid sending the result back into a Moxie action that raises the same event, or the scenario feeds itself.
Modules

Every Moxie module, and when to pick it

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

Moxie1

Apply a Payment to an Invoice

Action

In Make“Applies a payment to an open invoice within Moxie.”

Closes the loop on getting paid: this module records a payment against an invoice that is still open in Moxie, so your books match your bank without a manual edit.

When to use it
right after a payment tool confirms a transfer, once you know which invoice it settles.
Watch out
it needs an open invoice; run Search Payable Invoices first to find the right one instead of guessing.
Moxie2

Approve a Deliverable

Action

In Make“Approves a deliverable that is in Client Workflow status.”

Signs off a deliverable for you, moving the work forward without opening Moxie. It only acts on deliverables sitting in the Client Workflow status.

When to use it
when the client gives their green light somewhere else, like an email reply or a form, and you want Moxie to reflect it.
Watch out
a deliverable in any other status is not a valid target, so check where it stands before the scenario reaches this step.
Moxie3

Create a Client

Action

In Make“Creates a new client record in the CRM.”

Gives you a fresh client record in the Moxie CRM, the anchor that projects, invoices and contacts attach to later.

When to use it
when a deal is signed or a form lands from a new company, and you want that company in Moxie before any work starts.
Watch out
nothing in the module description mentions a duplicate check, so play it safe: put Search Clients in front of it and only create when the search comes back empty.
Moxie4

Create a Contact

Action

In Make“Creates a new contact record in the Moxie CRM and optionally associates the contact with a client record.”

Adds a person to the Moxie CRM, and you can tie that person to a client record in the same step. Pick it over Create a Client when the company already exists and you only need a new face.

When to use it
a new stakeholder joins an existing account, such as a finance lead who should receive invoices.
Watch out
search the contacts first so the same email does not end up twice.
Moxie5

Create a Form Submission

Action

In Make“Creates a new form submission in the Moxie CRM which can optionally be attached to a Form Template or create an opportunity in the Sales Pipeline.”

Brings answers collected elsewhere into Moxie as a form submission. You can attach it to a Form Template, or let it open an opportunity in your Sales Pipeline straight away.

When to use it
your intake form lives in another tool, yet you want the answers and the lead inside Moxie.
Watch out
if you also chain Create an Opportunity, you may get the same deal twice; choose one path.
Moxie6

Create an Expense

Action

In Make“Creates an expense in the Moxie accounting records and optionally associates with a client and vendor record.”

Records a cost in the Moxie accounting records, optionally linked to a client and a vendor, so spending shows up next to the work it belongs to.

When to use it
a receipt arrives by email or through an expense app and should not wait for a manual entry.
Watch out
link the client whenever the cost is billable to a client; an unlinked expense is harder to trace back when you invoice.
Moxie7

Create an Invoice

Action

In Make“Creates an invoice record in the Moxie CRM with supplied line items. The invoice can optionally be sent using a pre-configured email template and dynamic contact list.”

Builds an invoice in Moxie from the line items you pass in, and can send it right away using an email template you set up beforehand and a dynamic list of contacts.

When to use it
a milestone is marked done or an order is confirmed, and billing should follow without someone remembering it.
Watch out
run the scenario with Run once without sending first, so you check the lines before a real client receives anything.
Moxie8

Create an Opportunity

Action

In Make“Creates a new opportunity in the sales pipeline.”

Drops a new deal into the Moxie sales pipeline, so a warm lead gets tracked from the first touch instead of living in a notes app.

When to use it
a discovery call is booked or a quote is requested, and you want the prospect visible in your pipeline.
Watch out
Create a Form Submission can already open an opportunity; use this module when the lead does not come from a form.
Moxie9

Create a Project

Action

In Make“Creates a new project in the Moxie CRM.”

Opens a new project in the Moxie CRM, the container for the tasks, time and deliverables of one job.

When to use it
a proposal is accepted and you want the project ready before the kickoff, with the right client already attached.
Watch out
map the client from an earlier module or from Search Clients; a project created without its client is easy to lose among others.
Moxie10

Create a Task

Action

In Make“Creates a task in the project management system.”

Puts a to-do into the Moxie project management system, so work requested elsewhere turns into something assigned and trackable.

When to use it
a client asks for a change in chat or email and you want it on the board instead of in your head.
Watch out
find the project with Search Projects first; a task needs a home that is still active to be useful.
Moxie11

Create a ticket

Action

In Make“Creates a new ticket”

Opens a support ticket in Moxie, which keeps client requests apart from planned project tasks.

When to use it
a client reports a problem through a help form or a shared inbox and the issue deserves its own follow-up.
Watch out
the official description stays vague on what a ticket holds, so run it once and look at the result in Moxie before you rely on it.
Moxie12

Create a Time Entry

Action

In Make“Creates a new time entry record in the workspace.”

Logs time into your Moxie workspace, which is what lets billable hours reach an invoice later without retyping.

When to use it
you track hours in a separate timer or calendar and want each finished session copied to Moxie.
Watch out
every run adds a new entry, so make sure the upstream trigger fires once per session and not on every edit.
Moxie13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Moxie API to your scenario with the connection you already set up, for anything the ready-made modules do not cover.

When to use it
you need a Moxie object or an update that none of the other modules offers.
Watch out
here you write the request yourself, path and body included, so keep the Moxie API reference open and test with Run once.
Moxie14

List Clients

Search

In Make“Lists all clients in the Moxie workspace.”

Returns every client in your Moxie workspace, each one as its own bundle, which is handy for syncing or reporting.

When to use it
you want to copy the full client list into a spreadsheet or another CRM.
Watch out
all following modules run once per client, and each run counts as an operation on your plan; prefer Search Clients when you need a single one.
Moxie15

List Workspace Users

Search

In Make“Lists all users and permissions in the Moxie workspace.”

Shows who belongs to your Moxie workspace and what permissions each person holds, one bundle per user.

When to use it
you want an access review sheet, or you need a team member's details to assign work in a later module.
Watch out
this list covers your own team, not your clients; for those, reach for List Clients or Search Contacts.
Moxie16

Search Clients

Search

In Make“Searches clients by name or contact information.”

Finds clients by name or contact details, so a scenario can reuse an existing record instead of creating a twin.

When to use it
before Create a Client or Create a Project, to check whether the company is already in Moxie.
Watch out
a search can return zero, one or several bundles; add a filter so the next step handles the empty case and the multiple case.
Moxie17

Search Contacts

Search

In Make“Searches contacts in the workspace by first name, last name or email.”

Looks up people in your workspace by first name, last name or email, and brings back the matching contacts.

When to use it
an email arrives and you want to know which client the sender belongs to before logging anything.
Watch out
email is the most reliable key; a first name alone can match several people and send the scenario down the wrong branch.
Moxie18

Search Payable Invoices

Search

In Make“Finds invoices in the CRM that are currently in a payable state.”

Pulls out the invoices that are still waiting for payment, which gives you the list of money you are owed.

When to use it
as the step before Apply a Payment to an Invoice, or to build a reminder that nudges late payers.
Watch out
already paid invoices do not show up here, so a missing result can simply mean the invoice is settled.
Moxie19

Search Projects

Search

In Make“Searches for active projects.”

Finds the active projects in Moxie, the step that tells a scenario where a new task or time entry should go.

When to use it
before Create a Task or Create a Time Entry, when the incoming data only carries a project name.
Watch out
a project that is no longer active will not come back, because the module only searches active ones.
Need help

Need help automating Moxie with Make?

A person reads every message.

FAQ

Moxie and Make: common questions

01Is the Moxie Make integration free?
Yes, on the Make side. Moxie is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. You still need your own active Moxie account, which Moxie bills separately.
02What does Moxie need to connect to Make?
An active Moxie account and an API key. In Moxie, go to Workspace settings, Connected Apps, Integrations, then click Enable Custom Integration. Copy the API key and the Base URL shown right under it. In Make, click Create a connection on any Moxie module and paste both values. For Watch Events, create the webhook first, then the connection. The same connection then serves all 20 modules, so you only do this once. The Connection name is optional.
03Does the Moxie trigger in Make react in real time?
Yes. Watch Events is an instant trigger: Moxie calls Make through a webhook as soon as an event happens, so the scenario starts right away instead of waiting for a scheduled check. That is the only Moxie trigger. If you want to start from another source, such as a form or a spreadsheet, begin the scenario with that app and use the Moxie actions and searches after it. Each event still costs one operation on your plan.
04What if a Moxie module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Moxie API with the connection you already have, so you are not limited to the listed actions and searches. Keep in mind that the Moxie documentation on the Make side is AI-generated and marked as possibly inaccurate, so test every step with Run once and check the Moxie documentation when a result looks off. Keep the connection name clear so you pick the right account.
05Should you automate Moxie with Make or n8n?
It depends on the tool your team already runs. Make offers 20 ready modules for Moxie, one instant trigger included, plus Make an API Call for the rest, and a visual editor where each step is a module. n8n often has a node for the same app, so check whether one exists for Moxie before choosing. Pick the platform where your other automations already live, which keeps connections and monitoring in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations