Hello! Is it possible to pass any metadata to POST /v1/connections/sync api end point? If not it would be great addition and I could create an issue in github. The use case: I run sync job and then create a task token. The task token is activated once job has finished. The problem is that sometimes job finishes very quickly (before the task token creation). This is why I would like to add metadata with tasktoken to a job call. Then I would call a trigger from the postgres database to finish the task token once status not in ('running', 'incomplete'). Thanks! Thanks P.S. This would be solved if there would be possible to have a simple workflow inside airbyte: job1, job2, job3 finishes -> run DBT cloud Edit: just figured out that Airbyte webhook now includes JOB ID, that helps as well.

Hi. I didnt fully understand the issue here could you elaborate? if this is the use case as I understood it: The flow you wrote, it sounds like you are looking to make airbyte like apache airflow that will orchestrate jobs. This is not what airbyte is for nor it`s API. If you want to get some response once the connection sync is done you can check it`s status each X sec, min etc.. via the API, but passing metadata is usually used via apache airflow, luigi, perfect etc... tech

Eli, I don't want to call API every sec, min etc... So I am looking for some solutions on how to make it more push type. Webhook works for now. Metadata would be useful to have for any reasons inside job's schema