No longer needed. I have this solved. Not sure how to remove this post.
Looking for help in automating a work process involving Katana MRP and QBO. The basic scenario is built but not working at the moment.
3 Likes
Hi @Jacob_Florine, Welcome to the make community! I can definitely help you get that Katana MRP and QBO scenario working.
Feel free to check out my past work and portfolios over on my Upwork profile (https://www.upwork.com/freelancers/pathfinderautomate), or if you’d rather talk it through first, you can book a call on my Calendly (Calendly). You’re also welcome to reach out directly by email at [email protected], and take a look at my website Website for more on what I do.
Looking forward to hearing from you
Taiwo
Hello Jacob, I saw your post and wanted to reach out. I help businesses build and troubleshoot automations, AI systems, CRM workflows, API integrations, and operational processes, so this looks like something I may be able to help with.
Website: https://philip-adeniji-portfolio.philipade.workers.dev
Fiverr: https://www.fiverr.com/s/odqEEVN
Calendly: Calendly - Adeniji Philip
Feel free to share more details of what you’re trying to accomplish, or grab a time on my calendar and we can walk through it together.
Hi Jacob,
Which record should move from Katana into QuickBooks Online, and at which module does the existing scenario stop? A redacted error message and the expected result would help distinguish a mapping problem from an authorization or business-rule error.
I can offer a first paid diagnostic for USD 75 fixed, delivered within two business days after we agree the sample, scope and start date. One scenario, one failing path: review the redacted blueprint and one sanitized run, identify the failure, and return the smallest proposed correction with a test plan. I would confirm that the supplied sample is sufficient before accepting; live accounting changes and a full rebuild are outside this first step.
For accounting records I would also check how the source record is matched to an existing QBO record before retrying, so a retry does not blindly create another transaction. I have not deployed this exact Katana–QBO combination for a client, and would not claim that experience. My implementation work is AI-assisted with human oversight.
If that scope fits, please reply with the record type, the failing module/error (without tokens or customer details), and whether the USD 75 diagnostic fits your budget. No credentials or live financial data in the public thread, please.
Hi Jacob, is this still open? I can review the existing Make scenario as a small paid diagnosis before proposing a repair. Which Katana record should create or update which QBO record, and where does the scenario currently fail? A redacted blueprint, sanitized run, error text, and expected result would let me confirm scope and a fixed price. I work remotely from Seoul in written English. Please also share your budget and whether AI-assisted troubleshooting is acceptable with credentials and customer data excluded.
Hi Jacob, welcome to the forum.
Without the error text nobody can tell you which one it is, but Katana into QuickBooks tends to break in the same three places, and you can check all three yourself in about ten minutes.
First, references. A QuickBooks invoice does not take a customer name or a SKU. The customer reference, and the item reference on every line, want QuickBooks internal record ids. Katana hands you a name and a SKU, so if those go straight across, the create either fails or comes back saying nothing was found. The shape that works is to search QuickBooks first, create the customer or the item only when the search comes back empty, then pass along the id that comes back.
Second, and this one hides behind the first. QuickBooks will not allow the same display name across customers, vendors and employees. So you search customers, find nothing, try to create, and get a 6240 duplicate name error because that company already exists in the file as a vendor. If your Katana customers are sometimes also suppliers, that is a likely cause.
Third, the lines. Sales order rows arrive from Katana as an array. If you iterate them and create the invoice inside the loop, you get one invoice per row rather than one invoice with several lines. Those rows need aggregating back into a single bundle before the create runs.
One question before any of that. Katana has its own QuickBooks Online integration that turns sales orders into invoices and purchase orders into bills, and syncs contacts. If that is switched on and you are also building the same path in Make, you will get duplicates. So what is the Make scenario meant to do that the native integration does not?
Post the module it stops on and what the error actually says, with ids and customer details taken out, and I will tell you what it is. If it turns out to be a rebuild rather than a fix, we can talk about that then.
Cindy Garcia
Advanced AI Automation
Hi Jacob — since the basic scenario already exists, I’d avoid rebuilding anything until the first failing path is reproducible.
Could you share, with any private/accounting data removed:
-
which Katana record/event should trigger the workflow,
-
what it should create or update in QuickBooks Online,
-
the first Make module where the result becomes wrong or stops, and
-
one expected-vs-actual example or redacted error?
I’d start by tracing just that one path and checking the mapping, state/retry behavior, and whether a rerun could accidentally create a duplicate QBO transaction.
My strongest hands-on automation work is n8n/API/webhook/data-flow reliability, including duplicate prevention, state branching, exception handling, Human Approval, QA and regression checks in CLEAR MERIT’s Internal / Working Demo Revenue OS. I haven’t deployed this exact Katana → QBO combination for a client, so I don’t want to overstate that.
If the issue is reproducible from a redacted scenario/export, I’m open to starting with one small fixed-scope paid diagnostic/fix rather than committing you to a rebuild.
No credentials or live financial data needed in the public thread.
Hi @Jacob_Florine — I can review one failing path in your existing Katana → QuickBooks Online Make scenario. For USD 75 fixed, I’d examine one redacted blueprint and one failed run, then deliver the likely failure point, smallest proposed correction, and a safe retest checklist within two business days after receiving sufficient materials. This excludes production changes and a full rebuild.
Which Katana record should create or update which QBO record, and where does the scenario fail? Please remove credentials and customer financial data from anything you share. My analysis is AI-assisted; I haven’t deployed this exact integration for a client. We’d agree on payment timing before starting.
Hi Jacob,
I’m Mikael, founder of Shinka AI. Since the scenario already exists, I would treat this as a focused repair rather than a rebuild: trace one reproducible Katana → QuickBooks path, correct the failing mapping/authentication/business rule, test the outcome with sanitized data, and add a basic error and duplicate check.
To scope it properly, could you share:
- the Katana record or event that should trigger it;
- the QBO record it should create or update;
- the first Make module where it stops or becomes incorrect; and
- one expected-versus-actual result or redacted error.
Once that path is clear, I can propose a fixed-price repair with specific acceptance checks. Please do not post credentials or live accounting data here.
Mikael Jacob
Shinka AI
Hi Jacob,
Since the scenario already exists but does not work, the fastest path is to find the actual failing step instead of rebuilding it: I would look at the last failed run, check which module errors, and inspect the data leaving the previous module. With Katana and QBO the usual culprits are the item or account identifiers not matching between the two systems, a field type that QBO rejects (dates and tax codes are the classic ones), or a connection that expired silently.
I build and debug Make and n8n flows as my daily work — my Snajper Ofert pipeline runs in production, receives data from several APIs, deduplicates it and keeps a log of every failed call, which is the same discipline your Katana scenario needs: JNX.Automation — automatyzacja procesów, integracje API i AI | Jan Noga
Two questions: which direction matters first — Katana into QBO (stock, purchase orders, bills) or the reverse — and can you share a screenshot of the failing module with the error message? A repair like this, ending with the scenario running correctly and a short note on what was wrong, is 100 USD, usually within 2 days. The estimate is indicative; we will fine-tune it once the details are confirmed.
Jan Noga
jnxautomation.pl
Hi Jacob,
Katana to QuickBooks is one of those integrations that looks straightforward until you hit QBO’s API and realise it has opinions about everything - account IDs, tax codes, customer references, you name it.
A few things I would check first before touching anything:
- Whether your QBO OAuth token has expired or needs reauthorisation
- How Katana is sending the data in the webhook payload and whether the field names match what QBO expects
- Whether you are writing to a sandbox first or straight to live data
That last one matters a lot. QBO can create duplicate invoices silently if the error handling is not right and cleaning those up is painful.
If you can share a screenshot of your scenario with the modules visible and one failed run from your History tab, I can tell you within a few hours what is going wrong and give you a fixed price to sort it. Usually something like this lands between $250 and $400 depending on how much custom logic is needed.
What error are you actually seeing when it runs? Red module, wrong data coming through, or is it just silently not doing anything?
George
norvane.uk
Hi Jacob, glad you got it sorted.
For future Make issues involving Katana or QuickBooks Online, feel free to reach out. I work mainly with Make, APIs and webhook-based integrations, and I’m also happy to troubleshoot existing scenarios rather than rebuild them from scratch.