Analytics data for decks
When a deck needs customer or product data, ask the Analytics agent over A2A
before creating or changing Slides content. The user's wording can be direct,
such as "ask the analytics agent to ...", or implicit in a request for customer,
account, CRM, HubSpot, pipeline, renewal, usage, product-activity, Gong, or
other analytics data.
Delegation
- Use
call-agent with agent: "analytics" and a natural-language message
by default. Describe the business question, requested window or cohort, and
the concise result shape the deck needs. Analytics decides which sources,
tools, queries, and joins answer it.
- A direct
action + input call is optional only when an exact bounded
semantic read and its complete schema are already known. It is not a fallback
for slow, failed, or unavailable agent delegation. Never invent an Analytics
action contract to make a demo pass.
- Slides must not write SQL, choose a warehouse or provider, call HubSpot/Gong
directly, or interpret a provider schema itself. Analytics owns source
selection, data dictionary interpretation, filters, joins, and query
execution using its own instructions and connected-source status.
Evidence and deck behavior
- Preserve the question, source, filters, date window, coverage, counts,
pagination, and limitations from Analytics. Never invent customer data or
claim a lookup succeeded when it failed.
- If a source is unavailable, name the missing source and continue only with
clearly labeled data that Analytics actually returned. Do not expose
credentials or raw provider payloads.
- Before generation, call
get-workspace-defaults when no reference deck or
design system is named, then follow creative-context for approved brand
context and provenance. For updates, preserve the existing deck structure
and make focused slide edits.
1---2name: analytics-data-for-decks3description: Route customer, account, CRM, HubSpot, pipeline, renewal, usage, product activity, Gong, and other analytics-backed deck requests through the Analytics agent. Use when generating or updating Slides content that needs external or first-party data.4---56# Analytics data for decks78When a deck needs customer or product data, ask the Analytics agent over A2A9before creating or changing Slides content. The user's wording can be direct,10such as "ask the analytics agent to ...", or implicit in a request for customer,11account, CRM, HubSpot, pipeline, renewal, usage, product-activity, Gong, or12other analytics data.1314## Delegation1516- Use `call-agent` with `agent: "analytics"` and a natural-language `message`17 by default. Describe the business question, requested window or cohort, and18 the concise result shape the deck needs. Analytics decides which sources,19 tools, queries, and joins answer it.20- A direct `action` + `input` call is optional only when an exact bounded21 semantic read and its complete schema are already known. It is not a fallback22 for slow, failed, or unavailable agent delegation. Never invent an Analytics23 action contract to make a demo pass.24- Slides must not write SQL, choose a warehouse or provider, call HubSpot/Gong25 directly, or interpret a provider schema itself. Analytics owns source26 selection, data dictionary interpretation, filters, joins, and query27 execution using its own instructions and connected-source status.2829## Evidence and deck behavior3031- Preserve the question, source, filters, date window, coverage, counts,32 pagination, and limitations from Analytics. Never invent customer data or33 claim a lookup succeeded when it failed.34- If a source is unavailable, name the missing source and continue only with35 clearly labeled data that Analytics actually returned. Do not expose36 credentials or raw provider payloads.37- Before generation, call `get-workspace-defaults` when no reference deck or38 design system is named, then follow `creative-context` for approved brand39 context and provenance. For updates, preserve the existing deck structure40 and make focused slide edits.
Builder.io