Hacker News X Agent with Workflow

This is a simple agent that fetches the top stories from Hacker News and tweets a summary. Agent orchestration is done using @upstash/workflow agents.

To see the agent in action, follow @hackernewsagent on X.

To learn more about how the agent works, check out our blog post.

Setup Instructions

Fill Environment Variables

1. Clone this repository.

git clone https://github.com/upstash/hacker-news-x-agent.git

2. Install dependencies.

npm install

3. Create a .env.local file in the root directory and copy the contents from .env.local.example. Fill these environment variables following the instructions in the next steps.

4. Go to QStash tab on Upstash Console. Fill the following environment variables in .env.local with the values found in the Environment Keys section:

# To power the workflow
QSTASH_TOKEN=

# To make sure requests are coming from the right source
QSTASH_CURRENT_SIGNING_KEY=
QSTASH_NEXT_SIGNING_KEY=

5. Go to Redis tab on Upstash Console. Create a new Redis database and fill the following environment variables in .env.local with the values found in the REST API section .env tab:

# To keep track of the news articles visited
UPSTASH_REDIS_REST_URL=
UPSTASH_REDIS_REST_TOKEN=

6. Go to OpenAI Platform -> API Keys and create a new API key. Fill the following environment variables in .env.local:

# To power the agent
OPENAI_API_KEY=

7. Go to ideogram and create a new API key. Fill the following environment variables in .env.local:

# To generate images
IDEOGRAM_API_KEY=

# To be able to tweet
TWITTER_CONSUMER_KEY=
TWITTER_CONSUMER_SECRET=
TWITTER_ACCESS_TOKEN=
TWITTER_ACCESS_TOKEN_SECRET=

Deploy the Agent

1. Deploy the agent to Vercel.

vercel

2. Go to the Vercel Dashboard -> Your Project -> Environment Variables and paste the contents of .env.local there, you don't need to set them one by one.

3. Deploy the agent to production.

vercel --prod

Calling the Agent

1. To secure the calls to the agent, only requests signed by QStash are allowed. If you don't want this security layer, you can just leave the following environment variables empty. You can learn more about how to Secure an endpoint with our guide.

# To make sure requests are coming from the right source
QSTASH_CURRENT_SIGNING_KEY=
QSTASH_NEXT_SIGNING_KEY=

2. Go to QStash tab on Upstash Console and publish a message.

Schedule the Agent

1. Go to QStash tab on Upstash Console and create a new schedule with Request Builder. Keep the limits of X API and QStash in mind while setting the schedule frequency. Cron expression 0 */2 * * * will run the agent every 2 hours.

Local Development

1. Check out our Local Development Guide to learn how to work with @upstash/workflow agents locally.

2. You can run the agent locally with the following command:

npm run dev