Are you using an out of the box SaaS connector in your environment, and it has almost all the features you need, but is missing a key piece of functionality in your environment? Or maybe you are using an open source connector and want to change its functionality in some way without breaking your upgrade path for future changes? Introducing connector customizers! In this session, I will walk you through how to get started using customizers and provide an example of some simple but powerful ways that you can introduce non-breaking changes to a SaaS connector.
Hi @philip-ellis
Do you have any sample code on how to update the request endpoint using connector customizers for webservice saas connector using .beforeStdAccountList command? or could you share some info how this can be done ?
Here is what I’m looking for,
for VA based webservice connector, using before rule ,we were able to update the baseURL on requestEndPoint. I’m looking similar functionality to achieve for SaaS connector with or without customizers.
Our API Scenario, after authentication, API return the base URL which needs to be used for account aggregation. more details - Modify Webservice SaaS connector requestEndPoint using customizer
@philip-ellis I have deployed a customizer for the OOTB Workday SaaS connector. I have successfully built and linked the customizer to the Workday connector instance. The customizer has some basic logger.info statements I was hoping to see when running test connection while tailing the logs with sail conn logs tail, however, I am not seeing the customizer logs, just the default connector logs. Any ideas why my logs are not showing up? I am trying to validate the source config input before I move forward with this implementation.
So I dug a bit deeper into this. I tested using the same exact customizer on a very basic Web Services SaaS connector instance and my logs printed out just fine when tailing via the CLI. For the Workday SaaS connector, it seems to just be some sort of proxy which still uses the old school Java-based connector (hints in logs show of using Apache commons HTTP classes, etc.), so I guess customizers are not even invoked? This seems like a decent flaw to me. @developer_relations_team can we confirm this is the case that these customizers do not work for all ‘SaaS’ connectors?
