PragerU <> OneAI: Integrations
Date: 2026-03-11 | Duration: 23.719999313354492 min | Account: prageru
External attendees: patrickm@prageru.com, travisg@prageru.com
Summary
The team discussed a phased strategy for integrating call data into their CRM, beginning with manual CSV exports to ensure flexibility and accommodate future changes. API URLs were shared, enabling segmented data downloads while requiring historical call logs for comprehensive reporting. Phone numbers were confirmed as unique identifiers for synchronization, simplifying contact tracking. The meeting also highlighted the need for real-time data exploration and clarified telephony system details for future discussions. Overall, the plan aims for balanced short-term usability and long-term efficiency in data integration.
Key Points
π Phased Data Integration Approach: Start with manual CSV exports, exploring automation later for flexibility and efficiency. π API URLs with Agent Keys Shared: Multiple API URLs provided for filtered data, limited to 10,000 contacts per request. π Historical Call Log Requirement: Running log of all contact attempts prioritized for comprehensive reporting and CRM notes. π Data Mapping with Phone Numbers: Phone numbers agreed as unique identifiers for simplifying data synchronization processes. π₯ Real-time Data Review Conducted: Live data exploration via screen sharing helped clarify formatting and ensure completeness.
Overview
- Phased Data Integration Approach: Start with manual CSV exports, exploring automation later for flexibility and efficiency.
- API URLs with Agent Keys Shared: Multiple API URLs provided for filtered data, limited to 10,000 contacts per request.
- Historical Call Log Requirement: Running log of all contact attempts prioritized for comprehensive reporting and CRM notes.
- Data Mapping with Phone Numbers: Phone numbers agreed as unique identifiers for simplifying data synchronization processes.
- Real-time Data Review Conducted: Live data exploration via screen sharing helped clarify formatting and ensure completeness.
- Telephony System Follow-up Planned: Discussion on telephony details deferred until after data integration issues are resolved.
Action Items
Daniella Block Resend the full set of API URLs (answered, transferred, all contacts) and instructions to Patrick and Travis (08:48) Confirm with Roy Sagi whether contact IDs are included in historical data uploads and coordinate adding them if missing (17:26) Develop an API providing a running log of every call attempt as separate entries ordered by call time (20:49) Retrieve information about PragerUβs telephony system from Emily Rachel and share with OneAI team (22:31) Add Travis Gordon to the PragerU Slack channel for communications (22:40)
Patrick Morrow Share API key for Cassandra agent with Travis via Slack (12:04) Clarify internally with Roy Sagi on historic inclusion of contact ID data (17:26)
Michael Gur Work with Roy on creating the enhanced API supporting granular call attempt logs and notify the team when ready (20:57)
Travis Gordon Begin manual downloads and reviews of data via API URLs for initial analysis and mapping (05:00) Test and validate data format and fields with OneAI team (16:15) Share screen and collaborate during data testing sessions (13:28)