Articles in this section

Choose between an application or a universal connector

There are hundreds of application connectors, one universal HTTP connector, and one universal GraphQL connector. How do you choose between a simple, pre-built application (with or without an HTTP or GraphQL form view) or a more granular universal connector? Each type provides different configuration options, and your chosen type determines how quickly, easily, and detailed your connection configurations get.

Warning

Authentication types will vary depending on your connection type and connector.

Pre-built application connectors

Pre-built application connectors are designed to optimize your connection to specific platforms. The simple, pre-built application connector will grant you easy access to your application. You may not be able to modify some aspects as carefully as you’d like, but you’ll have a complete, easy, and secure connection to your application.

After you find your application connector, you can toggle between the Simple, HTTP, or GraphQL forms. Whether you choose a Simple or HTTP/GraphQL form view, you're still using a pre-built application connector. The more complex HTTP/GraphQL forms include additional configuration options usually reserved for the standard universal HTTP or GraphQL connections.

Simple vs. HTTP or GraphQL forms

After choosing your pre-built application connector, you can toggle between a Simple or HTTP/GraphQL form view for more detailed customization. The Simple form view uses the minimum number of fields and configurations while maintaining a secure connection. The HTTP or GraphQL forms within your pre-built application connector provide additional configuration options pulled directly from the universal HTTP or GraphQL connectors.

toggle_button.png

Simple vs HTTP-based form toggle

simple_graphql_toggle.png

Simple vs GraphQL-based form toggle

The differences between a simple or form view (HTTP or GraphQL) can be radical, and you should always consult the universal connector guides for HTTP or GraphQL, as some fields are pulled directly from these connectors.

Note

This toggle will become available for more connectors over time. It’s not currently available for every connector.

Simple forms only include the most common settings required for integrating with the application. A simple connection provides the maximum security available without configuring many fields.

If HTTP and GraphQL are available, you may need to pick the API type. This will determine how you use your application's API(s) and may change configuration options. Check your application's API requirements to determine which API type suits your needs.

recharge_connection.png

Simple application form view (HTTP-based API type)

Simple_graphql_based.png

Simple application form view (GraphQL-based API type)

The HTTP or GraphQL forms have more configuration, control, and authentication options but are still not identical to the universal HTTP or GraphQL connectors. Consider these forms a simplified version of the universal HTTP or GraphQL connector. Toggling to the HTTP or GraphQL form allows you to configure additional details using the application connector.

HTTP_based.png

HTTP application form (see toggle)

graphql_based.png

GraphQL application form (see toggle)

An HTTP or GraphQL form differs from a universal HTTP or GraphQL connector. For example, creating an iClient directly in the Simple or HTTP form view is less granular than using a universal HTTP connector.

Universal connectors

The universal HTTP or GraphQL connectors give you the finest level of granularity when configuring your connection. Using these connectors, you can customize almost every aspect of your connection. The universal connectors will grant you more control over scopes, authentication types, permissions, requests, and responses.

Warning

Authentication types will vary depending on your connection type and connector.

After entering the Base URI in a universal connector, you can still select the prebuilt application connector, if available. If you choose the prebuilt application connector, the Base URI field is disabled, and the Simple form view will appear.

To review documentation for the Simple form view, navigate to the Celigo integrator.io Help Center and search for your connector. For example, if you switch to the Simple view for the Stripe connector, you can search for "Stripe" or "Set up a connection to Stripe" to find the application-specific articles. To remove the simple form view, click Clear selection. You can ignore the Simple Form view and continue using the HTTP Form view.

23292264807067-Simple switch.png

Choose between an application or a universal connector

There are differences between an application and a universal connector. Application-specific forms are based on the universal connector but include only the most common settings required for integrating with the application. You’ll know you’re using the universal connector if you select the HTTP or GraphQL application when creating your connection.

Let’s take a quick look at the differences between these connections:

Connection type

Mock output and response data

Automatic latest API version of resources and endpoints

Query parameters (export and import)

Application –Simple form view

Quick connection

Yes

Yes

Yes

Application – HTTP or GraphQL form view

Configure HTTP/GraphQL connection

Yes

No

No

Universal HTTP or Universal GraphQL

Configure HTTP/GraphQL connection

Yes

No

No

These connector differences are most visible at Resources → Connections → Type. When you view your connections, the Type column will display whether the application is HTTP/GraphQL or application-based.

Simple vs universal exports, lookups, and imports

You can toggle between the simple or HTTP/GraphQL form view of an export, lookup, or import. The simple views include:

  • Mock output and response data

  • Query parameters (export and import) – You can search through all query parameters.

    • Mandatory parameters are provided for you and disabled so they can’t be removed.

    • Search for, add, or delete features for query parameters.

    • Handlebars to add query parameters or values.

    • Select the setting’s value from a drop-down list when the available choices are documented and limited.

    • Error messages remind you if a value isn’t set for a mandatory parameter.

  • For resources and endpoints with different API versions

    • integrator.io will default to the latest version.

    • You can choose a resource, endpoint, and version, but you can only choose the version if it isn’t in the connection.