Resources · Zapier integration

Moxie Zapier integrationAutomate Moxie with Zapier.

The Moxie Zapier integration gives you 33 triggers, 14 actions and 1 search. Every trigger is instant, the app runs on the free plan, and this page covers what each operation does, what it costs and where a Moxie Zap goes wrong.

See the 48 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Moxie Zapier integration does for you

The Moxie Zapier integration links your Moxie workspace, the all-in-one tool for running a freelance business, to the other apps you use. Something happens in Moxie, such as a signed agreement, a payment or a new ticket, and Zapier passes it on. Or another app sends something in, and Moxie creates the client, project or invoice for you.

Three results show what it can do. First, a paper trail of money: Payment Received and Invoice Sent push each invoice event to a spreadsheet, so your numbers live in one place without retyping. Second, a project that opens itself: when Agreement Signed fires, Create Project sets up the work in Moxie for that client. Third, a support desk that talks to the rest of your tools: Ticket Created and Ticket Comment can post to your team chat, while Create Ticket files requests coming from elsewhere.

What Zapier does not do here matters just as much. There is a single search, Find a Client, so you cannot look up a project, an invoice or a ticket by itself. No action edits an existing client, project or ticket, and the only delete action is Delete Calendar Event. Three triggers, the Proposal ones, are flagged as deprecated by Moxie itself in favour of the Agreement ones.

The good news sits on the trigger side: all 33 triggers are instant, so timing does not depend on your plan. If you want the same app on another tool, see our Moxie Make integration page.

Vocabulary

The Zapier words you need, in one minute

Eight terms come back throughout this page. Here they are in plain English, once.

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 in an app that starts the Zap, such as a payment landing in Moxie. 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 in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant trigger
A trigger the app reports itself: Moxie calls Zapier the moment the event happens, so nothing waits for a timed check.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found, such as a client's id.
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 Moxie Zap really costs

Moxie is not a premium app, so it works from Zapier's free plan. You pay in tasks, and only actions produce them.

  • Trigger0 task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan

A trigger never costs a task. Each action that succeeds counts once, so a three-action Zap uses three times more than a one-action Zap, and an action that fails is not counted. A few actions take more than one task when they complete. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. A filter, a search or a second action makes it multi-step, and that needs a paid plan. The interval grid below is for polling triggers: it does not apply to Moxie, whose triggers are all instant.

Connect

Connect Moxie to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens where you type Moxie and pick it from the list. A connection is your Moxie account linked once, then reused by every Zap.

  2. 02

    Sign in to Moxie

    Click Add connection. A new tab opens on Moxie: sign in with the account you want the Zaps to work on. You need a Moxie account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Grant access

    Give Zapier access to the account when Moxie asks. The tab closes and the connection is ready. Every Moxie step in every Zap can now pick it, so you only do this once per account.

First Zap

Your first Zap: log the payments that matter

GoalEvery Moxie payment that meets a condition you set is added as a row to your spreadsheet.

  1. 01

    Build the trigger

    Create a Zap, pick Moxie as the app and Payment Received as the event, then choose the Moxie connection you added earlier.

  2. 02

    Test it

    Run the test. Zapier brings back the three most recent payments of the connected account, so you map the next steps on a real one rather than on a blank.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Set the field to look at, the rule and the value to compare with. The filter makes this a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the row

    Add your spreadsheet as the action and map the payment details from the trigger into the columns. Test the step once and read what came back before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. Each payment that passes the filter becomes a row, and each row written counts as one task.

Triggers

The 33 Moxie triggers

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

1

Agreement Sent

Instant trigger

In Zapier“Triggers when a proposal is sent either via link or email.”

Every agreement leaving your Moxie workspace sets this one off, whether you shared it by link or sent it by email. You get a clean record of every offer that went out.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log each sent agreement in a spreadsheet so you can see which ones still need a follow-up.
Watch out
this is the current trigger; the older Proposal Sent does the same job and is flagged as deprecated.
2

Agreement Signed

Instant trigger

