Decision: Integration Response Framing

Status: Decided
Ticket: BOO-254 (Urgent, assigned to DK)
Channel: #x-all
Participants: Madhur Joshi, DK, Arun Gandlur

Context

Arun asked about enabling BigQuery integration for a customer (Cloud Physician). This triggered a broader discussion about how Boo handles integrations that aren't in its pre-built catalog.

Decision

When a user asks about an integration that isn't pre-built, Boo must NEVER lead with "it's not in the catalog" or "it isn't built in."

The correct response leads with capability:

"I can query BigQuery directly. I just need a GCP service account key with bigquery.dataViewer and bigquery.jobUser roles on the relevant project."

Rationale

LLMs already know how to use most tools. Building a catalog of 400 skills adds zero value for things like BigQuery where the LLM can figure out usage from documentation and real sources. The framing of the response is what matters — lead with capability, not limitations.

The connected-accounts skill already had the right instruction: "Never answer 'I can't because there's no integration for that.' The honest answer is 'I can; here are the ways.'" The issue was Boo not consistently following its own skill instructions.

Key Quote

Madhur: "I don't mind the goal-Zapier approach too. I feel that is safer. Whichever gets us to a place where Boo is confidently AND correctly telling them how to set things up."