Apollo Update Contact Column No Longer Shows Custom Fields to Update
noticed that apollo's "update contact" column no longer lists custom fields as viable options to update with clay data. is that a temporary bug or did something change?
noticed that apollo's "update contact" column no longer lists custom fields as viable options to update with clay data. is that a temporary bug or did something change?
The available documentation doesn't specifically address changes to custom field options in Apollo's "update contact" column. [1] Our sources show that the Apollo update contact integration is still active and allows updating existing contacts, but they don't detail the specific field mapping options or recent changes to custom field availability. [2]
There have been some recent changes to Apollo integrations - for example, Apollo now requires using "Enrich Person from Apollo" to extract emails instead of showing them directly in search results. [3] This suggests Apollo has been making updates to their API or integration requirements.
Can you share what specific custom fields you were trying to update, or maybe a screenshot of what you're seeing in the column setup?
If you still need help with the Apollo update contact column or have more details about the custom fields you're trying to update, I'm here to assist. Would you like to provide more information about what you're trying to resolve?
I am also having this issue, where there once was a "custom fields" input for the Create or Find Contacts in Apollo, it is not there anymore. This is recent too as I was using this function just 3 days ago.
Since multiple users are experiencing this issue and it was working just days ago, this points to a recent change in Apollo's API or integration requirements.
Can you try refreshing the integration column or recreating it to see if the custom fields option reappears?
I understand this recent change with the Apollo integration is frustrating, and I’m here if you need more help troubleshooting it. Would you like to share any additional details or try other steps to resolve this issue?
I have tried recreating it, and it does not appear. Is there a solution to sending custom fields from clay to apollo?
Since the custom fields option disappeared from Apollo's integration, you can use our HTTP API integration as a workaround to send custom fields to Apollo. [1]
Set up the HTTP API integration and describe what you want to accomplish - like "Create or update a contact in Apollo with custom fields including name, email, and [your specific custom fields]." You can also paste Apollo's API documentation link to help the AI assistant configure it properly.
Alternatively, you can manually configure the HTTP API by setting the endpoint to Apollo's contacts API, adding your Apollo API key in the headers, and structuring the JSON body to include both standard fields and your custom field data. [2]
What specific custom fields are you trying to send to Apollo so I can help you set up the HTTP API configuration?
If you still need help with sending custom fields to Apollo using the HTTP API, I’m here to assist. Would you like to provide more details about the specific custom fields you want to send or any other challenges you’re facing?
thanks - I've already implemented an HTTP API workaround but the native Apollo feature for updating custom fields was a lot more convenient.
Yeah, totally get it - the native Apollo custom-field mapping was way nicer.
Right now, we don’t have anything documented that explains why the “custom fields” input disappeared from Apollo actions like Update contact / Create or Find Contacts, or whether it’s a temporary bug vs a deliberate change. [1]
Is that what you were looking for?
I’m sorry the native Apollo custom field feature is no longer available and understand how inconvenient that must be. Would you like to share more about your current setup or any other issues you’re encountering so I can assist further?
The typed_custom_fields parameter is still available in Apollo's API, I don't know why it is no longer displayed as an input field in Clay. Could this be a clay UI issue?
You're right that Apollo's typed_custom_fields parameter is still available in their API. Our documentation doesn't explain why the custom fields input disappeared from Clay's Apollo actions, so this could indeed be a UI issue on our side. [1]
Since you've already got the HTTP API workaround running, that's the current supported path for sending custom fields to Apollo. But given that the parameter still exists in Apollo's API, this might be something our team needs to look into. [2]
Before we dig deeper, have you tried using Sculptor (the AI tool in the top-right corner) to see if it can help rebuild the Apollo action with custom fields exposed?
yes I have, sculptor was not helpful, it kept telling me to input my custom fields in the "custom fields" input which is not shown