Resources · Zapier integration

MoonClerk Zapier integrationAutomate MoonClerk with Zapier.

The MoonClerk Zapier integration gives you 5 triggers, 0 actions and 1 search. Every trigger is instant, so a new plan, a payment or a failed charge reaches your other tools straight away, even on the free plan. Zapier reads from MoonClerk here; it never writes back into it.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MoonClerk Zapier integration actually does

The MoonClerk Zapier integration listens to what happens to your recurring plans and payments in MoonClerk, and passes each event to the rest of your tools. A Zap (the automation you build on Zapier: one event that starts it, then the steps that follow) does the relaying, so nobody has to copy payment details by hand.

Three things people get out of it. A payment log that fills itself: New Payment or Payment Succeeded adds a line to a spreadsheet every time money comes in. A follow-up queue for problems: Plan Payment Failed and Plan Ended tell your team chat that a subscriber needs attention. A welcome sequence: New Plan hands a fresh subscriber to your email tool, and Retrieve a Plan can fetch the plan details when a later step needs them.

What Zapier does not do for MoonClerk: it has no action for this app. You cannot create a plan, refund a payment or cancel a subscription from a Zap. The integration only reads, through five event triggers and one lookup. If the job is to change something inside MoonClerk, that part stays in MoonClerk itself, and a Zap can at most tell a person to go and do it.

Choosing the automation tool is a separate question. Before you commit, see our Make vs Zapier comparison and our n8n vs Zapier comparison.

Vocabulary

The Zapier words on this page, in plain English

Seven terms come back on every page of this kind. Read them once and the rest of the page goes faster.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for that event to happen.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills. One task is one action your Zap finished successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the unseen ones.
Instant trigger
A trigger the app reports itself. It calls Zapier the moment the event happens, so nothing waits for a check.
Filter
A step that lets the Zap continue only when the incoming data meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the following steps can use what it found.
Cost

What a MoonClerk Zap really costs

Zapier bills tasks, not events. A MoonClerk trigger firing costs nothing; only the actions that run after it and succeed are counted.

  • TriggerNever costs a task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • MoonClerkNot a premium app

The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger, one action. Add a filter, a second action or the Retrieve a Plan search and the Zap becomes a multi-step Zap, which needs a paid plan. MoonClerk is not a premium app, so it works from the free plan. The interval grid below only concerns polling triggers: all five MoonClerk triggers are instant, so it does not apply to them. An action that fails is not counted, and every action that succeeds is counted on its own, so a three-action Zap uses three times more.

Connect

Connect your MoonClerk account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your MoonClerk account linked to Zapier once, then reused by every Zap that touches MoonClerk.

  2. 02

    Find MoonClerk and start

    Type MoonClerk in the search box of the dialog, pick it, then click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and allow access

    A new tab opens on MoonClerk. Sign in there, then grant Zapier access to the account. From then on, every MoonClerk step of your Zaps reuses that connection.

First Zap

Your first Zap: alert the team when a plan payment fails

GoalWhen a recurring payment fails in MoonClerk, look up the plan and post a message in your team chat.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose MoonClerk as the app and Plan Payment Failed as the event. Select the MoonClerk connection you added earlier.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you can map fields from a real failed payment rather than a guess.

  3. 03

    Add the plan lookup

    Add Retrieve a Plan as the next step and map the Customer Id from the trigger into Customer ID. This search makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the message step

    Add your team chat as the action and build the message from the fields the trigger and the search returned. Test this step and read what came back before going further.

  5. 05

    Publish

    Publish the Zap to switch it on. Because the trigger is instant, the editor shows a lightning bolt on it, and the next failed payment starts the Zap straight away.

Triggers

MoonClerk triggers

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

1

Plan Payment Failed

Instant trigger

In Zapier“Triggers when a recurring plan payment fails.”

Fires when a payment on a recurring plan does not go through in MoonClerk. It turns a quiet failed charge into an event your other tools can act on.

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 someone on the team to contact the subscriber about the failed payment, through a chat alert or a task in your to-do tool.
Watch out
the trigger is about recurring plan payments; whether a one-off payment failure also shows up here is something to confirm at test.
2

Plan Ended

Instant trigger

In Zapier“Triggers when a recurring plan is canceled or expires.”

Reacts to the end of a recurring plan, whether the subscriber cancelled it or it simply expired. That one event covers both ways a subscription stops.

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 the person from a members list or tag them in your email tool so they stop receiving subscriber-only messages.
Watch out
cancelled and expired land in the same trigger; if your follow-up should differ, look at what the test returns before deciding how to tell them apart.
3

New Plan

Instant trigger

In Zapier“Triggers when a new recurring plan is created.”

Kicks off when a new recurring plan is created in MoonClerk, which is the moment a subscription 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
send the new subscriber into a welcome sequence in your email tool, or add them to a list in your spreadsheet.
Watch out
it only concerns new recurring plans; to follow every payment made instead, New Payment is the trigger to pick.
4

New Payment

Instant trigger

In Zapier“Triggers when a payment has been made on MoonClerk.”

