No two businesses are alike—so why settle for one-size-fits-all integrations? With Celigo, you don’t have to.

Some users assume that Celigo’s prebuilt connectors are the only option or that protocol support is limited. But in reality, Celigo’s platform is designed for extensibility with powerful customization options.

In our latest webinar, “Integrate Anywhere, Anyhow: Harnessing the Power of JDBC, HTTP, and Celigo’s Extensible Connectors,” we unpacked three major myths about Celigo’s connectivity and demonstrated how our platform offers true customization—so you can build exactly what you need without compromise.

If you missed the session, here’s a breakdown of the key takeaways.

Myth #1: All connectors are the same

One of the biggest misconceptions about Celigo is that all of our connectors function the same way. In actuality, Celigo offers two main types of connectors—prebuilt connectors and the HTTP universal connector—to provide both ease of use and advanced customization.

Prebuilt connectors offer dropdown lists that allow users to quickly select resources and API endpoints. Designed for simplicity, they offer a streamlined setup that is ideal for less technical users. On the other hand, the HTTP universal connector provides greater flexibility for technical users by allowing you to manually configure HTTP methods, URIs, and body requests.

And, you don’t have to choose between the two. You can switch between prebuilt connectors and the HTTP universal connector. This means you can:

• Use prebuilt connectors for quick authentication and easy setup.
• Switch to the HTTP universal connector when you need to modify payloads or protocol types.
• Modify existing connectors rather than building new ones from scratch.

Connectors don’t have to box you in. With Celigo, you can tweak and customize them to meet your needs.

Explore an example of how you can switch between a prebuilt and HTTP universal connector. 

Myth #2: Celigo is limited to REST-based integrations

Some users believe Celigo only supports REST-based integrations. While REST is a common choice, it’s not the only option. Celigo supports many different protocols, one that has been growing is JDBC (Java Database Connectivity) connector. 

When combined with our on-prem agent, you can add your JDBC drivers easily and connect to additional systems

See an example of how to implement a JDBC connector. 

Myth #3: You’re stuck with prebuilt connectors

A common assumption is that Celigo only offers prebuilt connectors—meaning if an integration isn’t available out of the box, you’re out of luck. But that isn’t the case. Celigo enables users to create their own connectors tailored to their unique needs.

To build your own connector, start by downloading the HTTP connector Postman schemas. Next, configure your schemas. Then, create the HTTP connector using Postman and the configured schemas. 

Before you start building, be sure to identify:

• Preconfigured fields in your system
• Authentication type 
• Base URL for the connection
• Values that will change from one configuration to another

This is a particularly good use case for managed service providers who need multiple customer-specific connections.

Learn how to build your own connector in the Celigo platform.

Connect everything with Celigo

Celigo’s platform is built for flexibility, ensuring that integrations adapt to your business—not the other way around. Whether you need the simplicity of prebuilt connectors or the customization of the HTTP universal connector, Celigo gives you the tools to integrate without limitations. No matter your requirements, you can build, modify, and scale your integrations with ease. 

Be sure to check out the full session on-demand for hands-on demos and expert tips. And tune in for the next webinar in our Tech Spotlight Series, “From Errors to Efficiency: Engaging Operations Teams for Smarter Integration Management,” April 1st.