Coming Soon — This page describes an architecture that is currently in development and not yet generally available. Contact us to learn more.
Beyond Tables: Dynamic API Extraction
Not all valuable business data lives in warehouses. Critical insights often reside in SaaS applications accessible only via APIs — sales call recordings in Gong, meeting schedules in Google Calendar, support tickets in Zendesk. AstroBee can extract data from these sources on-the-fly, transform API responses into ephemeral tables, and include them in the semantic layer for unified analytics.How API Extraction Works
Schema Discovery
AstroBee’s AI agent analyzes API documentation and sample responses to understand available data structures.
Extraction Logic Generation
For each user query, the agent generates appropriate API calls with filters, pagination, and field selection.
Response Transformation
JSON/XML responses are flattened into tabular format with inferred column types.
Example: Gong Integration
Gong provides conversation intelligence — recordings, transcripts, and AI analysis of sales calls. AstroBee can extract:| Gong Data | Semantic Entity | Use Cases |
|---|---|---|
| Call recordings | SalesCall | Call volume, duration trends |
| Transcripts | CallTranscript | Keyword analysis, talk ratio |
| Sentiment scores | CallSentiment | Deal health indicators |
| Deal intelligence | DealSignal | Risk identification |
Sample Queries Enabled
- “Which reps have the highest talk-to-listen ratio?”
- “Show deals where competitor X was mentioned in calls”
- “Compare call sentiment trend vs. pipeline progression”
Walkthrough: “Show calls where sentiment was negative”
Results transformed to table
| call_id | duration | sentiment | deal_id |
|---|---|---|---|
| c_123 | 45min | -0.3 | opp_abc |
| c_456 | 30min | -0.5 | opp_def |
Example: Google Calendar Integration
Google Calendar contains meeting data that reveals collaboration patterns and time allocation. AstroBee can extract:| Calendar Data | Semantic Entity | Use Cases |
|---|---|---|
| Events | Meeting | Meeting load analysis |
| Attendees | MeetingParticipant | Collaboration patterns |
| Response status | MeetingResponse | Engagement metrics |
| Recurring events | MeetingSeries | Time commitment analysis |
Sample Queries Enabled
- “How many hours per week do sales reps spend in meetings?”
- “Which team members have the most external meetings?”
- “Show my meeting load trend over the past quarter”
API Source Security Model
API sources follow the same credential delegation model as warehouses:- Per-user OAuth tokens — Each user authenticates with Gong/Google using their own account
- Native permissions enforced — If a user can’t access certain calls in Gong, AstroBee can’t extract them
- Scoped access — OAuth scopes limit AstroBee to read-only data access
- Token encryption — API tokens stored with same AES-256 encryption as warehouse credentials
- Audit trail — All API extractions logged with user identity and data accessed
Rate Limiting & Caching
- AstroBee respects API rate limits (e.g., Gong: 10 requests/second)
- Extracted data cached briefly (5–15 minutes) to avoid redundant API calls
- Cache invalidated on user request or data freshness requirements
- Large extractions paginated automatically to avoid timeouts