Starts a Zap each time a payment is made on MoonClerk. Pick it when the payment itself is the event you care about, not the plan around 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
keep a running payments sheet that anyone on the team can open without logging into MoonClerk.
Watch out
Payment Succeeded exists alongside it; run both tests and compare what each returns before you choose, so the log does not hold the same payment twice.
5

Payment Succeeded

Instant trigger

In Zapier“Triggers when a payment has succeeded on MoonClerk.”

Goes off once a payment has actually succeeded on MoonClerk. Where New Payment covers a payment being made, this one is about the money having gone through.

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 the receipt-style thank-you email, or unlock access in another tool, only once the charge is confirmed.
Watch out
do not build two Zaps that answer the same payment through New Payment and Payment Succeeded unless you mean to; each one runs its own actions and each counts its own tasks.
Searches

MoonClerk search

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

A search step does not change anything. It fetches a record that already exists so later steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH.

1

Retrieve a Plan

Search

In Zapier“This will get all the information about a specific plan.”

Pulls all the information MoonClerk holds on one specific plan, so a later step can use details the trigger did not carry.

When to use it
after a payment trigger, when your message or your spreadsheet row needs the plan behind that payment.
Watch out
Customer ID is required. With a MoonClerk trigger upstream, insert its Customer Id field here instead of typing one, and adding this step makes the Zap multi-step, so it needs a paid plan.

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 skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. MoonClerk has no find-or-create variant on Zapier, so Retrieve a Plan only ever finds, it never creates a plan.
  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 at once.
When it breaks

When a MoonClerk Zap breaks

Zapier links no help article to MoonClerk and lists no limit of its own for it. What goes wrong comes from how Zaps work in general.

These four cases cover what is documented for a MoonClerk Zap. For any other case, see our Zapier troubleshooting guide.

  • Old payments never come through

    A Zap only reacts to what happens after you switch it on. Payments and plans that existed before are not picked up; moving that history is a separate job.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration for instance, Zapier's flood protection can hold those runs back.

  • The plan lookup stops the Zap

    With the default setting, a Retrieve a Plan that finds nothing ends the Zap at that step, and every step relying on it is skipped.

  • Customer ID left unmapped

    Retrieve a Plan requires a Customer ID. Map the Customer Id field from the MoonClerk trigger and check the result at test before publishing.
Need help

Need help automating MoonClerk with Zapier?

A person reads every message.

FAQ

MoonClerk Zapier integration: common questions

01Is the MoonClerk Zapier integration free?
Yes, it works on the free plan, because MoonClerk is not a premium app. That plan gives you 100 tasks a month and an unlimited number of Zaps. The catch is the size of each Zap: one trigger and one action, nothing more. So a MoonClerk trigger feeding one step in another app is free, while a Zap that adds the Retrieve a Plan search, a filter or a second action becomes multi-step and needs a paid plan.
02How many tasks does a MoonClerk Zap use?
One per successful action, every time the Zap runs. The MoonClerk trigger never costs a task, and an action that fails is not counted either. A Zap that answers each new payment with one spreadsheet row uses one task per payment. If the same Zap also posts in a chat, it uses two per payment, since every action that succeeds is counted on its own. A few apps and actions take more than one task when they complete.
03Is MoonClerk on Zapier real time?
Yes, for all five triggers. Each one is instant: MoonClerk tells Zapier the moment the event happens, so the Zap starts right away whatever plan you are on. The interval grid of the plans does not apply to these triggers, which matters most on the free plan where polling triggers only check every 15 minutes. In the editor, a Zap started by an instant trigger shows a lightning bolt. On a polling trigger the free plan would mean waiting; here it does not.
04What do you need to connect MoonClerk to Zapier?
An account on MoonClerk, plus read or write access on anything you do not own yourself and want the Zap to touch. To set it up, you open Apps, click + Add connection, search for MoonClerk, then sign in to it in the tab that opens and grant Zapier access. The connection is made once and reused by every MoonClerk step afterwards. Each other tool in your Zap gets its own connection, made the same way.
05Can a Zap cancel or refund a MoonClerk payment?
No. The integration has no action, only five triggers and the Retrieve a Plan search. Zapier can hear about new plans, payments, failures and ended plans, and it can look a plan up, but it cannot change anything inside MoonClerk. Refunds, cancellations and plan edits stay in MoonClerk itself. What a Zap can do is send the event elsewhere, for example a chat alert asking someone to handle the refund by hand.
06What if the MoonClerk operation you want is not available?
Then Zapier cannot do it for MoonClerk today. The MoonClerk page on Zapier shows the current list of triggers and searches, which is the reference to check before building. If what you need is an event that exists, check whether a filter placed after an existing trigger such as New Payment gets you there, on a paid plan. If what you need is a change inside MoonClerk, no Zap can make it, since the app offers no action.
07Zapier, Make or n8n for MoonClerk?
Decide on criteria rather than on a ranking. First, which tool offers the MoonClerk events you rely on; on Zapier that is five instant triggers and one search, with no action. Second, how each tool counts usage against the volume of payments you expect. Third, which tool your team already knows how to build in. On Zapier, instant triggers mean no waiting even on the free plan, and a two-step Zap costs nothing beyond its tasks.
Same platform

Other docs you might need on this stack.

Browse all integrations