Skip to main content
The Apollo Enrichment node pulls additional contact and company data from Apollo into Conversion as contacts pass through a workflow. You map Apollo fields — such as job title, company size, LinkedIn profile, or company domain — to your own Conversion variables, and the node fills them in automatically during each workflow run.
You must connect your Apollo account before using this node. See Apollo Integration for setup instructions.

​
Configuration

SettingDescription
Apollo fieldChoose which Apollo field to pull data from. See available fields below.
Variable to updateSelect an existing Conversion variable or create a new one. This is where the Apollo data will be written.
Overwrite toggleWhen off (default), Apollo data only fills empty fields. When on, Apollo data replaces existing Conversion values.
You can add multiple variable-to-field mappings within a single Apollo Enrichment node to pull several data points at once.

​
Available Apollo fields

Apollo fields are organized into two categories:
CategoryPrefixExamples
Person fields”Contact”First name, Last name, Job title, LinkedIn URL
Organization fields”Company”Company name, Company annual revenue, Company size, Company domain
Conversion provides Apollo with the contact’s email address and queries the requested data. The email address must be present on the contact record for enrichment to run.

​
Behavior

  • The node attempts enrichment using the contact’s email address as the primary identifier.
  • If no email address is present on the contact, the step is skipped entirely.
  • If the overwrite toggle is off and the target variable already has a value, that mapping is skipped.
  • If Apollo does not have the requested data for a contact, no data is changed and the contact continues through the workflow.
  • Enrichment results are written to the mapped variables before the contact advances to the next node.
If the Apollo enrichment fails for a contact in a workflow (e.g., due to an API error or expired credentials), the workflow will fail for that contact. Verify your Apollo connection is active before activating workflows that use this node.

​
Best practices

  • Prioritize strong identifiers. Ensure the contact’s email address is populated before the Apollo Enrichment node runs. Without it, enrichment is skipped entirely.
  • Keep overwrite off for authoritative fields. For fields like name or mailing address where your internal data should take priority, leave the overwrite toggle off so Apollo only fills gaps.
  • Place enrichment early in the workflow. Position the Apollo Enrichment node near the beginning of your workflow so that downstream steps — Send Email, Slack Messages, Webhooks, True/False Branch — always operate on the most complete data available.
  • Combine with Magic Enrichment. Use Magic Enrichment after Apollo Enrichment to further classify or standardize the data Apollo returns (e.g., normalize Apollo job titles into standardized personas).