Hi there. You can pass variables into a SOAR connector function, but they must come from places that the connector runtime understands (inputs, incident fields, artifacts, datatable rows, etc.), not from arbitrary "local" variables inside the query definition itself. Connector functions only resolve values that are available to the playbook at run time and are referenced through supported expressions.

Common options:

• `playbook.inputs.<name>` for explicit playbook inputs.

• `incident.<field>` or `artifact.<field>` to use values from the current incident or artifact.

• Datatable/row fields (for example, inside a For Each Row loop) using the row's field references.

If your "variable" is not really a playbook input but, say, an incident custom field, use `incident.my_custom_field` instead of creating a fake input.

If the connector UI only shows playbook.inputs

Some early or simple examples in the docs and community posts only show `playbook.inputs.xxxx`, which is confusing when the value clearly comes from elsewhere.  In practice, you can:

• Define a playbook input and map it from an incident or artifact field in the "Input Mappings" section, then reference it as `playbook.inputs.my_input` in the connector.

• Or, where supported in newer connector/REST function UIs, reference incident or artifact context directly (for example, `incident.id`, `incident.properties.<field>`, `artifact.value`) in URL path, query string, or body templates.

The first approach is the most portable and works even if the UI only documents `playbook.inputs.*`.

Cheers! Hope this helps a little. Maybe someone else has suggestion that can help too. Happy Holidays