What are Native Integrations?
As the SaaS technology market continues to evolve, consumers are expecting their applications to be able to talk to each other in increasingly complex ways. Downloading and uploading spreadsheets to transfer data between applications is no longer an acceptable onboarding experience. With competition for SaaS tools at an all-time high, prospects continually choose products that communicate and integrate with their existing tooling the best.
For these reasons, it’s no surprise that a new movement in the integrations space is taking hold: the move toward native integrations. But what are native integrations and how are they different from existing integration solutions? In this article, we’ll dive into this question to help you understand what native integrations are and why they’re so powerful.
What Is An Integration?
Before we dive into the nuances of native integrations, let’s take a step back and try to build a more fundamental understanding of what an integration is. If you have a technical background and are already familiar with APIs and integrations, you can feel free to skip this section.
We call two SaaS systems integrated when they have some way to automatically pass information between them over the internet. Put another way, we’d call application A integrated with application B if there was a way for me to move data from one system to another without needing to download and upload a spreadsheet or enter information manually.
Most integrations happen through something called an Application Programming Interface or API. An API is really just a way for two computers to talk to each other and ask questions in a programmatic way (e.g., by using code!). If one of those computers is the computer that application A is running on and the other is the computer that application B is running on, then those two applications are integrated!
Here’s an example: let’s say that your company supports a Salesforce integration that allows your user to see their Salesforce Contacts in your product.
Here’s what’s roughly happening under the hood when your user tries to view their Contacts in your product. The arrows in the diagram below represent API calls and responses.
Nowadays, integrations can happen through a variety of methods, not just the way shown above. Salesforce, for instance, actually lets your developers write a little bit of code that will run on Salesforce’s computers and lets you show a part of your application inside of Salesforce.
Get Vessel’s stories in your inbox
Join Medium for free to get updates from this writer.
However, API integrations are still by far the most popular and are what any of the integration platforms you’ve heard of support. When you hear the term integration throughout this article, you can assume we mean “two systems using a secure API to pass data back and forth”.
What is a native integration?
A native integration is an integration that’s built directly into your product without going through a 3rd party platform. Put another way, a native integration is just an API integration that your developers implement directly in-code in your product.
What are the Pros of native integrations?
There’s a few very key reasons to build native integrations:
- Deeper integrations: Fundamentally, you can build much deeper integrations when you’re working with native integrations. Since you can work directly with the API of the downstream integration, you aren’t blocked on a 3rd party provider’s functionality or feature set.
- Better UX: You’ll have better control over the user experience. Most 3rd party integration providers force you to use their authentication UI meaning you have little control over how your user connects their SaaS tool. In extreme cases like Zapier, your user even has to make an account in Zapier to use an integration in your product. By building natively, you can have complete control over how your user connects.
- Build what you need: If a 3rd party integration provider doesn’t have the integration you need, you’re often blocked until they add the integration (which may be never). This results in your developers needing to set up the infrastructure to build native integrations anyway.
What are the Cons of native integrations?
But native integrations aren’t all roses and sunshine. Native integrations are hard to build, for a variety of reasons:
- Hard to scale: Integrations are extremely varied and no two integrations can be built the same way meaning it can take a while to build a net new native integration.
- Lots of Bureaucracy: Getting access to a company’s API can be difficult. Some companies like Outreach and Salesloft require that you go through an approval process. This usually means you need to meet with someone on their team and fill out a lengthy application which can take weeks to months.
- Hard to maintain: Since each native integration’s API can change over time as they release new features and bug fixes, adding new native integrations can greatly increase the maintenance burden on your developers. I’ve heard stories of companies having multiple developers on staff whose sole job is to keep their Salesforce integration running.
If you’re curious, we explore this in much more depth in our article on why building native integrations is difficult.
Should I build native integrations?
While building native integrations can be difficult, the benefits often outweigh the costs. More and more companies are choosing to build native integrations for a variety of reasons including:
- Building native integrations means you can build deeper integrations which helps keep your product competitive and your customers happy.
- Building native integrations means you always have access to the best APIs provided by the downstream integration and are never blocked on adding new features.
- Building native integrations lets you keep a tighter pulse on how your customers are using your product in the context of their other tools.
Read our last article for more information on why native integrations matter.
As an aside, Vessel is a platform that helps you build native integrations. We remove the typical headaches associated with building and maintaining native integrations by providing all the scaffolding and infrastructure (like pre-approved OAuth apps) you need to build native integrations. We’re a developer-first platform and we don’t limit what you can do with the downstream integration meaning you can build significantly deeper integrations than if you use other solutions.
If you’re interested in learning more, or just want to chat about anything integration related — don’t hesitate to reach out at zach@vessel.dev