In Zapier“Triggers when an agreement is accepted and signed with e-signature.”

Signed agreements are what this trigger listens for: a client accepts and signs with e-signature. That signature can set the next steps going, from the project to the first invoice.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
pair it with Create Project so the project opens in Moxie the moment the deal is closed.
Watch out
use this one rather than Proposal Signed, which Moxie marks as deprecated.
3

Agreement Viewed

Instant trigger

In Zapier“Triggers when a user views the proposal.”

Opening an agreement you sent is enough to start this Zap. It is a signal of interest, not of a decision, and it gives you a reason to get in touch while the offer is fresh.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
post a short note in your team chat so whoever owns the deal knows the client is reading.
Watch out
the older Proposal Viewed covers the same kind of event and is flagged as deprecated; build on this one.
4

Client Created

Instant trigger

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

New client records in Moxie set this trigger off. Whatever tool you keep beside Moxie hears about the newcomer without you typing the name twice.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
copy each new client into a spreadsheet or a mailing list you manage elsewhere.
Watch out
a Zap that writes into the very place its own trigger watches can set itself off again; keep that in mind before you add a Moxie action here.
5

Client Deleted

Instant trigger

In Zapier“Triggers when a client record is deleted in Moxie.”

Removing a client record from Moxie is the event here. This is how your other tools learn that a client is gone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
mark the matching row in your spreadsheet as closed, so your lists stop counting a client you dropped.
Watch out
what this trigger sends about the removed client is decided by Moxie; check it at the test before you map anything.
6

Client Updated

Instant trigger

In Zapier“Triggers when a client record is updated in Moxie.”

Edits to a client record start this one. Useful when Moxie is where client details are kept up to date, and other tools should 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
keep a copy of client details in another app in step with what Moxie holds.
Watch out
which edits count as an update is decided by Moxie; run a test after a typical change and check what comes through.
7

Task Created

Instant trigger

In Zapier“Triggered when a Project Task is created”

Adding a task to a Moxie project is what wakes this trigger. Each new piece of work on a project can then show up wherever your team actually looks.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
announce new project tasks in your team chat so nobody has to check Moxie to know what is coming.
Watch out
if another Zap of yours adds tasks with Create Task, remember that a Zap writing where its trigger watches can set itself off again.
8

Task Deleted

Instant trigger

In Zapier“Triggered when a Project Task is deleted”

Project tasks that get removed in Moxie are reported here. Without it, a copy of that task elsewhere would sit there forever, still looking open.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
cross the task off in a shared list kept outside Moxie.
Watch out
Moxie has no search for tasks, so whatever you need must come from the trigger's own data; check it at the test.
9

Task Updated

Instant trigger

In Zapier“Triggered with a Project Task is updated.”

Updates to a project task come through this trigger, so the people following that task elsewhere see the change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
combine it with a filter to react only to the change you care about, such as a given status.
Watch out
which changes count as an update is up to Moxie, and each run that reaches an action costs a task; a filter, on a paid plan, keeps only the ones you follow.
10

Task Approval

Instant trigger

In Zapier“Triggers when a new Deliverable is ready for client approval.”

Tasks ready for the client to approve start this Zap. It marks the hand-over point between your work and the client's sign-off.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send yourself or your team a reminder that something now waits on the client.
Watch out
Approve Task moves a task out of that status; read its note before you build a Zap that touches both sides of the approval.
11

Form Completed

Instant trigger

In Zapier“Triggers when a form is completed.”

Someone filling in one of your Moxie forms is the starting point. It is a clean entry point for anything that starts with a client answering questions.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
push each completed form into a spreadsheet to keep answers in one place.
Watch out
the trigger asks for a Form ID, typed exactly as it appears in Moxie; check at the test that real answers come through.
12

Invoice Sent

Instant trigger

In Zapier“Triggers when an invoice is sent in Moxie.”

Invoices going out from Moxie set this one off. You get the moment a bill reaches a client, which is where tracking of what is owed begins.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add each sent invoice to a follow-up sheet, next to the payments logged by Payment Received.
Watch out
the event is the sending of the invoice; check at the test what Moxie hands over before you map your columns.
13

