Quickbase

We are using some sophisticated integrations where we are looping through record sets and making decisions to execute external processes in other systems.

Project files. Training modules

In development phase with our technology team

It is fairly easy since QB provides good API on operating data layer.

Not all integrations were successful, though hard to determine if this was more a failure on enterprise structure over programming. Unfortunately corporate controlled data harder to integrate into the system

Quick Base give very good facility for integration with multiple platform using pipeline features we can easily integrate more that 15 platform including sales force and Jira. It also gives very smooth integration to connect with this application without any issue. Here recently we have also integrated Microsoft share point with Quickbase for automation process it is working very smoothly and effectively

A lot of times, you want things to happen in other applications when a record is created in Quickbase and vice versa. For example, we have a Prospects list in our app and when someone unsubscribes from our email list, we wanted it to unsubscribe in both MailChimp and Quickbase. Programming knowledge was an important aspect of integrating the two systems using both APIs and custom scripting.

It was not too difficult, we have different levels of integration.

It wasn't terribly deep. Mostly to link projects to calendars and track progress. It was not difficult at all to achieve and actually integrated quite easily.

We reviewed it but we did not go forward. It was doable but we decided to head a different direction. If I had my way I would have went with this option. QuickBase is awesome. Just not right timing for our company.

Fairly straightforward, no major problems encountered. Level of integration was fairly basic, mainly one way import or export.

Microsoft SharePoint
We store company files on a SharePoint site. Using a small amount of javascript and the Sharepoint API we were able to allow seamless file access in the browser directly from QuickBase. The integration was simple to implement.

QuickBooks Desktop and Online
It was a one-way sync of inventory, invoice, sales order, and purchase order data.

Custom Software
Two-way sync of scheduling modifications

Trello
Updating and moving a card when QuickBase data changed. They were all achieved using the QuickBase API which is easy to understand and use.

One of our main challenges with integration was that we were not capable of doing the integration ourselves. So, we had to rely on consultants who were hard to identify. It was challenging to build capacity in this area with so many other things going on day-to-day. Some minor integrations were successful but neither of the ones listed above were.

Personally do not have experience with employee information integration, but as a user find it extremely useful to have access to many aspects of an employee profile in one place. For sanitation processes, it has been useful in collaborating and creating one location to find and review processes, procedures, and results for multiple facilities.

The SFTP and QuickBase integrations were part of the native integrations that QuickBase allows. Those went very well. The interface was clear. I did have trouble with the SFTP location, but that was due to LDAP security from the client. Nothing related to QuickBase. The Zendesk interface was very frustrating. It wouldn't connect, and QuickBase did not respond in a timely manner. I found out later that it wasn't a priority for QuickBase. I ended up failing on this integration and it cost me a client.

The depth of integration was shallow in that it would auto-forward emails from a web client to either Outlook or Gmail based on some rules that we put in place. For example, emails for a certain subject would be forwarded to only certain people.

Once all platforms are ready to receive connections from the outside, the setup from there on is simple to establish. Depending on the issue, a contact of the destination system may be needed, but at the end of the day it is all done via API.

We have been able to accurately track authorizations for our providers' services, assignments to therapists, and hours billed against those authorizations. Some portions are handled manually due to the archaic, inflexible State mainframe systems in place in New Jersey.

We have looked at Integration with Outlook and Slack at the surface level only at this time. Basic integration with both of these solutions is fairly straight forward with Quickbase new integration solution Pipelines. They are quick to learn and relatively easy to use.

Integration via the QuickBase API is super easy. I'm not a developer so I'm not sure I can speak to ease at that end but from my perspective as a power user/admin it's extremely smooth. Platforms like ServiceNow or QuickBooks that are designed to be able to fit into other systems make it very easy; we've also integrated with systems that do not have integrations readily available via scripts we've written to automatically get that data into QuickBase where we need it.

Our company was recently purchased and we have been working to integrate our systems with the new corporate systems. Quickbase's ability to allow us to use pipelines to integrate with Salesforce has been key. It allows us to still function as normal, but report up to corporate through the means and channels that they require.