Troubleshooting Email Unlock Issue in Apollo Job Title Feature

Noor M. · 2025-10-20 01:35:08.354766+00

I am using Apollo, Find people using Job title feature. I have my own Apollo API key and we have connected successfully as well It keeps showing me Email unlocked @ domain . Com for the email column Other details like first name, last name, LinkedIn url are showing up fine What could be the issue.

Troubleshooting Email Unlock Issue in Apollo Job Title Feature | Clay

Clay Support
APP
·
·
Apollo now requires the "Enrich Person from Apollo" function to retrieve actual email addresses. The "Find People at Company By Job Title" action only returns "email_not_unlocked@domain.com" as a placeholder.
To get the real email:
1.
Use “Find People at Company By Job Title” to find contacts.
2.
Use the “write to table” function to extract results into a new table.
3.
In the new table, run “Enrich Person From Apollo” and map relevant fields (excluding email).
4.
The actual email will appear after enrichment.
API limits still apply [1].
Clay Support
APP
·
·
Was that helpful?
Noor M.
·
·
But I want to keep the emails in the same table. Wouldn't that add complexity to my workflow
Clay Support
APP
·
·
To retrieve actual email addresses from Apollo and keep them in the same table:
1.
Use “Find People at Company By Job Title” to get initial results (emails will show as email_not_unlocked@domain.com).
2.
In the same table, add a new enrichment column using “Enrich Person From Apollo”.
3.
Map fields like first name, last name, and company domain — do not map the email column.
4.
Run the enrichment; real emails will populate in the same table.
This avoids extra tables and keeps your workflow simple. [1]
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you still need help with keeping emails in the same table or have any other questions about your Apollo workflow, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any challenges you’re facing?
Noor M.
·
·
Ok everything is done I am able to see emails But when I map first name or last name to existing columns it says Dag is cyclical
Clay Support
APP
·
·
The "Dag is cyclical" error occurs when mapping fields like first name or last name back to the same table that triggers the enrichment, creating a circular dependency.
To fix this:
Avoid mapping output fields back to the columns that trigger the enrichment.
Use separate columns for input and output to prevent loops.
Set conditional run rules (e.g., "Only run if") to ensure one-way data flow [1].
This maintains a linear workflow and prevents cycle errors .
Clay Support
APP
·
·
Is that what you were looking for?
Noor M.
·
·
In this case What conditional run rule can I apply
Clay Support
APP
·
·
To prevent the "Dag is cyclical" error when mapping first name or last name in your Apollo enrichment:
Do not map output fields back to the same columns used as inputs for the enrichment.
Use a conditional run rule like: Only run if [Enriched Email] is empty AND [First Name] is not empty This ensures the enrichment only runs when needed and avoids circular logic [1].
You can also use Clay.getCellStatus(#{{field_id}}) in a formula column to control execution flow more precisely .
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you still need assistance with setting up conditional run rules or have other questions about your Apollo workflow, I’m here to help. Would you like to share more details about what you’re trying to resolve or understand?
Noor M.
·
·
Thanks
Clay Support
APP
·
·
You're welcome. If you have any more questions or need further assistance, feel free to ask.

39 comments