Documentation Index
Fetch the complete documentation index at: https://hc.pillargtm.com/llms.txt
Use this file to discover all available pages before exploring further.
Data Sources
PILLAR ingests data from CRM systems, email/calendar platforms, product analytics tools, support ticketing systems, NPS/sentiment platforms, district intelligence providers, and internal computation engines. PILLAR integrates with 20+ tools.
CRM Connectors
Each org can connect one CRM provider.
| Provider | Auth | Objects | Sync Cadence | Direction |
|---|
| Salesforce | OAuth 2.0 | Account, Contact, Opportunity, Lead, Task | Every 15 min (incremental) | Inbound + outbound score push |
| HubSpot | OAuth 2.0 | Company, Contact, Deal, Ticket | Every 15 min (incremental) | Inbound + outbound score push |
| Dynamics 365 | OAuth 2.0 (Azure AD) | Account, Contact, Opportunity, Lead, Case | Every 15 min (incremental) | Inbound + outbound score push |
All three CRM connectors sync on a 15-minute incremental cadence and support score write-back — PILLAR pushes computed health, risk, and priority scores back to custom fields in your CRM so reps see PILLAR intelligence without leaving their existing tools.
Field Mapping
CRM field mappings are customizable per org. Each mapping specifies the PILLAR field, CRM field, transform type (direct, lookup, formula, or picklist map), and sync direction (inbound, outbound, or bidirectional). Picklist value translations are also supported.
Email and Calendar
Per-user authorization required.
| Provider | Auth | Data | Sync Cadence |
|---|
| Google Workspace | OAuth 2.0 (per-user) | Email metadata, calendar events | Every 5 min |
| Microsoft 365 | OAuth 2.0 (per-user) | Outlook metadata, calendar events | Every 5 min |
Email body content is never stored. Only metadata (sender, recipient, timestamp, subject line) is captured as activities.
District Intelligence (Starbridge)
Starbridge.ai provides 120+ buyer attributes for school districts, higher education institutions, and government entities.
| Data Category | Examples | Sync |
|---|
| Buyer Attributes | Budget, enrollment, tech spend propensity, AI adoption | On-demand + webhook |
| Contacts (Job Changes) | Departures, new hires, promotions | Webhook (real-time) |
| Contracts | Public contract records between buyers and vendors | On-demand |
| Purchase Orders | Line-item procurement records | On-demand |
| Conferences | EdTech conferences with attendee/vendor data | Periodic |
| RFPs | Active bids and solicitations | Webhook (real-time) |
| Documents | Board minutes, strategic plans | On-demand |
Notifications
| Provider | Type | Usage |
|---|
| Slack | Real-time | Signal routing to channels, weekly digest |
| Email | Digest | Weekly summary, critical signal alerts |
| Microsoft Teams | Real-time | Signal routing (alternative to Slack) |
Product Usage Connectors
PILLAR ingests product analytics data to power adoption scoring, usage trend analysis, and renewal risk detection.
| Provider | Auth | Data | Sync Cadence |
|---|
| Pendo | API Key | Feature adoption, visitor sessions | Every 15 min |
| Mixpanel | API Key + Secret | Event volume, funnel conversion | Every 15 min |
| Amplitude | API Key + Secret | Behavioral events (US/EU endpoints) | Every 15 min |
| Segment | API Token + Workspace | CDP event forwarding | Every 15 min |
| Heap | API Key | Auto-captured analytics | Every 15 min |
| Mode Analytics | API Token + Secret + Workspace + Report Token | BI report data | Every 15 min |
Product usage data feeds the usage_trend variable in the Renewal Risk model and the Product Adoption component of the Account Health score. When product usage snapshots are available, PILLAR computes adoption percentage deltas automatically.
Support Ticketing Connectors
Support ticket data feeds the support_burden variable in the Renewal Risk model.
| Provider | Auth | Data | Sync Cadence |
|---|
| Intercom | OAuth 2.0 | Conversations, tickets, CSAT scores | Every 15 min |
| Zendesk | API Token + Subdomain | Tickets, SLA metrics, CSAT scores | Every 15 min |
| Freshdesk | API Key + Subdomain | Multichannel tickets | Every 15 min |
HubSpot Service Hub and Salesforce Service Cloud ticket data is also ingested through the CRM connectors listed above. PILLAR normalizes all ticket sources into a unified support burden score.
Customer Sentiment / NPS Connectors
NPS and satisfaction data flows into the nps_health component of the Renewal Risk model and the Satisfaction component of the Account Health score.
| Provider | Auth | Data | Sync Cadence |
|---|
| Wootric (InMoment) | OAuth 2.0 (Client ID + Secret) | NPS scores mapped to accounts.nps_score, feeds Health Score Satisfaction component | Every 15 min |
| Delighted | API Key | NPS/CSAT mapped to accounts.nps_score | Every 15 min |
Computed Sources (PILLAR Engine)
| Computation | Refresh |
|---|
| Scoring Engine | Continuous |
| Signal Generation | Periodic |
| Forecast Snapshots | Daily |
| Pipeline Cohorts | Daily |
| Org Metrics | On-demand |
| TAM/SAM Calculations | On settings change |
For step-by-step connection instructions, see the Connector Setup Guide. For field-level mapping details, see the Field Mapping Reference.