- Home
- Resources
- Integrations
- mySalesman
mySalesman Zapier integrationAutomate mySalesman with Zapier.
The mySalesman Zapier integration gives you 1 trigger, 0 actions and 0 searches. It picks up each new budget quote from mySalesman and hands it to the tool of your choice, on the free Zapier plan as long as two steps are enough.
Verified Trustpilot reviews · AI, automation & growth agency
What the mySalesman Zapier integration actually does
It is a one-way link. mySalesman is a tool residential construction contractors use to qualify their leads, and Zapier checks it for new budget quotes. Each quote it finds is passed to another app you pick. Nothing travels back: this integration reads from mySalesman and never writes into it.
Everything runs through one operation, New Budget Quote Created, so the results you can get all start from the same event. Three of them stand out. A quote log: every new budget quote becomes a row in a spreadsheet, which gives you a running list outside mySalesman. A heads-up: the quote lands as a message in the chat your team already reads. A record elsewhere: the quote opens an entry in the tool where you follow up on prospects. All three read the same quote; only the second step changes.
What Zapier does not do for this app matters just as much. There is no action, so a Zap cannot create, change or close anything inside mySalesman. There is no search either, so a Zap cannot look up an older quote. And the only trigger is checked on a timer (more on that below), so a quote waits for the next check before anything moves.
To weigh the other two tools for the same job, see our n8n vs Zapier and Make vs Zapier pages.
The Zapier words you will meet
Eight terms, in plain words. They come back on every line of this page.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts the Zap. Here it is a new budget quote in mySalesman, which Zapier waits for once the Zap is on.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- 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, calling Zapier when the event happens. mySalesman has none on Zapier today.
- 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 second action or a filter makes one, and it then needs a paid plan.
What a mySalesman Zap costs
The bill is easy to read here. The trigger costs nothing, however often Zapier checks mySalesman. Only the actions that follow are counted.
- Trigger check0 tasks
- Each action that succeeds1 task
- Action that failsNot counted
- Free plan100 tasks a month, two steps per Zap
One quote sent to one app is one task. Send it to two apps in the same Zap and it costs two. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each capped at two steps. A filter or a second action makes the Zap multi-step, and that needs a paid plan. mySalesman itself is open on the free plan.
The grid below is how often Zapier checks the trigger on each plan.
Connect mySalesman to Zapier
- 01
Open your Apps page
In your Zapier account, open Apps and click + Add connection. A dialog opens with a search box: type mySalesman and pick it from the list of results.
- 02
Sign in and grant access
Click Add connection. A new tab opens on mySalesman: sign in with the account whose budget quotes the Zap should see, then grant Zapier access to that account.
- 03
Check the prerequisites
You need an account on mySalesman, plus read or write access on anything you do not own yourself and want the Zap to touch. Once linked, the connection is reused by every step that calls mySalesman.
Your first Zap: a log of the quotes you care about
GoalEvery new mySalesman budget quote that meets a condition you set ends up as a row in a spreadsheet.
- 01
Pick the trigger
Create a new Zap, choose mySalesman as the app that starts it, then New Budget Quote Created as the event. Select the connection you made, or add it from there.
- 02
Fill in the Start Date and test
Type a Start Date in one of the two accepted formats, then test the trigger. Zapier brings back the three most recent budget quotes, so you map your fields on a real one.
- 03
Add the filter
Add a Filter step from the plus icon, then set the field to look at, the rule and the value. Pick a text rule for text and a number rule for numbers. This step needs a paid plan.
- 04
Add the spreadsheet step
Choose your spreadsheet app and its add-a-row action, then place the quote's values in the right columns. Test this step once and read what came back before going further.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new quote that passes the filter is written to the sheet after Zapier's next check.
The mySalesman trigger
1 event starts a Zap when something happens in mySalesman. Zapier checks for them at the interval your plan allows.
New Budget Quote Created
Polling triggerIn Zapier“Triggers when new budget quotes are created.”
Each budget quote created in mySalesman is picked up on Zapier's next check and starts your Zap, carrying the quote on to the app you chose for the next step.
YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ, nothing else.When a mySalesman Zap goes wrong
Zapier attaches no help article to this app and lists no limit of its own, so what can go wrong comes from how Zapier works in general.
Four cases are worth knowing before you publish. If a run still behaves oddly, see our Zapier troubleshooting guide.
Older quotes are not sent
A Zap only reacts to what happens after you switch it on. Quotes that already existed are not picked up, and moving that backlog is a separate job.A large batch can be held back
If mySalesman suddenly returns a huge batch of quotes, after a bulk import for instance, Zapier's flood protection can hold the run back.The same quote does not run twice
On a polling trigger Zapier remembers what it has already seen, so the same budget quote does not start the Zap a second time.The Start Date format is strict
The required Start Date only takes YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ. Check it in the trigger test before you publish.
Need help automating mySalesman with Zapier?
A person reads every message.



