Forms are collections of fields displayed on a page that allow you to enter the information necessary to complete a specific task. When setting up or modifying your export, you can keep up with API changes in real-time and get more control by switching between application-specific and universal forms.
- Understand forms
- Form View options
- Reasons to switch from application-specific connector forms to universal connector forms
You use forms to establish your connections or map your data when building an integration on integrator.io.
Forms simplify the integration process by displaying fields for all required API information you need for your integration. The export configuration form allows you to toggle between specific connector forms and generic connector forms.
All export forms have a Form View drop-down menu you can use to select specific connector types. Each form view option you select displays the fields required to establish the selected connection type.
Every app and system you use integrator.io to communicate with has its own dedicated form that allows you to enter all information needed to connect, configure exports, map data, and configure imports for those apps. Application-specific forms guide you through the process of building integrations with a specific system's required and optional fields so you can optimize the effectiveness of the connector.
You can use universal connector forms to integrate with systems that don't yet have a dedicated form. These connectors include REST and HTTP connection types and guide you through the process of configuring exports or imports with generic protocols.
These forms are dynamic in that they add, change, or remove fields based on the selections you make.
For example, the fields you see on a generic form that’s using a GET method displays different fields from those you see on a form using POST. Since universal forms are not specific to any app or system, they can have more fields available than are necessary for a given system in order to account for a variety of systems that use those protocols.
A universal connector form can occasionally give you more control and allow you to keep up with API updates that have not yet been accounted for by an application-specific connector form.
Generic forms have many fields in order to account for the more technical details of configuring the export, like configuring headers, providing paths to resources and status codes, and setting up pagination. If the app or system that you’re working with has updated their API, you can keep up with those changes in real-time in cases where the app-specific form does not yet include the expanded functionality. For example, if the API gives access to an expanded menu of resources or pagination capabilities, you can use the generic connector’s form to work with those changes in your export.