You are browsing as a guest. Sign up (or log in) to start making projects!

Sloogle Bot

  • 5 Devlogs
  • 10 Total hours

Publish Slack messages as searchable web pages to boost your community's visibility on Search Engines and AI web search tool calls.

Open comments for this post

3h 3m 24s logged

You can now publish message posts!


  • Publish messages as public search indexable posts using the /publish [message-url] slash command
  • View published posts from the web dashboard

In this update:

  • Add /publish [message-url/id] command to the slack bot
  • Add publish post API route
  • Add API helper and routes for fetching message, channel and workspace details

AI Usage Info

For adding debug logging into the codebase (helped me save a little time and headache so pls)


Next update

Manage posts (re-post, delete, etc.) feature, /my-posts command


GG

You can now publish message posts!


  • Publish messages as public search indexable posts using the /publish [message-url] slash command
  • View published posts from the web dashboard

In this update:

  • Add /publish [message-url/id] command to the slack bot
  • Add publish post API route
  • Add API helper and routes for fetching message, channel and workspace details

AI Usage Info

For adding debug logging into the codebase (helped me save a little time and headache so pls)


Next update

Manage posts (re-post, delete, etc.) feature, /my-posts command


GG

Replying to @snehasish

0
2
Open comments for this post

1h 44m 6s logged

Minor update

  • The /set-token [token] command now works.

You use /set-token [token]
|
POST /api/bot/set-token
|
Verify token and find the DB user bound with the token
|
Save token + workspace details (team ID, channel ID) in Database bound to user (so that we don’t need to filter through all API keys every request
|
You’re now ready to publish new posts using the /publish command!


Next update:

Improve the landing page, add a real login page and finally setup the /publish command

Minor update

  • The /set-token [token] command now works.

You use /set-token [token]
|
POST /api/bot/set-token
|
Verify token and find the DB user bound with the token
|
Save token + workspace details (team ID, channel ID) in Database bound to user (so that we don’t need to filter through all API keys every request
|
You’re now ready to publish new posts using the /publish command!


Next update:

Improve the landing page, add a real login page and finally setup the /publish command

Replying to @snehasish

0
2
Open comments for this post

1h 50m 19s logged

You can now create API keys to configure the Slack bot

How it will work:

  • Create an API key
  • Run the /set-token [token] command with the Sloogle bot
  • Done! You’re now authenticated to create and publish new message posts.

In this update:

  • Create backend endpoints for fetching and creating new API keys
  • Setup configure page with an API keys table and create API key modal
  • Add a How to configure the Slack bot section with steps to authenticate yourself with the Sloogle bot

Next: Work on the /set-token [token] command on the Slack bot

You can now create API keys to configure the Slack bot

How it will work:

  • Create an API key
  • Run the /set-token [token] command with the Sloogle bot
  • Done! You’re now authenticated to create and publish new message posts.

In this update:

  • Create backend endpoints for fetching and creating new API keys
  • Setup configure page with an API keys table and create API key modal
  • Add a How to configure the Slack bot section with steps to authenticate yourself with the Sloogle bot

Next: Work on the /set-token [token] command on the Slack bot

Replying to @snehasish

1
8
Open comments for this post

2h 44m 33s logged

Initialized Sloogle Web

  • Landing Page with integrated login (better-auth email OTP verification)
  • Configure supabase + drizzle ORM as Database and ORM
  • Configure Web Dashboard (shadcn/ui dashboard template)

Next up: configure backend route that will receive the slack message object and save it on DB (message content, id, timestamps, channel id, community id, etc.)

Initialized Sloogle Web

  • Landing Page with integrated login (better-auth email OTP verification)
  • Configure supabase + drizzle ORM as Database and ORM
  • Configure Web Dashboard (shadcn/ui dashboard template)

Next up: configure backend route that will receive the slack message object and save it on DB (message content, id, timestamps, channel id, community id, etc.)

Replying to @snehasish

0
1
Open comments for this post

51m 52s logged

First time making a Slack Bot (i was a pro discord bot dev back in 2020)

Initialized and setup the slack bot using Node.js and Slack Bolt

Added a Bot stats command that responds with the following:

First time making a Slack Bot (i was a pro discord bot dev back in 2020)

Initialized and setup the slack bot using Node.js and Slack Bolt

Added a Bot stats command that responds with the following:

Replying to @snehasish

0
1

Followers

Loading…