CRM & Sales · Integration
Dubsado
Add Dubsado to your product for your customers, and give your AI agents governed access to it.
Dubsado is the studio management tool a great many independent businesses run their entire client relationship through, from lead capture form to contract to invoice, and the honest description of its integration surface is that it is event-shaped rather than a general API. There is no open REST endpoint set and no OAuth flow. What a customer has is a key generated inside their own account, a defined list of triggers and a small number of actions, and building to that shape works well as long as nobody pretends otherwise. The triggers are the valuable half: a project created as a lead, a project created as a job, a signed contract, a payment on an invoice, and a status change on a project. The action is creating a project, with the client details and the workflow it should enter. That is enough to start work in Dubsado from your product and to react when a client moves, and it is not enough to treat Dubsado as a queryable system of record.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each business connect their own Dubsado account with a key they generate themselves, so nothing runs through a shared credential.
Create a project with its client and the workflow it should enter, so onboarding starts the moment your product says it should.
React to a signed contract by unlocking whatever your product gates behind one, rather than waiting for somebody to notice.
Take payment received and status changed events, so your product's view of an engagement is never a day behind theirs.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent opens a project in Dubsado once a lead qualifies, with the client it was created for recorded.
An agent reports which engagements had a contract signed this week and what should happen next on each.
An agent notices a project status change and starts the follow-up your workflow defines.
Example prompt
Which clients signed a contract this week, and has a first payment come in for any of them?
Set up Dubsado in 4 steps
- 01Enable the Dubsado connector in your fastn dashboard.
- 02Have each business generate a key inside their own Dubsado account, so nothing runs through a shared credential.
- 03Decide which triggers your product listens for and which workflow a project you create should enter.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Dubsado integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dubsado integration without building it. Your customers connect their own Dubsado account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Dubsado update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dubsado connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
HoneyBook
KeapWorks well with
Acuity SchedulingOften used alongside
Tools the same teams tend to run next to Dubsado, across other categories.
Slack
Mailchimp
Marketo
Google AdsDubsado integration FAQ
How do I add a Dubsado integration to my product?
Enable the Dubsado connector in your fastn dashboard, then let each customer authenticate their own Dubsado account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dubsado client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dubsado account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dubsado account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Dubsado integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent opens a project in Dubsado once a lead qualifies, with the client it was created for recorded.
Who maintains the Dubsado integration?
fastn does. When Dubsado changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Dubsado integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Dubsado schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Dubsado, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Dubsado do not drift apart.
What can I build with the Dubsado integration?
A common starting point: let each business connect their own Dubsado account with a key they generate themselves, so nothing runs through a shared credential. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Dubsado integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dubsado does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dubsado to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.