Mothernode CRM Zapier integrationAutomate Mothernode CRM with Zapier.
The Mothernode CRM Zapier integration gives you 0 triggers, 4 actions and 0 searches. It only writes: another app has to start the Zap, then Mothernode CRM receives the lead, contact, customer or case. Here is what each action does and costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mothernode CRM Zapier integration really does
Mothernode CRM is a CRM for running a sales pipeline and keeping customers. On Zapier it can take part in a Zap: an automation with one starting event and one or more steps after it. Here the starting event always comes from another tool, and Zapier writes the result into Mothernode CRM for you.
Three results you can build with the four actions. A lead from every form answer: a new response in your form becomes a record through Create Lead. A customer file opened without retyping: a new row in a spreadsheet goes into Create Customer, where only the Company Name is required. A case logged from outside: a request collected elsewhere lands as a case with Create Case, title and description included.
What Zapier does not do here. Mothernode CRM has no trigger on Zapier, so nothing that happens inside the CRM can start a Zap: a new lead or a new case stays where it is. There is no search step either, so a Zap cannot check whether a contact or customer already exists before writing, and there is no update action. Every one of the four actions creates something new.
If you are weighing other tools for a CRM that only receives data, see our Make vs Zapier comparison and our Zapier review.
Zapier vocabulary, in one minute
Seven words come back on this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Mothernode CRM, that event always comes from another app.
- Action
- What the Zap does once it has started: the step that creates a lead, a contact, a customer or a case for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What a Mothernode CRM Zap really costs
Mothernode CRM is not a premium app on Zapier (an app kept for paid plans), so it runs on the free plan. The bill is counted in tasks.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, unlimited two-step Zaps
- TriggerNever costs a task
- Mothernode CRM triggersNone, the Zap starts in another app
The trigger never costs a task, and each action that succeeds counts as one: a Zap that creates a customer, then a contact, uses two tasks per run. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below concerns the trigger of the other app when it is a polling one; Mothernode CRM has no trigger of its own.
Connect Mothernode CRM to Zapier in three steps
- 01
Open your Apps page
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Mothernode CRM account linked once, then reused by every step that writes to it.
- 02
Find Mothernode CRM
Type Mothernode CRM in the search box of the dialog, pick it in the results, then click Add connection. A new tab opens on the Mothernode CRM sign-in screen.
- 03
Sign in and grant access
Log in to Mothernode CRM in that tab and grant Zapier access to the account. You need an account on Mothernode CRM, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Mothernode CRM Zap: turn form answers into leads
GoalWhen your form gets a new answer, check that it meets the condition you choose, then create a lead in Mothernode CRM.
- 01
Create the Zap and pick the trigger
Start a new Zap and choose your form tool as the app that starts it, with its new-response event. Mothernode CRM cannot start a Zap, so this first step always belongs to another app.
- 02
Test the trigger
Run the test and pick a real answer among the ones Zapier brings back, so the next steps are mapped on actual data rather than on empty fields.
- 03
Add a filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value to compare. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add Create Lead
Add Mothernode CRM with
Create Lead, pick the connection, then map the Prospect and the Reference, both required, from the answer of the form. - 05
Test, then publish
Run each step once and read what came back before going further. When the lead looks right in the test, publish the Zap to switch it on.
Mothernode CRM actions on Zapier
Mothernode CRM gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Case
ActionIn Zapier“Creates a new Case”
Logs a new case in Mothernode CRM, with a Case Title and a Case Description, both required.
Create Contact
ActionIn Zapier“Creates a Contact”
Adds a person to Mothernode CRM. Only the First Name is required, so even a short sign-up can create the contact.
Create Customer
ActionIn Zapier“Creates a Customer”
Creates a customer record in Mothernode CRM from a single required field, the Company Name.
Create Lead
ActionIn Zapier“Creates a Lead in Mothernode CRM”
Opens a new lead in Mothernode CRM from two required values, the Prospect and the Reference.
When a Mothernode CRM Zap breaks
Zapier attaches no help article to Mothernode CRM, so the cases below are the general Zapier limits that apply to it.
Three general cases are worth knowing before you publish. For anything else, see our Zapier troubleshooting guide.
Earlier records are not picked up
A Zap only reacts to what happens after you switch it on. Form answers or rows that existed before stay out; moving that backlog is a separate job.A big import gets held back
When the trigger of the other app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.The same item never runs twice
When the other app's trigger is a polling one, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating Mothernode CRM with Zapier?
A person reads every message.
