Wevo iPaaS Connector store¶

The Connector store is an area where you can access all available connectors. Connectors are tools tailored to a specific system from the market, for instance, databases, ERP systems, marketplace platforms, SaaS services, among others. These tools are responsible for establishing connections with the systems they were designed for, which in turn, makes integration possible. Using the SQL Server connector as an example, it can be used to access the data contained inside an SQL Server database.

The Connector store works similarly to typical app stores available on mobile devices. In the Connector store, you can install connectors and configure your accounts for them. This page goes into more detail about how best to use the Connector store.

Overview¶

In the platform menu, click Builder > Connector Store. This will give you access to the connector catalog, as seen in the screenshot below:

The following options are available in the lateral menu on the left:

• Search Connector: Use this search field to look up a connector by name.

• Installed: Use this filter to see only the connectors already installed in your environment.

• Available: This filter shows the complete catalog of connectors available for installing.

Install a connector¶

After picking the Available filter to see all the connectors that can be installed, locate the one you want and click Install Connector.

Now, fill in the connector's parameters. These parameters are security specifications that must be defined in order to allow the connector to authenticate a connection with the system via the Wevo platform. For instance, to use the SQL Server connector, some of the fields you need to define include connection string, server, connection port, username and password, so that you can connect to the database. Similarly, most connectors have required parameters that must be defined.

Once you obtain the information you need, fill in all the fields that are required for the connector you want to use, and choose a name in the Account Name field. The configuration you've input will be saved under an account with that name. To illustrate: a connection with a database could have the name "QA Environment" along with a certain set of parameters. That way, when you design your integration, you could specifically define that it uses information from your QA database. Account names can be used with several systems, and they always save the settings defined in the parameters.

After you save, the connector will be shown in the Installed filter.

Actions¶

The actions are all the processes that a given connector is capable of executing within the system it connects with. These processes may include sending a file, downloading some data, deleting records, updating information, looking something up, querying data, altering or inserting information, the list goes on.

The actions work by making an API call to the systems they connect with in order to handle information. During the creation of your flow, you can see the structure of the API call by seeing the JSON payload that will be sent during the query. To learn more, see Mapping.

Each connector has its own actions, which generates many distinct connection possibilities. Similarly to connectors, the actions have parameters that must be configured during flow creation in order to ensure that they will work correctly.

Parameters¶

Connectors can have up to three types of parameters to be defined.

Connector parameters¶

Connector parameters are used to configure an account that will establish a connection with the target system of a given connector, as explained above. They can vary a lot: from defining a region, to inserting an access key, authentication tokens, usernames and passwords, among others. In summary, the connector parameters are data you obtain through your system, in order to enable a connection.

Action parameters¶

Action parameters are configurations that exist inside specific actions. You only need to configure them when you are creating your flows, however, you can see what they are from the Connector store, as illustrated below.

Trigger parameters¶

Triggers are what kickstarts the integration flows. In order to configure a trigger, you need to pick which event will perform that task.

Triggers define how an integration flow will begin (see Configure or Modify a Trigger to learn more). Some connectors may have specific triggers which get a flow started through an event. These events could be, for instance, every time there is a new message, or a new email, or whenever a new order is received, and so on.

Triggers also have parameters, which can be quite similar to action parameters. Such settings allow the trigger to be executed correctly. Again, these parameters must be configured during flow creation.