Apollo
Paminga's Apollo integration brings Apollo's people-data into your Paminga contacts in two ways:
- 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.
- 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.
Both use one field mapping, configured once for your account.
Paminga only reads from Apollo. Nothing is written back to your Apollo account.
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.
Field Mapping
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.
Where Enrichment Shows Up
Every contact Apollo writes to gets an "Enriched with Apollo" entry in its Activity Stream naming the fields that were filled in, and an entry under Data Enrichment → History showing the values before and after, so you can see exactly what Apollo changed and when.