Meeting Cancelled

Instant trigger

In Zapier“Triggers when a meeting is cancelled”

Cancelled meetings booked in Moxie are reported here. The free slot and the follow-up both start here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn your team chat so whoever prepared the meeting can stop.
Watch out
a rescheduled meeting comes through Meeting Updated instead, so a cancellation Zap alone will not catch a moved slot.
14

Meeting Scheduled

Instant trigger

In Zapier“Triggers when a new meeting is scheduled”

Booking a new meeting in Moxie starts this trigger. Every booking can then reach the people or tools that need to prepare 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
post each booking in your team chat, with the time mapped from the trigger.
Watch out
a cancelled or moved booking has its own trigger, so this one alone only covers new meetings.
15

Meeting Updated

Instant trigger

In Zapier“Triggers when a meeting is updated or rescheduled”

Meetings that get changed or moved to another time come through here. It covers the reschedules that a simple booking alert misses.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
update the matching line in a shared planning sheet when a client moves a call.
Watch out
both edits and reschedules come through here; a filter is how you keep only one kind, on a paid plan.
16

Opportunity Created

Instant trigger

In Zapier“Triggered with a pipeline opportunity is created”

Opportunities entering your Moxie pipeline set this trigger off. That is the first sign of a possible deal, before any agreement exists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a running list of new opportunities in a spreadsheet you review with your team.
Watch out
every new opportunity reaches the Zap; a filter is how you keep only some of them, on a paid plan.
17

Opportunity Deleted

Instant trigger

In Zapier“Triggered with a pipeline opportunity is deleted”

Removing an opportunity from the pipeline is the event here. Your other tools learn that a possible deal is off the table.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
close the matching row in your sales sheet so your totals stay honest.
Watch out
Moxie has no search for opportunities, so take what you need from this trigger's own data, checked at the test.
18

Opportunity Updated

Instant trigger

In Zapier“Triggered with a pipeline opportunity is updated”

Changes to a pipeline opportunity start this one, so your other tools follow the deal as it evolves.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
with a filter on a field you choose, alert your team only about the deals you care about.
Watch out
make a real change in Moxie before you set the filter, and read at the test which fields actually arrive.
19

Payment Received

Instant trigger

In Zapier“Triggers when a payment is received either vial Stripe or manual entry.”

Payments landing in Moxie, through Stripe or entered by hand, start this Zap. It is the event that closes the loop on an invoice.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add every payment to your bookkeeping sheet without retyping it.
Watch out
both Stripe and manual payments come through here; check at the test which details each kind carries.
20

Project Completed

Instant trigger

In Zapier“Triggers when a project is set to "complete" in Moxie.”

Setting a project to complete in Moxie is what this trigger waits for. It marks the end of the work and the start of everything that follows 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
send a thank-you or a feedback request through another tool once a project wraps up.
Watch out
the event is the project being set to complete in Moxie, so the status has to be changed there.
21

Project Created

Instant trigger

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

New projects set up in Moxie start this one. Every new job can then appear in the tools your team already 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
open a matching line in a shared planning sheet the moment a project exists.
Watch out
the tasks inside the project have their own trigger, Task Created; this one only reports the project itself.
22

Project Updated

Instant trigger

In Zapier“Triggers when the settings for a project are updated.”

Project settings that change are reported here. It follows the project itself, not the tasks inside it, which have their own 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
keep a project overview elsewhere in step with Moxie when names or settings move.
Watch out
tasks have their own trigger, Task Updated, so pick the one that matches what you follow.
23

Proposal Sent

Instant trigger

In Zapier“[DEPRECATED - Please use "Agreement Sent"] - Triggers when a proposal is sent either via link or email.”

Proposals going out by link or email set this older trigger off. Moxie's own description now flags it as deprecated and points to Agreement Sent instead.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
only to keep an older Zap running while you move it over to Agreement Sent.
Watch out
for any new Zap, pick Agreement Sent, the trigger Moxie now points to.
24

