Dynamically Switching Between Multiple Credentials for the Same Connection in Celigo
Hello,
We've been working with Celigo for integrating with -in this case- an eCommerce platform. Our challenge lies in the requirement to use multiple sets of credentials for the same connection within a single integration flow. The structure of our flow remains consistent, but the credentials need to be changed dynamically based on certain conditions or triggers. Specifically for predefined connectors and not HTTP connections only.
While it's possible to clone the flow for each set of credentials, this seems inefficient and cumbersome from a maintenance perspective. Manually switching credentials within the flow settings isn't feasible either given the dynamic nature of our requirements.
Has anyone in the community faced a similar challenge in Celigo? I'm curious if there are any creative solutions or workarounds to handle this, without resorting to external systems or processes.
Your insights would be greatly appreciated. Thanks in advance!
-
Nuri Ensing there isn't any current way to do this. The closest way you can get to it is by calling myAPIs within your flow and those myAPIs running virtual imports/exports, but then it requires you to build out myAPIs with Javascript.
In your use case, do you basically have multiple brands/accounts of the same ecommerce platform and they all need to go to the same destination/ERP, like NetSuite?
0 -
Nuri Ensing -- how many different credentials are there? Curious to understand why different creds are needed. Can you share more?
Two quick ideas:
- You can also use virtual imports/exports in our API which can be invoked via a script. Eg: https://docs.celigo.com/hc/en-us/articles/360048159772-Invoke-a-My-API-virtual-export
- Can you create different connections for each? And then clone bubbles and have each clone use appropriate creds, and finally have some branching logic to route to the right bubble (cred) in each case? Definitely adds a bit of complexity, but maybe an option if you don't have too many separate creds to worry about.
0 -
Hi Tyler Lamparter, Matt Graney
First and foremost, I appreciate the rapid feedback and the depth of insight both of you have shared.
To provide a clearer picture: Our client's objective is to funnel product data from a singular PIM into BigCommerce. The challenge lies in the fact that these products might be associated with multiple "brand" or "companies" identities. We initially thought this would necessitate multiple sets of credentials for each distinct "company" on BigCommerce. However, upon delving deeper into BigCommerce's functionalities, I discovered the 'storefront' feature. This revelation suggests that BigCommerce can manage various storefronts under a single connection.
This discovery has led me to conclude that the initial need for managing different connections might not be necessary for our specific use case anymore..
That said, while our immediate use case might have found a resolution, I believe there is merit in discussing the broader application of managing identical flows across different connections. A potential solution might be to integrate a dynamic multiple connection feature into the flows. This would enable to maintain a consistent flow structure but have the flexibility to dynamically alter its connection based on certain criteria or triggers. Such a feature would prove invaluable for scenarios where identical data processes are needed across various connections but within the same flow framework.
Thanks again for your invaluable insights and collaboration.
0 -
Nuri Ensing Thanks for the suggestion! We've added it to the product board for the team to consider based on priorities. (Moving this post to the product enhancement section.)0
Please sign in to leave a comment.
Comments
4 comments