Current + Kaseya Quote Manager integration
Won Kaseya Quote Manager quotes become Autotask projects with their charges, and the sales order, payments and delivery detail come with them.
Kaseya Quote Manager (formerly Datto Commerce) is Kaseya's quoting and procurement tool, the place a hardware quote is built and then bought: the quote goes out, the partner accepts it online, and a sales order, its payments and the purchase orders behind it follow. Current's integration turns that acceptance into delivery work. A won quote lands in a queue in front of a project manager, a guided wizard builds the project and pushes the charges into Autotask, and the order, the payments and the ship-to details travel with it. Current reads Kaseya Quote Manager and never writes to it.
What the integration does
It is the same Win Quote Engine Current runs for ScalePad Quoter and ConnectWise CPQ, with one addition. Current polls Kaseya Quote Manager every five minutes with a read-only API key, mirrors every quote it finds onto the company record, and puts the won ones into the ready-to-convert queue. Converting one writes a real project, real project charges in Autotask, and moves the Autotask opportunity to the stage you nominated. The addition is procurement: the sales order behind the win, what has been paid on it, the purchase orders raised for it, and a notification when the order is fulfilled.
Autotask stays the source of truth for money
Kaseya Quote Manager's own Autotask integration creates the Opportunity, the Quote and the quote items from an accepted quote. Current reads the amounts, the costs and the line items back from Autotask, which is where billing already lives, rather than trusting a figure it was handed. Kaseya Quote Manager's own line totals come across as well, and they are what the accepted-total check measures a project manager's ticked lines against before anything is billed. Tax sits outside both figures, because an Autotask opportunity amount is stated before tax and the two have to compare like with like.
Autotask workspaces only, and why
A Kaseya Quote Manager quote carries Autotask ids and nothing else: the Opportunity, the Quote and the organization its own integration created. There is no ConnectWise or HaloPSA identifier anywhere in the data, so on a ConnectWise or HaloPSA workspace there would be no way to match a win to an opportunity. The card still appears there, saying what it does and why it is locked, and Connect appears once Autotask is connected.
What flows, and which way
- Quotes, inbound — every quote at any status: drafts, quotes awaiting approval, quotes out with the partner, wins, declines, and quotes that ran past their expiry date.
- Won quotes, inbound — the ones that reach the project manager's queue, matched to the Autotask Opportunity behind them.
- Sales orders, payments and purchase orders, inbound — the order number and status, what has been paid and whether it went on account, on a card or by hand, and how many purchase orders are draft, approved, received or cancelled.
- Delivery details, inbound — the company, contact, phone, address and instruction the order ships to, shown to the project manager before the project is built.
- Project charges, outbound to Autotask — the one-time lines a project manager ticks, pushed as Autotask project charges.
- Opportunity stage, outbound to Autotask — the win moves to the stage you picked under "After Current converts" once the project exists, which is what clears it from the queue. The stage that fills the queue in the first place is the one you picked under "Ready to convert".
Nothing goes the other way into Kaseya Quote Manager. Its API is read-only, so there is no endpoint for Current to write to even by accident.
The part after the yes
A win is where the delivery work starts. A hardware quote becomes a sales order, the order becomes purchase orders, the purchase orders become boxes that arrive, and until they do the project cannot really begin. Current puts that chain on the quote itself: the order and its status, the payments and how they were taken, the purchase orders and how many have been received. When Kaseya Quote Manager marks the order fulfilled after the project was built, the project's lead and whoever ran the conversion are told, and a note lands on the company's timeline.
Polling, because there is no webhook
Kaseya Quote Manager's API carries no webhooks and no events, so Current polls it every five minutes with your own key and works out what changed. A win reaches the queue within a poll cycle, and a missed cycle is caught by the next one, because there is no delivery to drop. The first connect scans a look-back window you set, 30 days by default and anywhere from 1 to 365; it applies on that first connect only, and after it each poll picks up where the last one left off. Kaseya Quote Manager allows 60 API calls a minute and Current stays under that, so a large account works through its backlog over a few cycles rather than all at once.
Unknown reads as unknown
Kaseya Quote Manager reports no currency on a quote, so Current reads the figures as the workspace's own currency and does not raise a mismatch, because an unknown currency is not evidence of one. Current converts no money anywhere. A recurring line is stated per month on its own cadence, quarterly divided by three and yearly by twelve, and a recurring line with no cadence at all is counted as monthly with that fact recorded on the quote rather than hidden. A quote with no sales order yet says so instead of showing a row of zeroes.
Built from the published API, before a live account existed
This connector shipped without a Kaseya Quote Manager account to test against. Connecting runs a short check that records what your own account returned: how many employees the key could see, and whether a sample quote carried the Autotask ids and the sales order id the matching depends on. Two readings are still to be confirmed against a live account: the exact link path into a quote, and how a fixed-value line discount is applied. Everything else is built to fail safe: a quote Current cannot read cleanly is left alone rather than guessed at, a partial read never moves the sync forward, and nothing is ever written back.
Why it matters
The handoff from sales to delivery is where MSPs leak money. Somebody has to notice the win, build the project, remember the hardware and the recurring services, bill the one-time items, and move the opportunity in the PSA. An MSP quoting a firewall refresh for a partner like Northwind Traders can see the accepted quote, the order it became, the two purchase orders behind it and the day the boxes were fulfilled on one screen, then convert it into a scheduled project with the charges already lined up. The quoting stays in Kaseya Quote Manager and the billing stays in Autotask.
Sources
- 1.Kaseya Quote Manager help centre — Kaseya