So you want to build your own connector.

This week we announced custom connector capabilities for FLOs. Now, customers are able to build their own user-friendly connectors for their internal microservices, external APIs, and niche cloud applications so they can be continually be reused throughout their organization.

Today, we will walk you through an example of one of these custom connectors and provide information about connector creation so that you can start connecting anything to Azuqua right away.

Why Use Custom Connectors?

Before you delve into the world of custom connector building, it’s important to make sure that a custom connector is actually going to be the right fit for your organization. Sometimes, it’s much more appropriate to simply use the HTTP functions inside Azuqua instead of going through the custom connector process.

Times when building a custom connector makes sense:

  • The service is heavily used by different individuals. By investing the upfront time in building the service into Azuqua as a connector, subsequent uses of it are incredibly easy and fast for everyone without requiring extensive documentation.
  • Non-technical teams need to use the service. Building a connector on Azuqua to that service means that any team member (with the right permissions) can now use that service without coding.
  • You want to add a layer of security and authentication to using that service. Just as different individuals can add different accounts to a Salesforce connector in Azuqua, you can explicitly set permissions for different users and easily control access.
  • You want to leverage a commercial application that’s not already a part of our existing list of connectors. In many cases, we’ll build the connector for you, but in certain cases, customers have had specific specifications for how a connector must work and have chosen to build it themselves.

A Game of FLOs

We have created full step-by-step documentation to show exactly how to create a connector for yourself in Azuqua’s connector builder.

The example that we’re talking about today focuses on creating a connector that can pull information from “An API of Ice and Fire”, a Game of Thrones themed API, created by Joakim Skoog. This is a simple example of an external API in order to demonstrate some of the basic capabilities that these connectors can have.

The documentation walks you through how to create a “Get Character” method connected to the Ice and Fire API. It serves as a good entry point into the world of custom connectors.

We’re not going to go through this entire example in this blog post because it would be too long. Make sure you read our documentation if you would like to try this example for yourself.

If you would like a different example or have any more questions about the way custom connectors work, you can read more here or contact us here.