Idea: Xquik public X/Twitter data integration #21930
Replies: 3 comments
-
|
hi @kriptoburak generally we will promote well-adopted integrations to official, and otherwise encourage interested folks to make and use their own collection. we'd be happy to help with any questions you have if you choose to build it! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that guidance makes sense. I will treat this as an external collection or recipe path first, and not push for official integration placement unless there is adoption data or a maintainer asks for it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for the guidance. I built the external collection here: https://github.com/Xquik-dev/prefect-xquik PyPI package: Guide: Current shape:
I'm not asking for official promotion yet. This is the external collection path first; if there are conventions you want adjusted before adoption work, I can align it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Current behavior
Prefect has first-party and third-party integrations for workflow systems such as GitHub, Slack, AWS, and data platforms. I did not find an integration for read-only public X/Twitter data tasks.
Proposed behavior
Consider a Prefect integration or documented recipe for Xquik that exposes read-only tasks for public X/Twitter research workflows:
GET /x/tweets/searchGET /x/tweets/{id}GET /x/users/{id}andGET /x/users/searchGET /x/users/{id}/tweetsGET /x/trendsThis would let Prefect flows collect public social signals, persist results, and trigger downstream enrichment without maintaining scraper code inside each flow.
Example use
A flow could run on a schedule, call Xquik with a Prefect Secret or block-backed API key, normalize matching tweets, and pass the rows to a warehouse or notification task.
Additional context
Xquik Prefect guide: https://docs.xquik.com/guides/prefect
External collection: https://github.com/Xquik-dev/prefect-xquik
SDK and skill repo: https://github.com/Xquik-dev/x-twitter-scraper
I am opening this as an Ideas discussion because the integration contribution guide says new integration ideas should be discussed first. If maintainers prefer this as an external collection or recipe rather than a core integration, that works too.
Beta Was this translation helpful? Give feedback.
All reactions