Access Organization Name in Workflows

[lelondono]

Access Organization Name in Workflows

[frikky]

Summary I would like to request a feature that allows workflows to directly access and utilize the organization name associated with the repository or workflow context. This feature would significantly enhance automation capabilities by enabling more personalized and context-aware workflow actions.

Use Case In many automation scenarios, particularly in multi-organization setups or enterprise environments, workflows need to behave differently based on the organization context. For example, notifications, deployment strategies, or access controls might vary from one organization to another. Direct access to the organization name within the workflow would allow for dynamic adjustments and more intelligent automation logic.

Potential Benefits Enhanced personalization for automated messages or notifications sent from workflows. Improved control and differentiation in multi-organization environments, allowing workflows to adapt based on the organization context. Increased efficiency in workflow design by reducing the need for external scripts or API calls to fetch organization information.

I believe this feature would be a valuable addition for many users and look forward to seeing its potential implementations. Thank you for considering this request.

Heyo!

Great suggestion, and this is already supported using the built in utility functions that you can access with Python (or liquid python inline anywhere).

With liquid it would look something like this (you can put this ANYWHERE). Add ["name"] on the end to get the name instead of all the org info.

{% python %}self.full_execution["workflow"]["executing_org"]{% endpython %}

Tell me how it goes :)

[lelondono]

Hi frikky,

Thanks for getting back to me! Your fix does the trick for the main workflows, but it seems like it doesn't quite cut it for the subflows.

Regards,

[frikky]

Hi frikky,

Thanks for getting back to me! Your fix does the trick for the main workflows, but it seems like it doesn't quite cut it for the subflows.

Regards,

ooh, don't subflows have executing org set? fascinating bug in that case

[frikky]

Made a quickfix. Will be available in the next nightly release of the backend (next few days sometime) to also work for subflows. Here's the full command I tested with.

{% python %} print(self.full_execution["workflow"]["execution_org"]["name"]) {% endpython %}