hmmm okay I think I see the issue. I think it’s the endpoint that you’re calling from within the setup workflow. In your initial example, you’re trying to kick off a pipeline using thehttps://circleci.com/api/v2/project/github/org/repo/pipeline endpoint. This would trigger a completely separate pipeline, rather than continuing the pipeline from your setup workflow. So I think it would be expecting the parameters you’ve defined to be in your setup config rather than the generated config.
The endpoint to continue a pipeline and trigger more workflows from within the setup workflow is different. It’s https://circleci.com/api/v2/pipeline/continue. Check out the API docs are here for the endpoint. You can see it has some input for the parameters that you have defined in your deploy.yml.
if you’re trying to continue the pipeline and call new workflows from the setup workflow you should use the continue API endpoint above. If you’re trying to launch a completely separate pipeline then you would use the API pipeline endpoint in your original post, but I think the parameters would need to be defined in your config.yml. does that make sense?
This post here may help break down what you need to do for continuing the pipeline. Check out the continuation orb example as that may make this easier for you and remove the need craft your own API calls.