Quickbase

The ability to automate processes in Pipelines is equivalent to Zapier or Power Automate if you can use the proper connections. Normal benefits that you would receive from process automation are present.

Growth in sales and projects

None of yet

Not applicable

I have used Pipeline as it gives me two way integration i.e from Quickbase to Quickbook online and vice versa. Here recently we have also integrated Microsoft share point with Quickbase for automation process it is working very smoothly and effectively

Wow, pipelines are truly amazing. It is like having Zapier built right in. I was skeptical at first, but after attending a virtual seminar, I was quickly intrigued by all the opportunities Pipelines was opening. With Pipelines, I was able to syncronize Mailchimp list unsubscribes with my Prospects database easily, quickly and with no code.

We were able to log progress on projects, as well as implement processes that we were unable to implement before. These integrations allowed us to be more efficient on our projects from start to finish. They also helped us to be able to set a clear path to follow for the completion of projects.

I was able to integrate QuickBase with UiPath so UiPath bots can write to QuickBase using QuickBase HTTP API Calls from UiPath's HTTP Activity. Even embarked upon a venture to develop a UiPath reusable component that others can use to interact and perform the CRUD operations with QuickBase.

One specific bot that I developed in UiPath, writes day to day posted transactions from Credit Card websites in such a way that in QuickBase the duplicates are automatically never inserted by the bot, even if the bot sees duplicate transactions because it runs daily.

None

Pipelines allows a two-way integration that can be completed directly in QuickBase. Previously you would have to create integrations in both systems for two-way notifications. While it's not quite as code free as they would have you think, it is definitely within the skills of someone who does not generally write code to build a piplines integration. It is a very powerful and intuitive system. It cut down the amount of time for us to build it in half, it cut out the need for us to write a scripts, and it eliminated the need to do any integration work in a third party system.

None -- we were not able to successfully integrate using QB pipeline. Unfortunately, integration proved too time consuming given our limited resources. Pipelines seems to resolve the problem we previously had but since we weren't aware of it previously, we have since moved on. May need further education on its capabilities.

Unfortunately do not have any experience with using QuickBase pipeline integrations.

The looping process and ability to reorganize the sequence were very helpful. However, I didn't like the charging of each API call for each run. With webhooks or automations you don't have this same issue if you are running through a batch of data. I do like the visual design of the interface.

Doing this integration eliminated some overhead admin work which we would do manually before we started using QuickBase. The rules were easy to setup but they were not easy to test. In other words, sometimes we would be suspicious that we might not be receiving certain emails and only after contacting our IT would they be able to figure out the problem, which is usually because they didn't setup a rule correctly, or certain characters in email subjects or bodies would make the system hang and not follow the rule.

The connection to Service now has allowed users across the country without access to service now to be able to submit help tickets via quickbase. When the ticket is submitted it will then be imported into Service now to be handled like any other ticket and we didnt need to add an exception to the firewall.

We have not been able to utilize Pipelines due to the outdated architecture utilized by the State of NJ systems.

Easy notifications in a Slack channel of new entries into a Quickbase application.

We have not yet used Pipelines.

I have not yet actually used Pipelines to connect with other non QuickBase Apps but I have a couple of clients who want to be able to create Quick Books invoices based on data in Quick Base. i know that I will use Pipelines do do this integration and based on postings in the QuickBase Community Forum, i know that it is doable and also i will be able to get assistance from Quick Base support if I get stuck.

With Service Now, and Salesforce, the integration becomes seamless with the new Pipelines feature and establishing the connection was real quick. The Pipelines has provided many capabilities to Quick Base in integrating with other platforms seamlessly. Looking forward for the on-premise integration support with the new ODBC based connector with on-prem agent installed within the firewall boundaries

The integration between Quickbooks and Quickbase has been something that we have been working on. Capturing payment information as well as customer information has been rather seamless. And Quickbase has been there to help us every step of the way, providing support for when do get stuck and getting us out of a pickle. Quickbase has also been helping to capture employee time and importing for payroll is a future step that I know that Quickbase has the capability to do. Quickbase can do quite a lot with Quickbooks.

Increased work efficiency and time saved in integrating the two softwares. It was tremendously worth it integrating the two systems.