- Home
- Resources
- Integrations
- moreflow
moreflow Zapier integrationAutomate moreflow with Zapier.
moreflow Zapier integration: 5 triggers and 1 action carry your moreflow clients, contracts, invoices and payments into the rest of your tools. Four of the five triggers are instant, and the app works on the free plan, within its two-step limit.
Verified Trustpilot reviews · AI, automation & growth agency
What the moreflow Zapier integration does for you
The moreflow Zapier integration links your moreflow account to Zapier. A new client, a contract sent or signed, an invoice or a payment can then start work in another tool, and a sign-up elsewhere can become a moreflow client. moreflow presents itself as a tool for coaches and service businesses that want to automate their business.
A signed contract that tells the team. New Signed Contract starts the Zap when a client signs, and the next step posts a message or adds a line wherever your team follows new deals. Nobody has to keep an eye on the contract list.
A payment log that fills itself. New Payment and New Invoice each start a Zap of their own, so every invoice generated and every payment completed can land in a spreadsheet or your accounting tool without retyping.
A client file opened from outside. Create Client adds a client to moreflow from an event in another app, such as a form answer, with the email address, first name and last name filled in for you.
What Zapier does not do here: there is no action to update, delete or look up a client, and no search step at all. Nothing that existed before the Zap was switched on gets picked up either. Four triggers are instant, but New Client is checked on a timer, so it follows the interval of your plan. If you are still choosing your automation tool, see our Make vs Zapier guide.
Zapier vocabulary in one minute
Eight words come back all over this page. Here they are once, in ordinary English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a signed contract in moreflow. 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 creating a moreflow client.
- Task
- The unit Zapier bills: one action that completes successfully. The number on your plan counts those, and nothing else.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen yet.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a moreflow Zap really costs
Zapier bills tasks, not Zaps. The trigger never costs a task, and checking for new clients costs nothing however often Zapier looks. Each action that succeeds is one task; an action that fails is not counted.
- Free plan100 tasks a month, unlimited Zaps of two steps
- Premium appNo, moreflow works on every plan
- Trigger costNever counted as a task
- Filter or second actionMulti-step Zap, paid plan
moreflow is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to two steps. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below only matters for New Client, the one polling trigger of the app; the four instant triggers ignore it. On paid plans, how often New Client is checked can be changed, and a check can be run by hand from the editor.
Connect moreflow to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your moreflow account linked to Zapier once, then reused by every moreflow step you add later.
- 02
Pick moreflow
Search for moreflow in the dialog, select it, then click Add connection. A new tab opens so you can sign in to your moreflow account and finish the link from there.
- 03
Sign in and grant access
Sign in to moreflow in that tab and grant Zapier access to the account. 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.
Your first moreflow Zap
GoalPost a message in your team chat each time a client signs a moreflow contract, but only for the contracts that match a rule you set.
- 01
Create the Zap and pick the trigger
Create a new Zap, choose moreflow as the app that starts it and New Signed Contract as the event. Select your moreflow connection, or add it if this is the first time.
- 02
Test on a real contract
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you set up the next steps on a real signed contract.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, and the value to compare with. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the message
Add the action of your team chat that sends a message, then place the useful values of the contract in the text. Pick a text rule for text and a number rule for numbers in the filter.
- 05
Test, then publish
Test each step once and read what came back before going further. When the message lands as expected, click Publish to switch the Zap on.
moreflow triggers
5 events start a Zap when something happens in moreflow, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
New Client
Polling triggerIn Zapier“Triggers when a new client is created.”
Starts the Zap when a client is created in moreflow, which makes it the natural entry point for anything that should follow a new relationship: a welcome sequence elsewhere, a row in a tracking sheet, a card on a board.
New Contract Sent
Instant triggerIn Zapier“Triggers when a new contract is sent to a client.”
Fires when moreflow sends a new contract to a client. It marks the moment a contract goes out to the client, before anything is signed.
New Signed Contract
Instant triggerIn Zapier“Triggers when a contract is signed by the client.”
Runs when a client signs a contract in moreflow. It is the event that closes a deal, which makes it a good moment to tell the people who deliver the work.
New Invoice
Instant triggerIn Zapier“Triggers when an invoice is generated.”
Kicks off the Zap whenever moreflow generates an invoice. Every invoice can then be copied into another tool the moment it exists, without waiting for the client to pay it.
New Payment
Instant triggerIn Zapier“Triggers when a payment is completed by the client.”
Triggers when a client completes a payment in moreflow. It is the event to follow when money, not paperwork, is what matters to the next step.
moreflow actions
moreflow gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Client
ActionIn Zapier“Action to create a new client”
Adds a new client to moreflow from an event in another app. The client exists in moreflow without anyone typing the details twice.
When a moreflow Zap breaks
Zapier attaches no help article to moreflow and documents no limit of its own for this app. What breaks is what breaks on any Zap, plus one case tied to the polling trigger.
Four general limits apply to moreflow as to any other app, and each gets its own card below. For help with a Zap that misbehaves, see our Zapier troubleshooting guide.
Older records are ignored
A Zap only reacts to what happens after it is switched on. Clients, contracts or payments that existed before are never picked up, and moving them is a separate job.A Zap that sets itself off again
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. Keep that general precaution in mind.A sudden batch held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.The same client, only once
On a polling trigger such as New Client, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating moreflow with Zapier?
A person reads every message.



