...
A Service Provider refers to the external system internal or 3rd party service that your pipeline interacts with. This could be a database, an API, a cloud service, or any other external resource that your pipeline needs to communicate with to perform its tasks. The Service Provider is responsible for handling the requests and providing the necessary responses or data.
Click on Service Providers Menu → Service Provider Setup
Click “Create New” Button on the bottom of the right pane
Type the Name of the Service Provider
Click SAVE button
...
Click on Service Providers Menu → Credentials
Click “Create New” Button on the bottom of the right pane
Type the Name of the Credentials (for the Service Provider)
Select Authentication Type and Fill in details/data needed
...
Click on Service Providers Menu → Endpoints
Click “Create New” Button on the bottom of the right pane
Type the Name of the Endpoint
Select Type Value (HTTP or SQL)
Select Provider
Type HOST (Domain for HTTP or Server endpoint for a SQL)
Select Default Credentials
Click SAVE button
...
Click on Service Providers Menu → Services
Click “Create New” Button on the bottom of the right pane
Type the Name of the Service
Select Type Value (HTTP or SQL)
Select Service Provider
Select Direction (Inbound or Outbound)
Inbound direction refers to data coming into the system.
Outbound direction refers to data going out of the system.
Click SAVE button
...
Part II -
...
Create Configuration Versions/Mapping
“Versions” Tab will be visible after completing details in Part I
Type Version Name
Select Type
Create Input and Output schema
Input schema specifies the structure of the data that a service or system expects to receive. It defines the required fields, data types, and any validation rules that the incoming data must adhere to.
Output schema defines the structure of the data that a service or system will produce and send back as a response. It ensures that the response data is formatted correctly and contains all the necessary information.
For HTTP type like Shopify, use webhooks or API calls in JSON format (See Sample 1)
For Seko systems that uses SQL like DCM, TMS, etc, specify the list of fields you use as a source for SP parameters (See Sample 2)
Sample 1:
...
Sample 2:
...
Part III - Trigger Configuration
...
Click SAVE button to save configuration
Click SAVE button to save the version
Sample 1a
...
Sample 2a
...
Pipeline Templates Menu
Templates are pre-defined pipelines which follow the same structure that can be reused for different Clients. This reduces errors and saves time and effort, as you don’t have to start from scratch each time.
Create Pipeline Template
Click on Pipeline Templates Menu
Click “Create New” Button on the bottom of the right pane
Add Pipeline Name
Configure TRIGGER then click SAVE button
A trigger is a mechanism that initiates the execution of a pipeline based on specific events or conditions.
Configure PIPELINE then click SAVE button
Pipeline action steps are the individual tasks or actions that are executed as part of a pipeline. These steps define the specific operations that need to be performed, such as building code, running tests, deploying applications, or any other automated tasks.
SAVE the Template
...