FAQ: When should I use a universal connector form view instead of an application-specific connector form view?

Export and import configuration forms in integrator.io (application-specific or universal) are dynamic in that they add, change, or remove fields based on the selections you make. For example, the fields you see on a form that’s using a GET method displays different fields from those you see on a form using POST.

Since universal connector forms are not specific to any app or system, they display more fields and settings than are required by any single platform because they must account for a variety of systems that use those protocols. Whenever possible you should rely on an application-specific connector form so that you don't have to navigate or ignore fields that are irrelevant to your integration; however, a universal connector form can occasionally be useful for API updates that have not yet been accounted for by an application-specific connector form. If the app or system that you’re working with has updated their API, you can keep up with those changes in cases where the app-specific form does not yet include the expanded functionality. For example, if the API allows access to an expanded menu of resources or pagination capabilities, you can use the universal connector form view to work with those changes in your export or import.

For more information, see Choose application-specific or universal form views.