Log In to iHub Site
Test Environment: https://ihub-uat.seko360.com/
Live Environment: https://ihub.seko360.com
Select User account in the Header dropdown for multiple Identities/user entitlements.
If user has only one identity, dropdown is not visible.
Settings Menu
Create Pipeline Groups (optional)
Pipeline Group helps in organizing various pipelines into groups for easier identification.
Part I - Group Details
Click on Settings Menu → Pipeline Groups
Click “Create New” Button on the bottom of the right pane
Type the Name of the Service Provider
Click SAVE button
Part II - Notifications
“Notifications” Tab will be visible after completing details in Part I
Add Email address where to receive notifications (success or failure)
Add Data items (e.g. order ID, SKU, etc) to include into notifications.
The syntax for referencing ‘data items’ should be: { $.trigger.data.abc.def },
where abc.def are the object properties in the request body.
e.g. Name: SKU Data path: {$.trigger.data.inventory_item_id}
Click SAVE button
Add Client Credentials
Some Service Providers requires unique credentials for each client which are configured based on credential Type.
Click on Settings Menu → Credentials
Click “Create New” Button on the bottom of the right pane
Type the Name of Credentials for a specific Service Provider
Select Authentication Type and Fill in details/data needed
Authentication details may vary depending on Credential Type:
*Generate Access Token or API keys for 3rd party apps like Shopify (Generic Http)
*Add service ID (Generic Http)
*Add username and password (Basic Http)
*Add connection string ( for SQL/database)
Click SAVE button
Set Up Pipelines
Part I - Pipeline Details
Click on Settings Menu → Pipelines
Click “Create New” Button on the bottom of the right pane
Add Pipeline Name
Select Pipeline Template. Leave blank if no template needed/Create new.
Pipeline Template is configured at Admin site
Toggle “IsActive” to enable (YES) and disable (NO) a Pipeline
Click SAVE button
Select Pipeline Group (optional)
Configure TRIGGER then SAVE
Configure PIPELINE then SAVE
Scriban is a scripting languange and a versatile tool for creating dynamic messages and content in applications.
SEE More Examples here: https://seko.atlassian.net/wiki/pages/resumedraft.action?draftId=2982740027&draftShareId=a39bb7ab-7821-4545-90a9-087806cdeee0
Part II - Pipeline Variables
“Pipeline Variables” Tab will be visible after completing details in Part I
Click “Create New”
Select Client or Pipeline
Pipeline variables are specific to a single pipeline and are shared between its runs.
Client variables are accessible across all pipelines for a client, allowing shared values between multiple pipelines.
Fill in Variable Name and Value. Specify the requirements based on the pipeline’s function.
Click SAVE button
Repeat steps if needed
Part III - Notifications (optional)
“Notifications” Tab will be visible after completing details in Part II
Add Email address where to receive notifications (success or failure)
Add Data items (e.g. order ID, SKU, etc) to include into notifications.
The syntax for referencing ‘data items’ should be: { $.trigger.data.abc.def },
where abc.def are the object properties in the request body.
e.g. Name: SKU object: inventory_item_id
Data path: {$.trigger.data.inventory_item_id}
TEST Pipeline
1. Manual Pipeline Run
Click “Run Now” button to Test all steps in a Pipeline
2. Dry Run Task
Click “Dry Run” button to test specific task
Export Pipeline
Click “Export” button to export in json file
Pipeline Runs
Click on Pipeline Runs Menu to Monitor History and execution of Pipelines
Use search Filters and click “APPLY” button
Click “VIEW” button to Check errors and View details of activity
Activity will show Green
if successful or Red X if failed
