Step 2 of 4 · About your integration

What should your first version do?

Answer what you can. Where you’re not sure, say so: we’ll pick something sensible and explain the choice in your walkthrough.

Your company
Your stack

So the code we write for your app’s side fits it.

HTTP library is optional. Leave it blank and we’ll use what your framework usually does.

Which way should records go?
Which records?

Pick all that apply. QuickBooks Desktop has more; tell us under Others if yours isn’t here.

When should it happen?
How should we find a customer who’s already in QuickBooks?
Your data models optional

With your app’s models, the code we write reads and saves your own fields instead of guessing their names. Your coding agent can write them from your codebase: copy this prompt into it, then paste or attach what it answers.

Prompt for your coding agent 
Write this codebase’s data models as JSON Schema, so another team can build our QuickBooks Desktop integration against them. Answer with one ```json block and nothing else: `$defs` with an entry per model a QuickBooks integration would read or write (customers, invoices, items, payments, whichever we have), keyed by its class name, with every field (its type, whether it can be null, its `enum` when it has a fixed set of values) and each association as a `$ref` to the other model, or an array of them for a has-many. Generate it from the schema file or the models, don’t write it by hand, and describe the shape only: no real records, no `examples` or `default` values.
Or JSON, up to 200 KB
Anything else we should know? optional
Back