hi
@will hitchcock, So you can trigger the worflow assiciated with the
Create Flow Run From Deployment API . Note since this will return the workflow run id. Since the workflow will queue to the work pools and will be processed by the workers so it will be async process and won't be ideal for you to wait to get the result.
What you can do is. Create your workflow as subflow and then use the worklow as a task to send the result back to your via an API ? like a push base event. Which you can listen to and update your results. This is one way of doing this.
If anybody have other ideas or better approach to handle please do share. Thanks