cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

SDK Connector capture Recipe variables

syepes
Deputy Chef II
Deputy Chef II

Hello,

I would like to know if there's a workaround for capturing specific variables configured in the Recipe using the Connector SDK.

Specifically, the issue I'm facing is that the connector has an input with a default value, but it is searching for a line "605cd37b" that does not exist in the target recipe, example:

 

{ name: 'debug_level', label: 'Debug Level', type: 'string', control_type: 'text', optional: false, sticky: true, ngIf: 'false', default: '#{=_dp(\'{"pill_type":"output","provider":"workato_variable","line":"605cd37b","path":["debug_level"]}\')}'}' },

 

Is there a way to do this like with the account_property and project_property by specifying a path or just the name?

Thanks in advance for the help,
Seb

3 REPLIES 3

Bhagya_pola
Deputy Chef III
Deputy Chef III

Hi @syepes

If I understood you right, youโ€™re trying to get a variable into your connector input (like debug_level), but the issue is that the default is pointing to a recipe step ID, which might not always exist. That can break things if the recipe changes or gets copied.

What I tried instead is using a project property โ€” itโ€™s way more reliable. You just define it once in the project settings, and then pull it into your connector like this:

default: '#{_dp(\'{"pill_type":"project_property","property_name":"debug_level"}\')}'

Screenshot 2025-06-07 105127.pngThat way, no need to depend on any specific step in the recipe, it just works across every recipe in that project.

Let me know if Iโ€™ve got the right idea of what youโ€™re trying to do, and if this actually helps!

syepes
Deputy Chef II
Deputy Chef II

Thanks for the info, actually I am already using the global properties (account_property and project_property), but because currently there are no way of having Recipe specific properties.

I am putting a standard variable block on all our own custom made recipes so that this connector always searches for these specific variables. This is a sort of workaround, it's why I was trying to read the same block from the SDK connector.

I'm probably not understanding what you're trying to accomplish, but if you're already putting the variable block in each recipe why not just pass it into the connector like any other argument?