Kloudless Blog

Kloudless Unified APIs enable you to code once and integrate many

The first official Kloudless webinar has come and gone, and we’re so thankful to all of you that turned out to learn about the different industry use cases that can benefit from Unified cloud storage APIs. If you didn’t get a chance to make it to the live session, please click here to watch the webinar in its entirety. What follows is a breakdown of what was covered during the webinar, as well as some answers to the questions we received.

Today’s web apps need to integrate with multiple storage services and provide a consistent user experience and workflow to increase stickiness. You need to build native integrations as quickly as possible, but your developers should not have to become API and integration experts for each storage service. Our Unified APIs allow you to launch new integrations quickly and allow your developers to focus on building beautiful products, not maintenance and troubleshooting.

In this webinar, we walked through several detailed use cases for cloud storage integrations covering workflow simplification, integration with multiple apps in the same UI, and activity monitoring. Some topics included:

  • Why integration should be your product’s differentiator.
  • Pros and cons for implementing native integrations into your app directly.
  • How to embed and customize our open-source file picker into your product.
  • How to create a workflow to integrate multiple file storage options into your app quickly, including Dropbox, Google, Box, and AWS repositories.

We received some great questions during the webinar. Here are the three that were addressed during the webinar:

QuestionFor the data security use case, in addition to the Activity Monitoring functionality that you provide, do you also provide the functionality to take further action and remediate? 

Answer: Yes, and that’s because we provide read/write functionality to the APIs. If something is determined to be a security risk, our APIs easily allow you to rectify the situation. For example, if you detect a change to a file and determine that an SSN has been added to it, you can use the Kloudless APIs to pull that file into your app, make the necessary changes, and put it back in place.

QuestionDo you have one unified data model for everything? I.e. cloud storage and CRM have one data model?

Answer: Some solutions in the market do this, but for our use case, it didn’t make any sense to design the data models this way. No, we have separate data models for each category. We realized when designing our APIs that it doesn’t make sense to have one universal data model, because, for example, sales leads, accounts, opportunities in CRM don’t exist in Cloud Storage. When you amalgamate all of the categories into a single data model, you wind up with a lot of null values that just clutter up the object.

Question: In the use case for Salesforce that you pointed out, we know there are often custom objects. How do you handle that in your CRM data model?

Answer: Great question. Our unified data model contains a raw field that returns custom objects in their original format, which eliminates the possibility of leaving out pertinent data. So taking Salesforce as the example, when making a request through our API, you’ll see core CRM concepts like Accounts, Contacts, Leads, Opportunities, and Tasks returned in a unified format, but custom objects specific to Salesforce like a Billing address or a tenant-specific serial number will be returned in the raw field in its original format. This ensures that you’re able to get a data-complete experience through our CRM API.

We look forward to seeing all of you at the next webinar. Until then, view this webinar in its entirety by clicking here.


Share this article:

Let’s get started. Start building for free today.