Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mock AI Integration
Added a new
MockAIIntegrationMCP workflow tool that enables agents to simulate any external integration (Salesforce, HubSpot, Power BI, etc.) by generating realistic mock data from a free-form prompt and storing it directly into the configured context store (ClickHouse or CockroachDB).What it does
When a user prompts something like "give me top 20 salesmen from my Salesforce data" and no real Salesforce integration exists, the agent automatically calls
MockAIIntegrationwhich:This lets users experience the full end-to-end agent workflow — pipeline ingestion, context store queries, interactive Q&A — without needing any real integrations connected.
Changes
MockAIIntegrationMCP workflow registered as a tool available to all pipeline agents by default, replacing the template-basedGenerateMockin the auto-attached pipeline tool setmockaiintegrationinstead ofgeneratemockmockaiintegrationto the protected tools list in the frontend so it can't be accidentally removed from pipeline agentsawaitin the ClickHouse list tables function that was causing query failuresPrompt used to test
Salesforce
Build me a "sales-dashboard" assistant. It should have a pipeline agent that pulls my top 20 salespeople from Salesforce with their name, email, region, total revenue, deals closed, and win rate for the last 6 months. Store the data in a ClickHouse dataset called "salesforce-reps". Then create an interactive agent called "sales-assistant" that can query that dataset and answer questions like "Who are my top performers in the West region?" or "Which reps have a win rate below 30%?"
Qrm medical facilities
Build me a "Regional Consultant Assistant". It needs two agents:
A pipeline agent called "qrm-kpi-pipeline" that pulls facility-level KPI data from our QRM platform — therapist productivity percentage, cost per treatment, and trends — for 8 dummy facilities across Northeast, Southeast, Midwest, and West regions. Include 12 months of weekly historical data so trend queries work. Store everything in a ClickHouse dataset called "qrm-kpi-data".
An interactive agent called "facility-advisor" that a field consultant can ask questions like "Which facilities had productivity drop below 80% this week?", "What's the cost per treatment trend for Sunrise Care over the last quarter?", or "Compare Northeast vs Southeast productivity." It should query the qrm-kpi-data dataset and respond in plain English.