Proposal Signed

Instant trigger

In Zapier“[DEPRECATED - Please use "Agreement Signed"] - Triggers when a proposal is accepted and signed with e-signature.”

Accepted and e-signed proposals start this older trigger. It still shows in the editor, but Moxie marks it as deprecated in favour of Agreement Signed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
in an existing Zap built before the agreement triggers, until you swap it out.
Watch out
building something new on it means rebuilding later; start from Agreement Signed.
25

Proposal Viewed

Instant trigger

In Zapier“[DEPRECATED - Please use "Agreement Viewed"] - Triggers when a user views the proposal.”

Opening a proposal is enough for this older trigger. Moxie labels this trigger deprecated and sends you to Agreement Viewed for the same event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
as a stopgap in an old Zap that already relies on it.
Watch out
a new Zap should use Agreement Viewed, the trigger Moxie now recommends for this event.
26

Ticket Closed

Instant trigger

In Zapier“Triggers and a support ticket is closed”

Closing a support ticket in Moxie is the event here. It is the end of a request, and a natural point to measure or follow 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
log closed tickets in a sheet to see what clients ask about most.
Watch out
a closed ticket and a deleted one are two separate triggers; pick the one that matches your process.
27

Ticket Comment

Instant trigger

In Zapier“Triggers when a comment is created on a ticket”

Comments added to a ticket start this one. Conversations inside Moxie's support desk can then reach the place your team 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
post each new comment to your team chat so replies do not wait.
Watch out
a Zap that writes into the very place its own trigger watches can relaunch itself; keep that in mind before adding a Moxie action.
28

Ticket Created

Instant trigger

In Zapier“Triggers when a new support ticket is created”

Opening a new support ticket in Moxie sets this trigger off. Every client request becomes something your other tools can see.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alert your team chat for each new request, with the subject mapped from the trigger.
Watch out
later comments come through Ticket Comment, not here; this trigger only covers the opening of the request.
29

Ticket Deleted

Instant trigger

In Zapier“Triggers when a support ticket is deleted”

Deleted support tickets are reported here. Copies of that ticket elsewhere can be cleaned up instead of lingering.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
remove or mark the ticket in a tracking sheet kept outside Moxie.
Watch out
what Moxie sends about a removed ticket is up to Moxie; check it at the test before mapping.
30

Ticket Updated

Instant trigger

In Zapier“Triggers when a support ticket is updated”

Once a support ticket is open, each update to it comes through this trigger, which follows the request from there.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
with a filter, flag tickets that move to a state you watch closely.
Watch out
each run that reaches an action costs a task, so keep the Zap to the changes you follow with a filter, on a paid plan.
31

Time Worked Created

Instant trigger

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

Recording a new time worked entry in Moxie starts this Zap. Hours become data that your other tools can add 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
copy each entry into a timesheet you share with a client or partner.
Watch out
a corrected entry has its own trigger, Time Worked Updated, so pair the two if your timesheet must stay exact.
32

Time Worked Deleted

Instant trigger

In Zapier“Triggers when a time worked record is deleted.”

Time worked records that get removed are reported here. Without it, hours deleted in Moxie would stay counted elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
take the entry out of your external timesheet so totals match Moxie.
Watch out
Moxie has no search for time entries, so map what you need from the trigger, checked at the test.
33

Time Worked Updated

Instant trigger

In Zapier“Triggers when a time worked entry has been updated.”

Edited time worked entries come through this trigger. Corrected hours reach your other tools instead of leaving an old figure behind.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
update the matching line in a shared timesheet after someone fixes a start or end time.
Watch out
finding that matching line needs a lookup in the other app; Moxie's only search is for clients.
Actions

The 14 Moxie actions

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

1

Apply Payment

Action

In Zapier“Apply payment to open invoice”

Records a payment against an open invoice in Moxie.

When to use it
when money is confirmed in another tool and the payment should appear on the invoice in Moxie.
Watch out
the invoice number must match Moxie exactly, the date goes in YYYY-MM-DD, and the amount cannot exceed what is still owed.
2

