Bonsai Zapier integrationAutomate Bonsai with Zapier.
The Bonsai Zapier integration gives you 10 triggers and 5 actions, with no search step. Every trigger is instant, so a signed contract or a paid invoice starts your Zap right away, even on the free plan, and every action creates something new in Bonsai.
Verified Trustpilot reviews · AI, automation & growth agency
What the Bonsai Zapier integration is for
The Bonsai Zapier integration connects Bonsai, the business management platform agencies and service firms use to run client work, to Zapier, the tool that automates work between apps. Bonsai tells Zapier when a client acts (signs, views, pays, books), and Zapier creates the client, deal, project or task that follows.
Picture a small design studio. First result: a project that sets itself up the moment a client says yes. Proposal Accepted starts the Zap, Create Project opens the project, and Create Task adds the kickoff. Second: a sales pipeline fed by your forms. Form Submitted catches a new inquiry and Create Client records the lead. Third: billing that closes the loop. Invoice Paid starts a Zap that creates the wrap-up task for whoever handles delivery.
Here is what Zapier does not do with Bonsai. All five actions create; none of them updates a deal, edits a task or sends an invoice. There is no search step, so a Zap cannot look up an existing client or project first. Anything that only exists in Bonsai's interface stays there.
The good news sits on the trigger side: all ten are instant, so the plan you pay for does not slow them down. Before choosing a tool, the Make vs Zapier and n8n vs Zapier comparisons help.
Zapier words you will meet on this page
Seven terms come back everywhere below. Here they are in plain English.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The Bonsai event that starts the Zap, like a proposal accepted or an invoice paid. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that creates a client, a deal, a project or a task in Bonsai for you.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts nothing else.
- Instant vs polling
- Instant: the app calls Zapier the moment the event happens. Polling: Zapier checks on a timer. Every Bonsai trigger is instant.
- Filter
- A step that lets the Zap carry on only when what arrived matches your condition, and stops it 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 Bonsai Zap really costs
Bonsai is not a premium app, so it works on the free plan. Zapier only bills actions that go through, and because all Bonsai triggers are instant, the polling grid below does not slow them down.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on Free2 steps: one trigger, one action
- Bonsai triggersAll instant, no waiting
- Premium appNo, Bonsai works on Free
The trigger never costs a task. Each action that succeeds counts once, so a Zap that creates a project and then a task uses two tasks per run, and a failed action is not counted. The free plan stops at two steps: one trigger, one action. A second action or a filter makes the Zap multi-step, which needs a paid plan. The interval grid only concerns polling triggers, and Bonsai has none, so the plan you pick changes your volume, not your speed.
Connect your Bonsai account to Zapier
- 01
Go to Apps
In Zapier, open Apps and click + Add connection. A connection is your Bonsai account linked once, then reused by every Bonsai step in every Zap you build.
- 02
Find Bonsai
Search for Bonsai in the dialog, pick it, then click Add connection. You need an active Bonsai account of your own before this works, with the clients and projects the Zap will use.
- 03
Log in and allow access
Sign in to Bonsai in the new tab and grant Zapier access. Anything you do not own yourself, such as a teammate's project, needs read or write access for your account.
Your first Zap: from accepted proposal to ready project
GoalWhen a client accepts a proposal in Bonsai, Zapier creates the project, then adds a kickoff task for whoever leads delivery.
- 01
Set the trigger
Under Build, pick Bonsai and the event Proposal Accepted, then your Bonsai connection. The lightning bolt shows the trigger is instant.
- 02
Test with a real proposal
Click Test. Zapier brings back the three most recent accepted proposals of the account, so you can map the next steps on a real one.
- 03
Add Create Project
Add Bonsai with Create Project. Fill Project Name, Client Email and Currency, written as an ISO 4217 code such as USD or EUR.
- 04
Add the kickoff task
Add Create Task with a Task Title. The Zap now has two actions, so it is multi-step: on the free plan, keep only the project.
- 05
Test and publish
Test each action, check the result in Bonsai, then click Publish. The next accepted proposal starts the Zap straight away.
Bonsai triggers: what starts a Zap
10 events start a Zap when something happens in Bonsai, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.
Contract Signed
Instant triggerIn Zapier“Triggers when a contract is signed by your contact (client or contractor).”
Fires when your contact, a client or a contractor, signs a contract in Bonsai. That signature is often the real start of the job, and this trigger turns it into a signal other steps can use.
Contract Viewed
Instant triggerIn Zapier“Triggers when a contract is viewed.”
Lets you know a contract has been opened, before anyone has signed. It sits one step earlier than Contract Signed in the life of an agreement, so it suits follow-up rather than delivery.
Deal Updated
Instant triggerIn Zapier“Triggers when a deal is updated in Bonsai.”
Follows your pipeline: when a deal changes in Bonsai, the Zap gets it. This is the trigger for sales teams that live in the deal view rather than in proposals.
Form Submitted
Instant triggerIn Zapier“Triggers when a new form response is submitted.”
Catches every new response to a Bonsai form, the entry point for inquiries and briefs sent by prospects. It is the natural starting line for a lead flow.
Invoice Paid
Instant triggerIn Zapier“Triggers when an invoice is paid.”
Reports the moment money lands: an invoice marked paid in Bonsai starts the Zap. It is the cleanest signal you have that a piece of work is settled on the client side.
Invoice Viewed
Instant triggerIn Zapier“Triggers when an invoice is viewed by the client.”
Fires when the client opens an invoice, which tells you it reached the right inbox. Paired with Invoice Paid, it lets you see the gap between reading and paying.
Event Scheduled
Instant triggerIn Zapier“Triggers when a new event is booked via Scheduling”
Reacts when someone books a slot through Bonsai's scheduling feature. In the editor you will find it under the name Event Scheduled.
Proposal Accepted
Instant triggerIn Zapier“Triggers when a proposal is accepted by the client.”
The clearest go signal an agency gets: the client accepts a proposal, and the Zap starts. Everything that comes after, from project to kickoff, can hang on it.
Proposal Viewed
Instant triggerIn Zapier“Triggers when a proposal is viewed by the client.”
A proposal opened by the client, before any decision, is what this one reports. It gives the sales side a precise moment to step in.
Task Updated
Instant triggerIn Zapier“Triggers when a task is updated in Bonsai.”
Watches your tasks: when one changes in Bonsai, the Zap starts. It is the trigger for teams that track delivery inside Bonsai rather than in another tool.
Bonsai actions: what a Zap can create
Bonsai gives you 5 actions. 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“Creates a client lead on Bonsai”
Adds a client lead to Bonsai from whatever started the Zap.
Create Deal
ActionIn Zapier“Creates a new deal in Bonsai”
Opens a new deal in your Bonsai pipeline, tied to a client by email.
Create Project
ActionIn Zapier“Creates a project”
Sets up a project in Bonsai, with its name, client and currency.
Create Task
ActionIn Zapier“Creates a new task in Bonsai”
Creates a single task in Bonsai, the lightest action of the set.
Create Tasks From Template
ActionIn Zapier“Adds tasks from a task template in Bonsai”
Adds a whole set of tasks to a project from one of your Bonsai task templates.
When a Bonsai Zap breaks
Zapier attaches no help article to Bonsai and lists no limit of its own for it. The failures to plan for are the ones every Zap shares, plus the required fields of Bonsai's actions.
Four cases are worth knowing before you publish, each with a simple way out. For anything else, see Zapier troubleshooting.
Past proposals and invoices are ignored
A Zap only reacts to what happens after it is published. Contracts signed or invoices paid earlier are not picked up; moving that history is a separate job.The Zap feeds itself
A Zap that writes into the very place its own trigger watches sets itself off again and again, and burns through your task count fast. Point actions elsewhere.A bulk import gets held back
When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold the run back rather than fire on all of it.The second action never runs on Free
The free plan builds two-step Zaps only. A project plus a task, or a filter in front of an action, needs a paid plan before you can publish it.
Need help automating Bonsai with Zapier?
A person reads every message.



