How to Fix Missing Cookie Issue in Phantombuster

Gabriel A. · 2025-05-15T18:35:35.065Z

When I "push data" in Phantombuster, I always get the message that there is no cookie. Before the Phantombuster update, I always copied the cookie from the Phantombuster backend. Now, however, it is no longer there. How can I do this as easily as possible?

How to Fix Missing Cookie Issue in Phantombuster | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
To easily obtain the required cookie for "push data" in Phantombuster after the update, you can use the PhantomBuster browser extension. Here's how: 1. Install the PhantomBuster browser extension if you haven't already. 2. For Slack: Click the "Connect to Slack" button to automatically retrieve your cookie. The Slack cookie's name is "d". 3. For LinkedIn: Click the "Connect to LinkedIn" button. Alternatively, you can manually find your LinkedIn cookie, named "li_at". This method simplifies the process of obtaining the necessary cookies for pushing data in Phantombuster.
Source: Phantombuster integration | Documentation | Clay University
Gabriel A.
·
·
I did all of this (install the Phantombuster Extension, etc) and it works in Phantombuster but in clay I always get the cookie error.
Loading attachments
LuisArturo
·
·
Hey there Gabriel, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Gabriel A.
·
·
https://app.clay.com/workspaces/155599/workbooks/wb_0swlxm6zKQWaR7ZamyC/tables/t_0swnvzbEdMYzYqsyR8d/views/gv_0swnvzbPJ65BmMMX8kB
Owen C.
·
·
Hey Gabriel, thanks for reaching out! You can add your LinkedIn session cookie within the PhantomBuster column as shown below. Let me know if this helps and how else I can assist here! :)
(532 kB)
Gabriel A.
·
·
My first question is: Why does it appear as “optional” when it is necessary? And my second question is: Previously, the cookie appeared in the Phantombuster backend, but after the update, this happens automatically. Do I really have to search for the cookie manually, and if so, where?
Owen C.
·
·
Hey Gabriel, this is setup so that on Clay's end it's technically optional so that if you've inputted the LinkedIn Session Cookie in your Phantom directly you can leave this blank and simply push data to a configured Phantom. Ah I haven't used PhantomBuster in a bit, however, yes usually being able to find the LinkedIn session cookie manually is required with scrapers like this. Quick video on how to do this here. Let me know if this helps!

Channeled
APP
·
·
To easily obtain the required cookie for "push data" in Phantombuster after the update, you can use the PhantomBuster browser extension. Here's how: 1. Install the PhantomBuster browser extension if you haven't already. 2. For Slack: Click the "Connect to Slack" button to automatically retrieve your cookie. The Slack cookie's name is "d". 3. For LinkedIn: Click the "Connect to LinkedIn" button. Alternatively, you can manually find your LinkedIn cookie, named "li_at". This method simplifies the process of obtaining the necessary cookies for pushing data in Phantombuster.
Source: Phantombuster integration | Documentation | Clay University
Gabriel A.
·
·
I did all of this (install the Phantombuster Extension, etc) and it works in Phantombuster but in clay I always get the cookie error.
Loading attachments
LuisArturo
·
·
Hey there Gabriel, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Gabriel A.
·
·
https://app.clay.com/workspaces/155599/workbooks/wb_0swlxm6zKQWaR7ZamyC/tables/t_0swnvzbEdMYzYqsyR8d/views/gv_0swnvzbPJ65BmMMX8kB
Owen C.
·
·
Hey Gabriel, thanks for reaching out! You can add your LinkedIn session cookie within the PhantomBuster column as shown below. Let me know if this helps and how else I can assist here! :)
(532 kB)
Gabriel A.
·
·
My first question is: Why does it appear as “optional” when it is necessary? And my second question is: Previously, the cookie appeared in the Phantombuster backend, but after the update, this happens automatically. Do I really have to search for the cookie manually, and if so, where?
Owen C.
·
·
Hey Gabriel, this is setup so that on Clay's end it's technically optional so that if you've inputted the LinkedIn Session Cookie in your Phantom directly you can leave this blank and simply push data to a configured Phantom. Ah I haven't used PhantomBuster in a bit, however, yes usually being able to find the LinkedIn session cookie manually is required with scrapers like this. Quick video on how to do this here. Let me know if this helps!