If you're using External MySQL, PostgreSQL, or Oracle queries in Xano, you've probably run into this: the connection string field only accepted a hard-coded string literal. That meant no flexibility, no environment-based switching, and a lot of manual updates if anything changed.
That changes with this release. Connection strings in external database queries can now be populated by a variable and support filters, giving you full control over how and where your queries connect. Whether you need to route queries to different databases based on environment, tenant, region, or any other runtime condition, you can now build that logic directly into your function stacks.
With dynamic connection strings, you get:
Variable-driven connections: Populate connection strings with variables instead of hard-coding them, making your workflows portable and maintainable
Filter support: Apply filters to connection string fields for even more control over how values are resolved
Multi-environment flexibility: Easily switch among development, staging, and production databases without duplicating or editing function stacks
Cleaner multi-tenant patterns: Route external queries per tenant or per region dynamically, without workarounds