Payments / Pipelines
We are trying to connect our Quick Base to Quick Books through Pipelines, so that we can receive a payment in Quick Base and it pushes across and reflects in Quick Books. Looking at the Pipeline optio...
Forum Discussion
We had been using Zapier for all our integration needs with Books. But we were notified by Base that our API calls were off the charts and were informed that by using Pipelines it would not impact API calls to the point of having to purchase more. So we decided to start weening off Zapier and switching to Pipelines.
I've only been able to create 2 effective pipelines; one to create customers and one to create invoices. It seems that creating records in Books from new records in Base works very well, but updating them is something that needs to be "fleshed out" also. I had been building a new pipeline to update an invoice and it errored out and blanked out the whole pipeline. I have to start from scratch. But I'm not very eager to attempt that again. At least until they do some fixes.
Not a very productive use of my time. So we are having to stay with Zapier, at least for payments. And updates will need to happen manually.
Thank you,
------------------------------
Barry Dolan
------------------------------
I've only been able to create 2 effective pipelines; one to create customers and one to create invoices. It seems that creating records in Books from new records in Base works very well, but updating them is something that needs to be "fleshed out" also. I had been building a new pipeline to update an invoice and it errored out and blanked out the whole pipeline. I have to start from scratch. But I'm not very eager to attempt that again. At least until they do some fixes.
Not a very productive use of my time. So we are having to stay with Zapier, at least for payments. And updates will need to happen manually.
Thank you,
------------------------------
Barry Dolan
------------------------------
This is an old thread, and you all may have already found a solution since then, but I had the same issue and ran into some issues using Zapier and recently discovered that the "Invoice Updated" trigger works when a payment is received/applied to an invoice. Depending on what you were looking for the received payment trigger to do/carry forward to future steps, I thought this might be helpful info.
For our use case, I mainly wanted some quickbase records updated as paid when an invoice balance was 0, so adding that filter to the "Invoice Updated" trigger to only run if the invoice balance was 0 did the trick.
I tried adding a filter to only run if {{a.balance}} <> {{a.$prev.balance}}, so it would only run specifically when the balance changed to 0, but that logic doesn't seem to be working at this point and it still triggers even when there's a non-numerical update to the invoice and the balance is 0. Thankfully we are a really small company and don't update invoices after they're paid very frequently, so it shouldn't be too much of a step run suck to not have the extra logic barrier.
------------------------------
Stacy
------------------------------
For our use case, I mainly wanted some quickbase records updated as paid when an invoice balance was 0, so adding that filter to the "Invoice Updated" trigger to only run if the invoice balance was 0 did the trick.
I tried adding a filter to only run if {{a.balance}} <> {{a.$prev.balance}}, so it would only run specifically when the balance changed to 0, but that logic doesn't seem to be working at this point and it still triggers even when there's a non-numerical update to the invoice and the balance is 0. Thankfully we are a really small company and don't update invoices after they're paid very frequently, so it shouldn't be too much of a step run suck to not have the extra logic barrier.
------------------------------
Stacy
------------------------------
