Apollo
Paminga's Apollo integration brings Apollo's people-data into your Paminga contacts in two ways:
- Enrich with Apollo: fill in empty fields on contacts you already have. Run it as an Action from workflows, forms, imports, and Action Sets, or on a single contact from Contact Details.
- Import from Apollo: pull any list you've saved in Apollo into Paminga as contacts, with the same field mapping and Actions you'd expect from a CSV import.
Both use one field mapping, configured once for your account.
Paminga only reads from Apollo. Nothing is written back to your Apollo account.
Enrich Records with Apollo
You will find Paminga's Enrich with Apollo Action available wherever Actions appear.
This means you can trigger Apollo enrichment from:
- Action Sets: reusable actions that can be leveraged from multiple places in Paminga
- Form Builder: trigger actions when a form is submitted
- LinkedIn Lead Forms
- Calendly Event Forms
- CRM Sync Actions: trigger actions as leads or contacts are synced to Paminga from your integrated CRM
- CSV Imports: trigger actions as contact records are imported from your .csv file
- Drip Series & Workflow Goals: trigger actions when a goal is achieved
- Workflow Actions: trigger actions as leads/contacts progress through workflows
- Lead Scoring Thresholds: trigger actions when a prospect's lead score crosses a threshold
- Lead Stage Change Actions: trigger actions when a lead's stage changes
- Opportunity Stage Change Actions: trigger actions when an opportunity's stage changes
- Workato Recipes
- Zapier Zaps
Import Lists from Apollo
Any list you've saved in Apollo can be imported into Paminga as contacts. The import works the same way as a CSV import: choose the source, confirm where each field lands, choose the Actions Paminga should take for every contact, and start it.
There is no upload and no file to format. Paminga reads the list straight from Apollo.
You'll find it under Contacts & Accounts → Import from Apollo. Connect Apollo first if you haven't.
Choose List
Pick the Apollo list to import. The picker searches by name, and the sort control orders your lists by name, size, or date created or updated.
The contact count beside each list comes from Apollo's own cached count. It's there to help you recognize the right list, not to promise an exact import size.
Map Fields
This step shows the Apollo field mapping for your account: Apollo's standard person fields on top, your Apollo custom fields below. Confirm it, adjust anything you like, and click Next to save it and move on.
The mapping is per account, not per import. Changes you make here also apply to the Enrich with Apollo Action.
Need a Paminga field that doesn't exist yet? New Contact Field creates one and makes it available as a target right away. New Account Field creates one too; map it on the Apollo field mapping screen, since an import writes contacts, not Accounts.
Actions
Choose what Paminga should do with every contact the import creates or updates. This is the same Actions step you know from the CSV import:
- An Action Set, if you have one for this purpose
- Global Actions, which run for every imported contact. Adding them to a Marketing List is the common one
- Conditional Actions, which run only for imported contacts that meet conditions you choose
Actions run as each page of contacts arrives, not after the whole list is done.
Click Save & Import Contacts to start.
Import Contacts
Your import is queued and runs in the background. Contacts appear as they're imported, a page at a time, and any Actions you configured run for each contact as it arrives. From here you can view your contacts or import another list.
What Happens During an Import
Contacts are matched by email address. A person in the list whose email Apollo doesn't provide is skipped. Apollo only supplies the email addresses your Apollo plan has unlocked.
New contacts get every mapped value. Existing contacts get only the mapped fields that are currently empty. An import never replaces a value you've since corrected by hand.
The contact's Account is resolved from Apollo's Company. Paminga links the contact to an existing Account of that name or creates one. It does not write Account field values; that's what Enrich with Apollo is for.
Every imported contact has the source "Apollo Down Sync", so you can segment on it.
Importing the Same List Again
Every import is a fresh one. Choose the list again and you get a clean Actions step, so a list whose membership has changed in Apollo can be re-imported as often as you like. Contacts already in Paminga are updated in place, matched on email, and new members are created.
Limits
An import reads up to 500 pages from Apollo, roughly 50,000 contacts. A list larger than that stops there and is reported as an error rather than a completed import, so you know the tail was not fetched.
One import of a given list runs at a time. Starting it again while it's still running is refused.
Connect Paminga to Apollo
You'll need a Paminga user with the Integrations permission, and an Apollo master API key. Apollo rejects scoped keys for the list and contact endpoints Paminga reads, so a scoped key will not connect.
- In Apollo, go to Settings → Integrations → API and copy your master API key.
- In Paminga, go to Settings → Account → Integrations and click Connect on the Apollo card.
- Paste the key and click Connect Apollo.
Paminga checks the key against Apollo before storing it. A key Apollo rejects is never saved, and the card tells you why: either Apollo refused it (it isn't a master key), or Apollo couldn't be reached and you should try again.
Once connected, the Apollo card reads "Paminga is connected to Apollo" and gains a Field mapping link and a Disconnect button.
Disconnecting
Disconnect removes the stored key. Your field mapping is kept, so reconnecting later restores it as it was.
Mapping Fields from Apollo to Paminga
The field mapping decides which Apollo fields are written to which Paminga fields. It is set once for your account and shared by every Apollo surface: the list import, the Enrich with Apollo Action, and the on-demand enrich on Contact Details. Save it in one place and all three use it.
Open it from the Field mapping link on the Apollo card, or from the Map Fields step of an Apollo import.
Standard fields are pre-mapped, but Paminga won't start an import or an on-demand enrich until a mapping has been saved. Open the mapping screen, review it, and click Save Mapping. That's the one setup step.
Standard Fields
Apollo's standard person fields are mapped to their Paminga counterparts for you: Email, First Name, Last Name, Title, City, State, Country, LinkedIn URL, Facebook URL, and Time Zone. Apollo's Company always resolves the contact's Account. Every Paminga contact belongs to one.
You can turn any standard field off by setting it to Do Not Map. Anything set to Do Not Map is skipped.
Two standard fields are off by default: Mobile Phone and Work Phone. Apollo charges extra credits to reveal phone numbers, so they're only written when you both map them here and ask for a reveal on the Enrich with Apollo Action.
Custom Fields
Every custom field you've defined in Apollo is listed. Map each one to a Paminga custom field of the same type: an Apollo date field lists only Paminga date fields, a picklist lists only drop-downs, and so on. That keeps the data valid on arrival.
Need a Paminga field that doesn't exist yet? Use the + beside the dropdown to create one on the fly. It's available as a target immediately.
Account Fields
Apollo returns the contact's employer in the same lookup as the person, so Account fields cost nothing extra. Company Website, Phone, Employees, Revenue, LinkedIn URL, Description, SIC Code, and Industry are mapped to the Account's standard fields by default. Industry is matched by name against the industries already in your account; Paminga never invents one.
Additional company data (Domain, Founded Year, Total Funding, Latest Funding Stage, Technologies, Keywords, Ticker) and any account-level custom fields from Apollo can be mapped to Account custom fields.
Account fields are written by Enrich with Apollo. An Apollo list import creates or links the contact's Account by company name but does not write Account field values.
Existing Values
Whether Apollo replaces a value a record already has is not decided here. It's a setting on the Action or enrich that runs, and it's off by default, so Apollo fills empty fields and leaves your data alone.
Apollo Credits
Reading your Apollo lists costs nothing. Every contact Apollo matches during an enrichment or import spends Apollo credits, and revealing phone numbers spends more. Paminga tells you before either happens, and never retries a paid call on its own.
