Identifying Source Repositories for Stargazers in Multi-Source Columns

Julien Nakache · 2024-12-01 01:27:28.578461+00

Hi, when adding items from a source column using more than 1 source, how can you know the source of the item? For example, I'm using the "Find Stargazers" source column with more than 1 source repo, and I'd like to know for each stargazers the source repo that they starred and made them show up in that list.

Identifying Source Repositories for Stargazers in Multi-Source Columns | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
When using the Find Stargazers action, you'll need to input a specific repository URL or name (e.g., https://github.com/clay-run/clay-base-sdk or clay-run/clay-base-sdk) for each search. The action will return an array of stargazers for that particular repository. If you want to track stargazers from multiple repositories, you'll need to run separate searches for each repository, and the results will be tied to their respective source repositories. Source: Find Stargazers with Github
Julien Nakache
·
·
What does that mean to run separate searches? Does that mean I have to create a table for each repo and then aggregate all of them into one main table?
Channeled
APP
·
·
You can use our Find Stargazers with Github action to retrieve stargazers from any repository. The action accepts either a repository URL (like https://github.com/clay-run/clay-base-sdk) or just the repository name (clay-run/clay-base-sdk) as input. You can add this action multiple times to a single table to collect stargazers from different repositories - there's no need to create separate tables and aggregate them. Source: Find Stargazers with Github
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bruno (Clay)
·
·
Hi Julien, thanks for reaching out! While it's not possible to retrieve the repository source at the individual record (row) level, you can inspect the repository source at the table level by reviewing the table sources. This approach will help you estimate which stargazers are associated with each repository: https://downloads.intercomcdn.com/i/o/w28k1kwz/1272320958/63eeb3170acf6f998877093fa5bd/CleanShot+2024-12-01+at+10_17_01.gif?expires=1733067900&signature=ce6df283c9ffde9d65c20448bc57801ac116b4d9956245c868ef3dc0ab8bba0d&req=dSIgFMp8nYhaUfMW1HO4zdINLnL1pDGdbSvTmMi8sWBW4Pqlax%2BcPdCIsDeo%0A1pov%0A If you're targeting precise categorization of your stargazers, using different tables for different repository sources may be the best approach here.
Julien Nakache
·
·
Thanks Bruno (Clay). Is there a way to query the stargazers URL? The startgazers endpoint requires pagination, but I could not find references on how to do that. Am I missing something?
Daniela Debebs (Clay)
·
·
Hey Julien! Thanks for the reply. Happy to help. Just to confirm, are you referring to how to import more records from the same stargazers URL? Are you experiencing any issues with all records not being imported?
Julien Nakache
·
·
Sorry I mispoke. I meant querying the starred URL, that is the list of repos a user has starred. I'd like to query it in order to get all the repos the user has starred (vs just knowing the user has starred one of the source repos).
Daniela Debebs (Clay)
·
·
Hey Julien! Thanks for the reply. The native integration is not able to do this (except return a count of Starred repositories). However, if there's an endpoint for this on Github, you could use the HTTP API feature to get that information. Here's a quick guide: - https://docs.clay.com/en/articles/9672489-http-api-with-clay - Additional video guide for configuring HTTP AP Also sharing a community resource I found on Github: https://stackoverflow.com/questions/24746041/github-show-users-starred-repos Let me know if this helps.
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

Channeled
APP
·
·
When using the Find Stargazers action, you'll need to input a specific repository URL or name (e.g., https://github.com/clay-run/clay-base-sdk or clay-run/clay-base-sdk) for each search. The action will return an array of stargazers for that particular repository. If you want to track stargazers from multiple repositories, you'll need to run separate searches for each repository, and the results will be tied to their respective source repositories. Source: Find Stargazers with Github
Julien Nakache
·
·
What does that mean to run separate searches? Does that mean I have to create a table for each repo and then aggregate all of them into one main table?
Channeled
APP
·
·
You can use our Find Stargazers with Github action to retrieve stargazers from any repository. The action accepts either a repository URL (like https://github.com/clay-run/clay-base-sdk) or just the repository name (clay-run/clay-base-sdk) as input. You can add this action multiple times to a single table to collect stargazers from different repositories - there's no need to create separate tables and aggregate them. Source: Find Stargazers with Github
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bruno (Clay)
·
·
Hi Julien, thanks for reaching out! While it's not possible to retrieve the repository source at the individual record (row) level, you can inspect the repository source at the table level by reviewing the table sources. This approach will help you estimate which stargazers are associated with each repository: https://downloads.intercomcdn.com/i/o/w28k1kwz/1272320958/63eeb3170acf6f998877093fa5bd/CleanShot+2024-12-01+at+10_17_01.gif?expires=1733067900&signature=ce6df283c9ffde9d65c20448bc57801ac116b4d9956245c868ef3dc0ab8bba0d&req=dSIgFMp8nYhaUfMW1HO4zdINLnL1pDGdbSvTmMi8sWBW4Pqlax%2BcPdCIsDeo%0A1pov%0A If you're targeting precise categorization of your stargazers, using different tables for different repository sources may be the best approach here.
Julien Nakache
·
·
Thanks Bruno (Clay). Is there a way to query the stargazers URL? The startgazers endpoint requires pagination, but I could not find references on how to do that. Am I missing something?
Daniela Debebs (Clay)
·
·
Hey Julien! Thanks for the reply. Happy to help. Just to confirm, are you referring to how to import more records from the same stargazers URL? Are you experiencing any issues with all records not being imported?
Julien Nakache
·
·
Sorry I mispoke. I meant querying the starred URL, that is the list of repos a user has starred. I'd like to query it in order to get all the repos the user has starred (vs just knowing the user has starred one of the source repos).
Daniela Debebs (Clay)
·
·
Hey Julien! Thanks for the reply. The native integration is not able to do this (except return a count of Starred repositories). However, if there's an endpoint for this on Github, you could use the HTTP API feature to get that information. Here's a quick guide: - https://docs.clay.com/en/articles/9672489-http-api-with-clay - Additional video guide for configuring HTTP AP Also sharing a community resource I found on Github: https://stackoverflow.com/questions/24746041/github-show-users-starred-repos Let me know if this helps.
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.