By name: vendor-integrations description: How Apollo.io uses key third-party vendors — Snowflake, Salesforce, and others
Apollo Vendor Integrations
Snowflake (Data Warehouse)
- What we use it for: Primary data warehouse for analytics and data science
- Who owns it: Data Infrastructure team
- Access: Via Okta SSO — request through access-requests skill
- Key databases: [list actual database names]
- Do not: Run large unoptimized queries on production without checking with #data-infra
- Support: #data-infra
Salesforce (CRM)
- What we use it for: Sales pipeline, customer records, RevOps reporting
- Who owns it: RevOps team
- Access: Request via IT — manager approval required
- Key objects: Lead, Contact, Account, Opportunity, [custom objects]
- Do not: Modify records or run bulk updates without RevOps sign-off
- Support: #revops or #it-help
Okta (Identity / SSO)
- What we use it for: SSO for most internal and SaaS tools
- Who owns it: IT/Security
- Provisioning: New hires auto-provisioned; app access requires request
- Support: #it-help
[LaunchDarkly / Feature Flags Tool]
- What we use it for: Feature flags and gradual rollouts
- Who owns it: Platform Engineering
- Access: Engineers can request project access via #platform
- Conventions: See the deploy-process skill for naming conventions
- Support: #platform
[PagerDuty / On-Call Tool]
- What we use it for: On-call alerting and incident escalation
- Who owns it: Platform Engineering / IT
- Access: Request via #it-help; team leads configure rotations
- Support: #platform or #it-help
Adding a New Vendor
New vendor integrations must go through:
- Security review (see Security agent)
- Legal/procurement approval
- IT provisioning setup
Contact #security and #procurement to start the process.