iPaaS Core

Work with elastic.io's own integration management API through a visual interface

Programming language:

Javascript

Current state:

Production

Provider of the connector:

elastic.io

Type of license:

Proprietary

Tags:

When it comes to application integration on the elastic.io iPaaS, you would normally require the connectors of the applications you’re working with plus, potentially, a few of the so-called Utility connectors such as JSONata or Splitter in order to add some business logic.

However, in some rare cases, you might need to manipulate elastic’s own integration artefacts such as flows – for example, when you migrate entire integration flows from one contract to another.

For this purpose, we have created the iPaaS Core connector, which allows you to call to the endpoints of elastic.io’s own integration management API through a visual interface, which is much more easy-to-use and user-friendly than working with the raw code.

About iPaaS Core connector

This connector was created particularly for the elastic.io platform to manipulate integration artefacts such as flows via elastic.io’s own REST API. It is compatible with all other connectors and comes with the platform by default.

Given its nature, the iPaaS Core integration connection doesn’t come with a trigger function, so when an integration flow is created, it won’t appear in the list of available connectors as the first component. Instead, you’ll be able to see it only when chosen as an action.

This connector is under the proprietary license, which means that you cannot change or extend this connector yourself. If you have any questions, you’re welcome to contact our pre-sales team at ps[at]elastic.io.

PLEASE NOTE: To use this connector, you require an account on the elastic.io integration platform. To create one, please sign up for a free 14-day trial here.

How to add and use iPaaS Core on elastic.io

Step 1
First navigate either to the Dashboard or Flows section of the platform, then click on the button “Add new Flow” and select the data source which you’d like to start building the flow. Since iPaaS Core connector doesn’t have any triggers, you won’t be able to see it in the list of available connectors at the stage.

Only after you’ve selected your data source as a trigger and clicked on the next “+” button to add an action, you’ll be able to see iPaaS Core.

iPaaS Core connector selection

Step 2
Select the function that you’d like to work with. You can fetch dynamic metadata or select model, look up one or several objects by unique criteria, make a raw request to our platform API’s endpoints, or upset object by unique criteria.At the moment, all functions work only with one data object, which is Flows. More objects can be added upon request.

Creating credentials for iPaaS Core

Step 3
Once you’ve selected the function you want to work with, the platform will ask you to add new credentials. This is really easy, because you’ll find everything you need for that within your own workspace: the URL of the platform’s instance, your email address, and the API key which you will find under “Profile Information”.

Configuration of iPaaS Core

For more details on how to work with the iPaaS Core component, please check the dedicated Documentation page following the link above.