Approve Task

Action

In Zapier“Approve a task and move it from the Client Approval status to the next status in the Kanban”

Approves a task and moves it from the Client Approval status to the next column of the Kanban board.

When to use it
when the client's approval is given in another tool, such as a form.
Watch out
it needs the client, project and task names; check at the test that Moxie finds the right task.
3

Create Client

Action

In Zapier“Creates a new client record in Hectic”

Adds a new client record to Moxie from data that arrives in another app, such as a form answer.

When to use it
turn each new enquiry collected elsewhere into a Moxie client.
Watch out
it requires a Client Name and a Record Type; decide in advance which record type your Zap should set.
4

Create & Optionally Send Invoice

Action

In Zapier“Create an invoice for a client and optionally send it via Hectic Mail.”

Builds an invoice for a client and, if you choose, sends it from Moxie as well.

When to use it
bill a client automatically once work logged elsewhere is done.
Watch out
it wants the client's id, not the name; get it from Find a Client or Create Client in an earlier step.
5

Create Opportunity

Action

In Zapier“Create a new pipeline opportunity”

Opens a new opportunity in your Moxie pipeline. Only a name is required, so it is one of the easiest actions to wire.

When to use it
feed leads from a form tool straight into the pipeline you work from.
Watch out
a Zap that writes where its own trigger watches can set itself off again, so check your trigger before using it.
6

Create or Update Calendar Event

Action

In Zapier“Create or update a calendar event in Moxie”

Writes an event into Moxie's calendar, or updates it if it already exists.

When to use it
block time in Moxie for work planned elsewhere.
Watch out
start and end times use the ISO format, the timezone is an official name, and name, description and busy are required.
7

Create Project

Action

In Zapier“Create a project and optionally use a template”

Sets up a project in Moxie for a client, with the option of starting from one of your templates.

When to use it
open the project automatically after Agreement Signed.
Watch out
it needs a Project Name and a Client Name; check at the test how Moxie handles the client name you send.
8

Create Task

Action

In Zapier“Create a task in the project management system”

Adds a task to an existing project, inside Moxie's project management.

When to use it
when a request arrives in another tool and needs to become work on a live project.
Watch out
the task name, client name and project name are all required, and the project must already exist.
9

Create Ticket

Action

In Zapier“Create a Ticket for a client and contact”

Opens a support ticket for a client contact, with a subject and a first comment.

When to use it
route requests from a contact form into Moxie's support desk.
Watch out
the ticket is rejected if the email is not a known contact, and the ticket type must match the one set in your workspace settings.
10

Create Ticket Comment

Action

In Zapier“Adds a comment (public or private) to an existing ticket.”

Adds a public or private comment to an existing ticket, identified by its number.

When to use it
when a reply written in another tool should end up on the ticket.
Watch out
the email must belong to a known contact or team member; the private setting is ignored when that email is a client contact's.
11

Create Time Worked

Action

In Zapier“Creates a time worked entry”

Records a time worked entry in Moxie, from a start time and an end time.

When to use it
send hours tracked in another app into Moxie so billing sees them.
Watch out
three optional boxes can create the client, the project or the task when none is found; leave them off if you do not want new records appearing.
12

Delete Calendar Event

Action

In Zapier“Deletes a calendar event in Moxie by the external ID.”

Removes a calendar event from Moxie, found by its external ID.

When to use it
clear a slot in Moxie when the matching event is cancelled in another calendar.
Watch out
the Event Id is usually the ICS event ID from the linked calendar; map it from the source, never type it.
13

Create Expense

Action

In Zapier“Creates a new expense record in the Hectic accounting system.”

Adds an expense to Moxie's accounting, with its date, amount and currency.

When to use it
log costs captured in another tool without retyping them.
Watch out
the currency is a 3 character ISO code, and paid, reimbursable and markup percentage are all required too.
14

Create Form Submission

Action

In Zapier“Creates a new form submission and adds the record to the inquiry section of SalesPipeline (pro only).”

