hi @YevhenK,

So, the requirements of each TMS can vary greatly (such as with RWS and XTM and their various parameters and payload requirements).

Are you able to share which TMS you are trying to connect to, and have you reviewed their documentation to see if what we have already got on our side is suitable or whether or not you need to make something new?

As a side note, the logic of the "TMS Additional Info" is for when you need to provide more parameters. For example, with XTM it's not uncommon to need to force the parameter of a particular "workflow" on their side (yes they use the same terminology as us) or the parameter of an "account" or "project" because most TMS's are used by Agencies and so there is a very specific topology to follow but it's also important to note that it's not always the case.
In the scenario of connecting to an Agency's TMS, you might need to factor in the "Customer", the "Project" and the "Model". But like I said, each TMS and their respective structure is different and not knowing which one you are trying to connect to would make that quite hard.

In my example instance, I am integrating with my XTM demo instance, which has a very specific "workflow" in XTM to route all translation requests in a very specific way. They call it a "template" and so I leverage the "Additional Info" to provide that in my LF setting record (this is the one used for the artefacts and would not be hardcoded in the flow, the flow just calls this to see if there is something to send):

Based on what you've said so far, my suggestion would be to thoroughly read through their documentation to see if you are sending everything it expects and then review how their end is expecting to send the payload back to you (if that makes sense),

Many thanks,

kind regards