Connections are established between the source and target applications before creating flows in integrator.io. A connection stores system credentials and other access information of the source or target application.
Establish a connection
Use the following steps to establish a connection:
- Go to integrator.io.
- Click Tools & Resources.
- Click Connections.
- Click + New Connection.
- Enter an appropriate name in Name for the connection being created. For example, if you are creating a NetSuite connection, you might want to name the connection as NetSuite Connection.
- From Connection Type, select the desired connection type. For example, if your source application is NetSuite, you will have to select NetSuite.
Note: After you select the desired connection type, several other fields appear based on the selected Connection Type. For example, if you select Salesforce or FTP, you would see a different set of fields for each Connection Type. For token-based communication, refer to NetSuite token-based authentication and FAQs.
- Click Save to save the connection.
- Optionally, you can click Test to check whether the connection is working fine.
Token-Based connection authentication
For REST API, HTTP, NetSuite applications and others, you can select Token from the Authentication Type field to establish a token-based connection.
- My existing NetSuite connection appears offline despite having correct credentials for authentication. What could be the reason? If your existing NetSuite connection appears offline despite having correct credentials, you might have used the Basic authentication type for creating the connection and you may also have enabled 2FA (Two-factor authentication) in NetSuite. To enable such a connection, you will have to disable 2FA in NetSuite and enter the credentials again to create the connection. However, if you want to use 2FA (Two-factor authentication) in NetSuite, you must modify your Authentication Type from Basic to Token for creating the NetSuite connection in integrator.io.
- Is there a workaround for using Basic authentication type with 2FA (Two-factor authentication) for NetSuite? It is highly recommended that you switch your connection's Basic Authentication Type to the Token Authentication Type. However, if you still want to use the Basic Authentication Type, you can create a custom role in NetSuite for which 2FA (Two-factor authentication) is disabled (a custom role that is specially created for integrations) and has all the required permissions.
- Do I need an integrator.io sandbox license if I want to create an integrator.io connection that connects to NetSuite sandbox environment? If you use the integrator.io platform to build your own integration flow, then you can create an integrator.io connection to the NetSuite sandbox environment without purchasing an integrator.io sandbox license. You can specify the environment on the field provided on the NetSuite connection.
Integration App environment licensing requirements:
- Production environment license: Integration Apps require an integrator.io production environment license to connect to a NetSuite production environment.
- Sandbox environment license: Integration Apps require an integrator.io sandbox environment license to connect a NetSuite sandbox environment.
Note: Although it is technically possible to connect the NetSuite sandbox environment to your integrator.io production environment with an Integration App production license, Celigo strongly recommends that you purchase the Integration App sandbox license because it allows you to use the integrator.io sandbox environment to connect the NetSuite sandbox environment and perform all testing in sandbox environments while keeping the testing and production environments separate. If you choose to use your Integration App production license to connect to a NetSuite sandbox environment, you must uninstall your Integration App after you are done with testing and then reinstall and reconfigure the Integration App to connect to production environments.