Apollo
What’s supported
Supported actions
The Apollo connector supports:
- Read Actions, including full historic backfill. Please note that incremental read is not supported, a full read of the Apollo instance will be done for each scheduled read.
- Write Actions.
- Proxy Actions, using the base URL
https://api.apollo.io.
Supported Objects
The Apollo connector supports reading from the following objects:
- emailer_campaigns (sequences)
- accounts
- account_stages
- contacts
- contact_stages
- opportunities (deals)
- opportunity_stages (deal stages)
- email_accounts
- labels (lists and tags)
- tasks
- typed_custom_fields (custom fields)
- users
Note: Due to limitations in the Apollo API, Ampersand can read a maximum of 50,000 records each time for Accounts, Contacts, or Tasks.
The Apollo connector supports writing to the following objects:
Example integration
For an example manifest file of an Apollo integration, visit our samples repo on Github.
Before You Get Started
Creating an API key for Apollo
Click here for more information about generating an API key for Apollo. The UI components will display this link, so that your users can successfully create API keys.
Using the connector
This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.)
To start integrating with Apollo:
- Create a manifest file like the example.
- Deploy it using the amp CLI.
- If you are using Read Actions, create a destination.
- Embed the InstallIntegration UI component. The UI component will prompt the customer for an API key.
- Start using the connector!
- If your integration has Read Actions, you’ll start getting webhook messages.
- If your integration has Write Actions, you can start making API calls to our Write API.
- If your integration has Proxy Actions, you can start making Proxy API calls.