To trigger specific data retrieval or actions within SQAI, you must use the designated Integration Keywords in your prompts. These keywords act as "intent signals" that tell the SQAI orchestrator which tool's API to call or which internal asset to access.
Working with Integration Keywords
When you include a keyword (e.g., "Jira", "Testmo", or a specific filename) in your natural language prompt, SQAI identifies the associated integration and switches the context of the conversation to that specific source.
Intelligent Live-Querying
SQAI is designed to handle the technical heavy lifting for you. While the system uses native querying languages to fetch live data, you do not have to write the code yourself. SQAI automatically builds and executes these queries in the background based on your natural language prompt:
Atlassian Stack: SQAI generates JQL (Jira) or CQL (Confluence) in the background to fetch your data.
Microsoft Stack: SQAI builds WIQL queries to filter through Azure DevOps Boards.
Redmine: SQAI constructs REST queries or utilizes GCBs (Global Custom Blocks) automatically.
Test Management: Simply mention a Test Case ID (e.g., “Retrieve TC-88”) and SQAI will instantly pull the full record.
Knowledge Base Assets (Uploaded Files)
For files uploaded directly to the SQAI Knowledge Base (assets not connected to an external app), you can trigger them by specifically mentioning the filename (and extension) as a keyword. SQAI will focus its analysis on that specific document.
Integration Keyword Mapping
Category | Tool / Integration | SQAI Trigger Keyword | SQAI Background Query |
Project & Task Management | Atlassian Jira (Cloud) |
| JQL |
| Azure DevOps Boards |
| WIQL |
| Redmine (Cloud/Self-Managed) |
| REST / GCBs |
| Notion (Cloud) |
| Keyword Search |
Test Management | Testmo |
| Test Case ID |
| TestRail |
| Test Case ID |
| Xray Test Management |
| Test Case ID |
| Zephyr Test Management |
| Test Case ID |
| TestMonitor |
| Test Case ID |
| BrowserStack Test Management |
| Test Case ID |
| QA Touch |
| Test Case ID |
Documentation & Wiki | Atlassian Confluence (Cloud) |
| CQL |
| Azure DevOps Wiki |
| Keyword Search |
| Azure DevOps Sharepoint |
| Keyword Search |
Internal Assets | Knowledge Base Files |
| Content Parsing |
Prompt Examples
1. Automated Technical Queries
Jira: "In Jira, find all high-priority bugs in the 'Mobile' project that are currently 'In Progress'." (SQAI will build the JQL for you).
Azure Boards: "Show me all work items in Azure Boards assigned to "Josh Brolin" that haven't been updated this week." (SQAI will build the WIQL for you).
Redmine: "Retrieve all issues in Redmine labeled 'Security' from the last month." (SQAI will build the REST query for you).
2. Test Management & ID Referencing
Direct ID: "What are the pre-conditions for TC-402 in Testmo?"
Traceability: "Does TC-105 in TestRail cover the requirements described in Jira ticket
PROJ-99?"
3. Knowledge Base (File) Queries
Specific File: "Based on Release_Notes_v3.pdf, what are the three main features we need to test?"
File Comparison: "Check if the acceptance criteria in User_Stories.xlsx match our current test cases with ID's X1029, X3390 and X4448 in Xray."
Best Practices
Use Natural Language: Don't worry about syntax; just describe what you need as if talking to a peer.
Filename Accuracy: When querying the Knowledge Base, include the extension (e.g.,
.pdf,.docx) so SQAI knows exactly which file to open.Combine Sources: You can bridge apps and files in one go: "Update TC-55 in Zephyr based on the new logic found in API_Documentation.docx."