Salesforce + Eru
Connect your enterprise CRM to see how accounts, opportunities, and custom objects map to your billing, support, and product data. Eru handles Salesforce complexity.
What Eru reads from Salesforce
Eru connects to Salesforce via OAuth and queries data through the REST and SOQL APIs. It discovers your specific org configuration—custom objects, fields, record types—rather than assuming a standard setup.
Accounts
Account records with all standard and custom fields. Industry, size, owner, hierarchy, and any custom fields you've added. Eru maps accounts to customer entities across your stack.
Contacts
Contact records with roles, engagement history, and relationships to accounts. Eru identifies champions, decision-makers, and stakeholder changes.
Opportunities
Pipeline and closed-won opportunities with stage, amount, products, and forecast data. Eru reconciles opportunity values against actual billing data.
Custom objects
Subscriptions, entitlements, cases, custom entities—whatever you track in Salesforce becomes part of the Truth Map. Eru discovers relationships between standard and custom objects automatically.
Activities and tasks
Logged activities that indicate engagement levels. Eru uses activity patterns to assess relationship health and identify accounts going quiet.
Salesforce is uniquely complex
No two Salesforce orgs look alike. Years of customization, multiple admins, acquired companies merged in—the data model becomes unique to each organization.
Schema discovery
Eru explores your org's metadata to understand the actual structure. Custom objects, custom fields, record types, page layouts—all mapped to understand what data exists and how it relates.
Semantic understanding
Field names don't always match their meaning. "ARR__c" might be annual revenue or something else entirely. Eru samples data and analyzes patterns to understand what each field actually represents.
Relationship mapping
Salesforce relationships—lookups, master-details, junction objects—create a web of connections. Eru traces these relationships to build a complete picture of your data model.
Common use cases
Pipeline-to-revenue reconciliation
Compare closed-won opportunity amounts to actual revenue in billing. Catch discrepancies between what sales recorded and what customers pay.
Account health scoring
Combine CRM data with support tickets, product usage, and billing status. Surface accounts at risk based on signals across all systems.
Renewal forecasting
Cross-reference contract renewal dates with usage trends and support patterns. Predict which renewals are at risk before the conversation happens.
Data quality monitoring
Ensure Salesforce data stays consistent with source systems. Catch when accounts get out of sync with billing or product records.
Setup
1. Connect via OAuth
Eru uses Salesforce's Connected App OAuth flow. You authorize read access to your org's data. Write access is never requested.
2. Eru explores your org
The agent queries org metadata to discover objects, fields, and relationships. It samples data to understand patterns and identify key entities.
3. Review proposed mappings
Eru proposes how Salesforce entities map to your other systems. Accounts map to billing customers map to product organizations. You review and approve.
4. Continuous monitoring
Once mapped, Eru tracks schema changes in your org. New fields, modified objects, relationship changes—all surfaced so mappings stay current.
Permissions required
Eru requests read-only access to:
- Standard objects (Accounts, Contacts, Opportunities, etc.)
- Custom objects and fields
- Metadata describing your org's schema
- SOQL query execution for data sampling
Eru never writes to Salesforce. It reads data for analysis and mapping only.
Other integrations
Connect Salesforce to Eru
Unify your enterprise CRM with the rest of your data stack.