# Job Custom ? This wildcard is replaced by the custom value of a specific key set via specific nodes. It is designed to hold Asset ID from third party systems. If the Medialoopster Add Asset To Project Action is used to add an Asset to Medialoopster, the ID provided by the MediaLoopster API will be added to Helmut’s database connected to the Asset ID provided by Helmut. If the wildcard is used while executing a job that is related to an Asset that holds a third party id, it will resolve the ID. * {job.custom.?} * For the following input (?) --> medialoopster * The output is going to be —> medialoopster asset ID The wildcard can be used according to the third party integrations that do support this wildcard. At the moment this is medialoopster. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.helmut.de/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-custom.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.