Creates a form submission in Moxie and adds it to the inquiry part of the sales pipeline.

When to use it
bring answers from an outside form into Moxie as if they came through a Moxie form.
Watch out
Moxie's own description marks it as pro only, and it needs the form's name.
Searches

The Moxie search

1 search step looks for data that already exists in Moxie, so a later step can use it.

Moxie has one search step. You find it at the bottom of the action list, under SEARCH. Three settings decide what happens when the result is not a clean single match.

1

Find a Client

Search

In Zapier“Finds a client by either name or contact email address.”

Looks up a client by name or by a contact's email, then hands the record to the next steps.

When to use it
right before Create & Optionally Send Invoice, which needs the client's id rather than a name.
Watch out
the query tries both the name and the contact email, so a common name can match more than one client.

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 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 and asks for the fields needed to create the missing item. Find a Client offers no such variant.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on.
When it breaks

When a Moxie Zap breaks

Zapier attaches no help article of its own to Moxie, so the traps below are the general ones of any Zap, applied to this app.

Read these three cases before you publish. If something behaves oddly afterwards, see our Zapier troubleshooting page.

  • Nothing from before the Zap

    A Zap only reacts to what happens after it is switched on. Clients, invoices and tickets already in Moxie are never picked up, and moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count fast.

  • A sudden big batch

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

Need help automating Moxie with Zapier?

A person reads every message.

FAQ

Moxie Zapier integration: your questions

01Is the Moxie Zapier integration free?
Yes, it works on Zapier's free plan, because Moxie is not a premium app. The free plan gives you 100 tasks a month and an unlimited number of Zaps. The limit is their size: each Zap holds two steps, one trigger and one action. A Zap that adds a filter, a search such as Find a Client, or a second action is multi-step and needs a paid plan. A simple pairing, like a new client copied to a spreadsheet, stays free.
02How many tasks does a Moxie Zap use?
One task per action that completes successfully, and nothing for the trigger. A Moxie event starting your Zap costs nothing, whichever of the 33 triggers you use. If the Zap runs one action, each event that reaches it costs one task; with three actions, three. An action that fails is not counted against your plan. A few actions take more than one task when they complete, so read the task count on your first runs.
03Does Moxie trigger Zaps in real time?
Yes. All 33 Moxie triggers are instant: Moxie tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. The polling interval of each plan does not apply to these triggers. In the editor, a Zap built on an instant trigger shows a lightning bolt. That matters most on the free plan, where polling triggers on other apps wait 15 minutes between checks. Instant does not mean free of limits, though: each action still counts as a task.
04What do you need to connect Moxie to Zapier?
A Moxie account, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection starts from the Apps page of your Zapier account: click + Add connection, search Moxie, sign in on the tab that opens and grant access. You do it once, and every Moxie step in every Zap reuses that connection. Pick the account that holds the clients and projects your Zaps should work on.
05Why is Create Ticket rejected?
Check first that the email you mapped is a known contact in your Moxie workspace: Moxie refuses a ticket when it cannot find that email. The ticket type is the other trap: it must be the exact text of a type set in your workspace settings, under Communicator, then Tickets. Make sure the contact exists before the Zap runs, and test the step with a real address before you publish.
06What if the Moxie operation you need is not there?
Then Zapier cannot do it with Moxie today. Moxie's page on Zapier shows the current list of triggers, actions and searches, so check there before you design a Zap around a step that does not exist. Today the gaps are clear: one search, for clients only, and no action that edits a client, a project or a ticket. If the missing step is central to your process, weigh another tool for that part.
07Zapier, Make or n8n for Moxie?
Choose by criteria rather than by ranking. On Zapier, Moxie brings 33 instant triggers, so speed does not depend on your plan, plus 14 actions and one client search. The limits to weigh are the two-step cap of the free plan and the lack of searches beyond clients. Check what Make and n8n offer for Moxie on the operations you need most, then compare how each tool counts the volume of actions you expect.
Same platform

Other docs you might need on this stack.

Browse all integrations