Skip to main content
Automate.ax connects Apollo through OAuth or an API key. OAuth requests the exact scopes used by each action. API-key requests act in the connected Apollo workspace; Apollo attributes them to the workspace’s oldest active administrator. apollo.listContactDeals, apollo.searchCalls, apollo.createCall, apollo.updateCall, and apollo.getEmailStats require a master API key. Apollo rejects OAuth access tokens for contact deals, omits the call scopes from OAuth app registration, and doesn’t support OAuth for email stats. Apollo does not expose a lifecycle webhook subscription API with a stable event payload. Apollo Workflows can send a user-configured webhook for people and company events, so receive those deliveries with onHttpRequest and validate the workflow’s body in your automation. Automate.ax does not create, reconcile, or label those workflow webhooks as managed Apollo triggers.
automations/apollo-workflow-webhook.automation.ts
Use getApolloApi(account) inside a custom account-backed action for an uncovered Apollo REST endpoint. Paths are relative to https://api.apollo.io/api/v1/; queries use provider-native names, and every response requires a Zod schema. Failures throw ApolloApiError with HTTP status, provider code and message, and retry delay. Apollo rate limits apply per workspace, endpoint, and minute, hour, or day. A 429 response includes the retry delay when available. The synchronous analytics report is limited to five requests per hour. The deprecated GET /typed_custom_fields endpoint is intentionally excluded; use apollo.listFields({ source: "custom" }). See Apollo’s API overview, authentication guide, OAuth flow, rate limits, and status codes.