Monax Zapier integrationAutomate Monax with Zapier.
The Monax Zapier integration gives you 2 triggers, 4 actions and 2 searches. Both triggers are instant, so an agreement moving in Monax can start a Zap straight away, and the actions draft agreements, attach files, add terms and close obligations for you.
Verified Trustpilot reviews · AI, automation & growth agency
What the Monax Zapier integration does for you
Connecting Monax to Zapier lets your digital contracts talk to the rest of your tools. An agreement changes in Monax and another app reacts, or something happens elsewhere and Monax drafts an agreement, files a document or ticks off an obligation. Monax is not a premium app, so it works from the free plan up.
A new agreement, drafted from a template. Create an Agreement From a Template starts an agreement from a template you already keep in Monax. A form entry or a new spreadsheet row is enough to set it going, and nobody opens Monax to copy the details across.
An agreement that grows on its own. Add Document to Agreement uploads a file as a new document of an existing agreement, and Add Terms to Agreement adds extra terms as structured fields, with a choice on whether every party can see them.
Obligations that close themselves. Complete Obligation on an Agreement marks an obligation as done once another app says the work is finished, and Find an Obligation fetches the Obligation ID it asks for.
What the app page leaves out. Both Monax triggers are instant, so Zapier's polling interval never slows them down, even on the free plan. On the other hand, there is no action to delete or edit an agreement, and nothing to create a template: templates are prepared in Monax beforehand. If you are still sizing up Zapier itself, see our Zapier review.
Zapier in one minute
Eight words carry the page. Here they are, in plain 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. Once the Zap is on, Zapier waits for it, here an agreement event or status in Monax.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like adding terms to an agreement.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling or instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by its app the moment the event happens, like both Monax ones.
- Filter
- A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists, such as an agreement, so the steps after it can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
What a Monax Zap really costs
Zapier bills completed actions and nothing else. A Monax trigger firing costs no task.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, unlimited two-step Zaps
- BilledEach successful action, never the trigger
- Monax triggers2, both instant
Each action that goes through counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to one trigger and one action. A search step or a filter makes the Zap multi-step, so a Zap that finds an obligation before completing it needs a paid plan. The grid below sets how often Zapier checks a polling trigger; it does not apply to the two Monax triggers, which are instant.
Connect your Monax account in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Monax account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Monax
Type Monax in the search box of the dialog, select it in the results, then click Add connection. A new tab opens so you can sign in on the Monax side.
- 03
Sign in and allow access
Sign in to Monax in that tab and let Zapier reach the account. The connection is saved once and offered again in every step and every Zap that uses Monax.
Your first Zap: an agreement event that becomes a task
GoalWhen an obligation is initiated on a Monax agreement, a filter keeps the events you care about and a task lands in your task tool.
- 01
Set the trigger
Create a Zap and pick Monax with An Agreement Event Has Occurred. Choose your Monax connection, then test: Zapier brings back the three most recent events so you work on a real one.
- 02
Add a filter
Click the plus icon and add Filter. Set the field to look at, the rule and the value to compare with. A filter makes the Zap multi-step, so this one needs a paid plan.
- 03
Create the task
Add your task tool as the action and map into the task the agreement details the trigger brought back at the test, and read each value before you rely on it.
- 04
Test each step
Run every step once and read what came back. If the filter stops the sample event, check that its rule type matches the field: a text rule only works on text.
- 05
Publish
Publish the Zap to switch it on. Only events that happen from that moment create tasks; obligations initiated before stay untouched.
The 2 Monax triggers
2 events start a Zap when something happens in Monax, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
An Agreement Event Has Occurred
Instant triggerIn Zapier“Triggers when an agreement obligation or notification has been initiated.”
Starts your Zap when an obligation or a notification is initiated on one of your Monax agreements. It is the broader of the two triggers: obligations and notifications both wake the Zap, and the next steps decide what to do with them.
An Agreement Has Status
Instant triggerIn Zapier“Triggers when an agreement or agreement draft has a specific status.”
Wakes the Zap up when an agreement, or an agreement draft, reaches the status you chose in the trigger settings. Zapier puts it forward on the Monax page, and it is the tidy option when one particular stage of the contract lifecycle matters.
The 4 Monax actions
Monax gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Document to Agreement
ActionIn Zapier“Upload a file as a new document for an agreement.”
Uploads a file and attaches it as a new document to an agreement that already exists, so the file sits with the contract it belongs to instead of in a separate folder.
Add Terms to Agreement
ActionIn Zapier“Add additional terms as structured fields to the agreement.”
Adds further terms to an agreement as structured fields, rather than burying them in free text.
Complete Obligation on an Agreement
ActionIn Zapier“Complete an obligation of an agreement.”
Marks one obligation of an agreement as completed, one of the two actions Zapier highlights for Monax.
Create an Agreement From a Template
ActionIn Zapier“Create a new agreement based on a pre-existing template.”
Drafts a new agreement in Monax based on a template you set up there earlier, filled with data from the earlier steps.
The 2 Monax searches
2 search steps look for data that already exists in Monax, so a later step can use it.
A search step finds an agreement or an obligation that already exists in Monax and hands its details to the steps after it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not a single clean match.
Find an Agreement
SearchIn Zapier“Search for an in-progress, active, or completed agreement by name or ID.”
Looks up an agreement by its name or ID, whether it is in progress, active or completed, and passes its details on.
Find an Obligation
SearchIn Zapier“Search for a an obligation by name.”
Finds an obligation inside a given agreement from its name, or from part of its name, and returns it for the following steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create. Monax exposes no find-or-create variant, so its two searches only find.
- 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 a Monax Zap breaks
Zapier links no help article to Monax, so the traps below are the general ones that apply to any Zap built on it.
Instant triggers remove the waiting, not the classic mistakes. If a run fails and you need to read why, see our Zapier troubleshooting page.
Agreements from before the Zap are ignored
A Zap only reacts to what happens after you switch it on. Agreements that already had their status or events are not picked up, and moving that backlog 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 tasks. Keep the actions away from what the trigger listens to.A sudden flood is 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.A search that finds nothing stops the run
With its default setting, a Find an Agreement or Find an Obligation step that comes back empty stops the Zap, and the steps after it are skipped.
Need help automating Monax with Zapier?
A person reads every message.
