modular365 Zapier integrationAutomate modular365 with Zapier.
modular365 Zapier integration: 0 triggers, 3 actions, 0 searches. modular365 receives data, it does not start anything: another app spots the event, then a Zap writes or updates a record in a modular365 table. Here is what it costs, how to connect, and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the modular365 Zapier integration does for you
The modular365 Zapier integration lets your automations write into modular365, the multi-tenant ERP built for service businesses, with CRM, invoicing, scheduling, work orders, payments and document generation. It works as a destination only: an event happens in another app, and the Zap adds or changes records in a modular365 table of your choice.
Three results come up most. A new record per submission: someone fills in your form, and Insert Record adds a row to the table you picked, with the answers mapped into its fields. One record corrected, and only one: Update Record changes the single record that matches your filters, and it fails instead of guessing when none or several match. A batch change in one step: Update Multiple Records rewrites every record that matches your filters at once, which saves steps and needs care.
What Zapier does not do here is just as useful to know. Nothing that happens inside modular365 can start an automation, because the app has no trigger on Zapier. There is no search step either, so a Zap cannot fetch a record first to reuse its values further down. And every action asks for a Table, so the account you connect has to see the table you want to write to.
Comparing tools before you build? See our n8n vs Zapier guide, or our Make vs Zapier guide.
The Zapier words you need, in one minute
Zapier comes with its own vocabulary. Each word is explained once here, in plain terms, then used as is on the rest of the page.
- 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. modular365 has none, so another app always plays this part.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Here, a record.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so nothing waits for a check.
- Filter
- A Zapier step that lets the Zap go on only when what arrived meets your condition. Not the same as the record filters of modular365.
- Connection
- Your modular365 account linked to Zapier once, then reused by every step that writes into modular365.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a Zapier filter makes one, and it then needs a paid plan.
What a modular365 Zap really costs
modular365 is not a premium app, so it works from the free plan. Zapier bills completed actions, not checks.
- Trigger0 tasks
- Each action that succeeds1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The trigger of the other app never costs a task, and looking for new data costs nothing either. Each modular365 action that succeeds counts as one task; one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: add a Zapier filter or a second action and you need a paid plan. The interval grid below only concerns a polling trigger of the app that starts your Zap. modular365 has no trigger, so the grid never applies to it.
Connect modular365 to Zapier in three steps
- 01
Open the connections page
In your Zapier account, go to Apps, then click + Add connection. Before you start, have an account on modular365, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick modular365
In the dialog, type the app name, select modular365 in the results, then click Add connection. A new tab opens on the modular365 side for the sign-in.
- 03
Sign in and grant access
Sign in to modular365 in that tab, then let Zapier use the account. The connection is saved once, and every modular365 step of every Zap you build reuses it.
Your first Zap: a modular365 record for each form submission
GoalAdd a record to a modular365 table each time your form receives a submission, only for the submissions that pass the filter you set.
- 01
Build: start on the form
Create a Zap and pick your form tool with its new-submission event as the trigger. modular365 cannot start a Zap, so the starting point always lives in another app.
- 02
Test the trigger on a real entry
Run the trigger test. Zapier brings back the three most recent submissions of the connected account, so the mapping is done on real answers, not on guesses.
- 03
Add a filter (paid plan)
Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value. The Zap becomes multi-step, so it needs a paid plan.
- 04
Add Insert Record
Pick modular365 and the Insert Record action, choose the Table, then map the answers of the submission into the fields that table offers.
- 05
Test, read, then publish
Run each step once and read what came back before going further, on the Insert Record step as much as on the trigger. When it looks right, click Publish to switch the Zap on.
The 3 modular365 actions
modular365 gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Insert Record
ActionIn Zapier“Creates a new record in the selected table.”
Adds a brand-new record to the modular365 table you choose, filled with values coming from the earlier steps of the Zap.
Update Multiple Records
ActionIn Zapier“Updates ALL records matching your filters. Use with caution — this modifies every matching row.”
Changes every record of a table that matches your filters, all in one action. Nothing limits it to one row: if ten records match, ten records change.
Update Record
ActionIn Zapier“Updates exactly one record matching your filters. Fails safely if zero or multiple records match.”
Edits exactly one record, the one your filters point to, in the table you select. If no record or several records match, the step fails rather than picking one.
When a modular365 Zap breaks
Zapier ties no help article to modular365, so the traps below are the general ones, seen from a Zap that writes into a table.
They come from the way Zapier runs a Zap, not from modular365 itself. If one of them is already in your way, see our Zapier troubleshooting guide.
No catch-up on the past
A Zap reacts only to what happens after you switch it on. Entries that already existed never become records, and moving that backlog is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and eats tasks fast.A sudden flood held back
When a trigger returns a huge batch at once, after a bulk import or a migration, Zapier's flood protection can hold those runs back.The same item, one run
On a polling trigger, Zapier remembers what it has already seen, so the same item does not start the Zap twice.
Need help automating modular365 with Zapier?
A person reads every message.
