โ04-22-2025 07:10 AM
We have a a custom connector that has grown quite large, I've seen that full access to ruby has now been given. Docs: https://docs.workato.com/developing-connectors/sdk/sdk-reference/whitelist-removal.html
Is it possible to split the connector.rb file into smaller files and import them using require? or does anyone have examples or best practices in organizing a Workato connector code base?
yesterday
@Proggreg wrote:We have a a custom connector that has grown quite large, I've seen that full access to ruby has now been given. Docs: https://docs.workato.com/developing-connectors/sdk/sdk-reference/whitelist-removal.html
Is it possible to split the connector.rb file into smaller files and import them using require? or does anyone have examples or best practices in organizing a Workato connector code base?
yesterday
@CETORRES wrote:Hi Community,
I am running into a situation where the HTTP response from a Recipe HTTP Endpoint does not consistently include all the fields defined in the โReturn data to callerโ step. If a field is not populated at runtime, it is omitted entirely from the final JSON response.This results in an inconsistent API schema, where the structure varies depending on whether values are present. This inconsistency causes issues for systems consuming the API, as they expect a predictable and stable response structure.
I havenโt found any documentation that confirms whether this is expected behavior or a platform limitation. Could someone from the Workato team please clarify:
Is this omission of empty fields by design?
Is there a way to enforce the full schema in the response, regardless of values?
If not, is there a roadmap to address this kind of response inconsistency?