.png){kind=logo}
Hello Support, is there a way to send data back into Apollo?
Hello Support, is there a way to send data back into Apollo? I would like to send back data into a custom field that I create within Apollo
Hello Support, is there a way to send data back into Apollo? I would like to send back data into a custom field that I create within Apollo
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Hey Janine, thanks so much for reaching out! Yes, there is definitely a way to send data back to Apollo. Could you let me know more about your use case? Are you looking to add the data as a contact in Apollo, or perhaps include them in a sequence? What exactly are you hoping to achieve with this integration? There are various ways to send data back to Apollo, often involving their HTTP API. You can explore more about these use cases here. Let me know how I can assist further! 😊
Hi Owen C., thanks for your reply. I am looking to do possibly do both. Here is my use case. I am collecting leads from a source, then enriching them with Apollo contact ID if it exists. once I have done that, I would like to find them in apollo, append data to a custom field that I created which is currently in Clay and then add them to a sequence in Apollo. Do you have any templates that do something similar to that. I would like to take a look at how they are accomplishing that.
Also, if they do not exist in Apollo, I want to add them as a contact in apollo
Let me clarify, if I do not already own the contact within Apollo so that I can append data to it, I would like to add the contact to Apollo and then append the data to it.
So in my case, I already have most of the Apollo contact ID's to append data to, those that do not have an ID within Clay, will need to be created as a new contact within Apollo.
Apologies for the delay! Your workflow makes perfect sense. Just to clarify and summarize: 1. Leads are being collected from a source. 2. If the lead already exists in your Apollo list (verified using the 'Find Account by ID' enrichment), you'll enrich the contact and update their information in Apollo. 3. If the lead is not in your Apollo account, you'll first add the contact to Apollo, then enrich their information and send that data to Apollo. Unfortunately, we do not have any templates on this workflow specifically however I'd love to help you make this happen! The first step is to set up the flow so that when an inbound lead arrives in your Clay table, it will immediately check whether the lead already exists in your Apollo account. Questions for you: 1. When the lead first arrives in Clay, whether this lead exists in Apollo or not, you’d like to enrich them to find updated data, correct? 2. What specific data points are you most interested in finding and sending to Apollo? 3. Also, are you hoping to add this contact to a sequence? or simply update the contact as it lives in Apollo? (if its the latter, it may be more effective to update this information in your CRM, would love to chat about this)
Owen C. Answers to your Questions:
I don't need to enrich them, I am using AI to figure out what their pain point was by looking at what page they visited on our website. This data is already in the table.
Do not need more data points
Firstly, I would like to update the contact in Apollo then once they are updated, add them to a sequence.
Gotcha! Perfect! So first step is going to be checking if this person exists in your Apollo account. To do this we will use the Search Contacts API from Apollo. This will be done through an HTTP API feature in Clay, and be setup like the following menu (image included): Once this is setup successfully, we'll know whether a contact exists in Apollo and then can continue moving forward in the workflow :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1203387191/ceb60b87b63049dd8807efd7728b/CleanShot+2024-10-03+at+17_41_34%402x.png?expires=1727993700&signature=12b960bac820ed0af201140363ba420c74bc8b85952beae884a2d21cca777327&req=dSInFcp2moBWWPMW1HO4zdgWlXTx82%2FXIlRcmXI1Q1K8plgvh8aKklrwvSnk%0Amp2a%0A
Great, let me set that up and see if it works because currrently the Apollo ID I am getting is incorrect. I will try it and let you know. Thanks for your help with this.
Amazing! Of course, let me know how it goes!
Looks like I figured it out, the Authorization needed to be
X-Api-KeyInstead
Hey Janine! Great catch—apologies for the miscommunication! To clarify, only rows with a Contact ID in the 'Apollo Contact ID' column are linked to contacts in your Apollo account. This is an important distinction! Now that we’ve identified which contacts are in your account, are you looking to update their information in Apollo based on the pain points that apply to them depending on the page they visited? or would you also like to update information like name, industry, email, etc?
Owen C. No worries, you are a great help for me. Before I update any info, I don't want to leave any lead behind. For those that do not exist in Apollo or that I have not purchased, Can I either purchase them and if not, can I add them as a new contact. Either or both would work in this instance.
I want to make sure that before I move on to the next step, that I have them all in Apollo. Then we can once I have the contact ID. I think we will be able to update them in Apollo.
Sounds great! I'm glad to hear it! With Apollo, you don't purchase leads directly—you gain access to a large database of contacts and companies that you can search through. If someone in this flow isn’t already in your Apollo list, we can add them using the Create a Contact' API. This API works similarly to the previous one, but in this case, you'll need to include all the data points you'd like to associate with the person in the body section of the API request. Be cautious when using this API, as it doesn't check for duplicate contacts. If a person already exists in your database and gets sent through this API, it will create a duplicate contact in your list. To prevent this, we can set up a conditional formula in the HTTP API column to run only when the 'Apollo Contact ID' column is empty. This way, it ensures the API is only triggered for new contacts.
Sounds great, I am going to do that now. I will make sure to only run it when there is no contact ID in the field we just created. Thanks for the headsup. If I have any issues sending back the data with the contact ID's, I will let you know but I think I might be good to go with this. You have been a great help here. Thank you
Sweet! I appreciate it Janine! I'll close this ticket out and if you run into any more blockers feel free to message us here at Clay! Always happy to help :)
Thank you Owen!
Hey, thanks for reaching out! 😊 For next time, here’s a helpful video showing how to resolve this: Loom Video. In this case, the issue is with the quotation marks (")—they need to be removed because our token contains quotations as well. If you still need help, feel free to send us the table, and we’ll be happy to take a look! 😊 https://downloads.intercomcdn.com/i/o/w28k1kwz/1203453502/146388b6cc3d5b753a93ca15b19b/CleanShot+2024-10-03+at+_45FRcZm8R2%402x.png?expires=1727999100&signature=82661e1a4f7b80547ed3a7bb943b1af248623f3c25471d2114496c0ed0ac8713&req=dSInFc17noRfW%2FMW1HO4zdh%2BR5CZnwcmr683BwZ21Di34%2Bl71kNmNPdMY6Vj%0AXdRz%0A
Owen C. we are on the last stretch here but I am having trouble trying to update custom fields inside of Apollo. I have been able to pull the custom field ID's from Apollo but when I try and update them, I keep getting errors. Can you take a look if my codes are correct and my setup in the screenshot is correct?
Sorry, wrong screenshot, here is the correct one:
This code gives the 200 but it does not change anything inside of Apollo.
Unsure if that’s the exact solve, however there are a few other thing I’d try:
Switch the column type of ‘Merged Apollo Contact ID’ to a number column
Add the two boxed key value pairs in the image to HTTP API menu in Clay
Include "contact" : { "custom_fields" : { ..... } } inside your body text
Hi Owen C., none of these options helped and I am unable to change the llr field to a number field in Apollo. I already have thousands of contacts using that field which also uses automation to many other software programs so creating a new one would not be an option. This is a string field so I think that anything should be able to to written to that field.
Hi Janine! Appreciate your patience on this, looking into this.
Thank you
I'll try using a workaround within Apollo but I probably need to find a way to find these leads within Apollo
Hey Janine! At least we've identified the culprit here. One suggestion is to use some of the unused built-in contact fields for LLR, Campaign Name, and Pain Point values. I really appreciate your patience—these issues can definitely be tricky to solve. Let me know how it goes! I'd love to help make this work, so don't hesitate to reach out if you have any other questions! :)
Super glad to hear that Janine! Good catch on your end and best of luck with the automation moving forward!! 😊
