Feedposter

An Automation Engine to watch RSS Feeds and post them to Twitter! Runs on GitHub Actions without any database 🎯

Configuration

1. Clone the Repository

2. Edit feed.yaml to include RSS Feeds you want to watch. feed_url consists of the URI of your RSS Feed

   monitor:
  - feed:
    - item:
      name: KCD Chennai
      feed_url: https://dev.to/feed/kcdchennai

3. Get Tokens from Twitter with Elevated Access and it to Secrets on Repository Settings. The required tokens are:

   1. ACCESS_TOKEN_SECRET
   2. ACCESS_TOKEN
   3. CONSUMER_SECRET
   4. CONSUMER_KEY

4. The workflow will be running every 6 hours without any configuration update

Twitter API Keys

To get Twitter API keys with full functionalities, you will need to follow the steps below:

1. Go to https://developer.twitter.com/en/docs and create a developer account.
2. After creating the developer account, you will need to create a new project. Click on the "Create Project" button and give your project a name.
3. After creating the project, you will need to create a developer application. Click on the "Create App" button and give your application a name.
4. Fill out the required information for your application, including a detailed description of what you plan to use the API for.
5. Once you have completed the application form, click on the "Create" button to submit your application.
6. Your application will be reviewed by Twitter's team, and you will receive an email when it has been approved. Once your application has been approved, you will be able to access your API keys in the "Keys and Tokens" tab of your developer dashboard.
7. Click on the "Generate" button next to the "Consumer Keys" section to generate your API key and API secret.
8. Click on the "Generate" button next to the "Access Tokens" section to generate your access token and access token secret.
9. With these keys, you will be able to use the Twitter API to access various Twitter data, such as tweets, users, and trends. Keep in mind that the Twitter API has rate limits, so you will need to be mindful of how often you are making requests to the API. For Batch Tweets, like here it won't be an issue and you won't hit rate limits.