# \[external integration\] Conditional fields in form — not possible

**URL:** <https://community.gladysassistant.com/t/integration-externe-champs-conditionnels-dans-le-formulaire-pas-possible/10823>\
**Category:** Demande de fonctionnalités\
**Created:** [September 7, 2026, 8:42am UTC](https://community.gladysassistant.com/t/integration-externe-champs-conditionnels-dans-le-formulaire-pas-possible/10823 "2026-09-07T08:42:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [September 7, 2026, 8:42am UTC](https://community.gladysassistant.com/t/integration-externe-champs-conditionnels-dans-le-formulaire-pas-possible/10823/1 "2026-09-07T08:42:16Z")

</div>

Would it be possible to add a notion of conditional visibility in `config_schema` for external integrations (e.g., a field `visible_if: {key, equals}`)?

Currently, the entire list of fields is always displayed, which becomes difficult to read as soon as an integration has a configuration with multiple modes (e.g., «&nbsp;dedicated MQTT broker&nbsp;» vs «&nbsp;existing broker,&nbsp;» or choice of a discovery method). This would require adding the field to the allowlist of the validator (`externalIntegration.validateManifest.js`) and having `ConfigSchemaForm.jsx` read `values[...]` during rendering.