Saved Queries

[ermoi]

Problem

Users often need to reuse the same complex subscriber queries multiple times (e.g., segmentation for recurring campaigns). Currently, there's no way to save queries, requiring users to:

• Manually copy/paste from external files
• Re-type complex queries each time
• Risk errors in repetitive queries

Proposed Solution

Add a "Saved Queries" feature with:

1. Save query with name

   • Button "Save query" in subscriber search
   • Name + optional description
   • Store the query expression

2. Query library

   • New section: Settings → Saved Queries
   • List of saved queries
   • Edit/Delete options

3. Quick access

   • Dropdown in subscriber search: "Load saved query"
   • One-click to apply a saved query

Use Cases

• Segmentation for recurring campaigns
• Complex queries combining lists + attributes
• Team collaboration (shared queries)
• Documentation of common segments

Implementation Suggestions

• Store in new DB table: saved_queries
• Fields: id, name, description, query_expression, created_at
• Simple CRUD API endpoints
• UI integration in existing search interface

Alternative/Workaround

Currently users maintain queries in external text files, which is error-prone and inefficient.

[knadh]

Hi @ermoi. This is being considered for the next release and there's already a PR open: #2546