Practical overview
When it fits
Use it when you want a self-managed worker to turn sales from one OpenSea collection into posts on an authorized X account.
Who it is for
- OpenSea collection operators who want sale announcements posted to an X account
- Developers able to configure API credentials and deploy a JavaScript worker
Documented uses
- Choose an OpenSea collection to monitor by its collection slug.
- Publish sale posts containing the NFT name, ETH and USD prices, hashtags, and an OpenSea item link.
- Customize alerts with an ETH sale threshold or a full NFT image.
- Extend posts with seller or buyer addresses using OpenSea event data and code changes.
Requirements & limits
- The bot monitors OpenSea sales; the README points to a separate project for tracking multiple marketplaces.
- Default polling is every 60 seconds and can be changed in the project.
- The documented setup requires an X Developer app with read/write permissions and an OpenSea API key.
- Threshold filtering, seller or buyer details, and full-image posting involve code or configuration changes.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the bot as a Heroku worker
Configure the project to monitor an OpenSea collection and post sales from an authorized X account.
Before you start
- A copy of the project in a Git repository
- An X Developer account and app configured with read/write permissions
- An OpenSea API key
- A Heroku account and app
- Access to the X account that will publish posts
Steps
Create the X Developer app and use Twurl with its consumer key and secret to generate the access token and secret for the publishing account.
Create a Heroku app and connect it as a remote for the project repository.
Set the documented Heroku config variables: CONSUMER_KEY, CONSUMER_SECRET, ACCESS_TOKEN_KEY, ACCESS_TOKEN_SECRET, OPENSEA_COLLECTION_SLUG, and X_API_KEY.
Push the project to the Heroku remote and configure the app to use a worker dyno rather than a web dyno.
Expected outcome
A Heroku worker is configured to monitor the selected OpenSea collection and publish sale posts through the authorized X account.
Guide limitations
- The README says polling defaults to every 60 seconds; running less often requires changing the project.
- Posts are for OpenSea sales; the README points to a separate project for monitoring multiple marketplaces.
- The guide reflects the repository's documented setup and is not a human execution test.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- dsgriffin/opensea-sales-x-bot · Official homepage title · retained in its source language
Related options
NFT Sales X Bot — The README recommends this separate project for monitoring sales across multiple marketplaces, including X2Y2 and LooksRare.