You must connect your Apollo account before using this node. See Apollo Integration for setup instructions.
Configuration
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: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.
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, If/Else 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).