Slack app templates

This app allows users to interact with a Slack bot, ask a question about the data in a table or request the table schema, and then uses the latest ChatGPT to generate a query that is executed on BigQuery to return the results. The app includes a retry mechanism for query generation in case of an error (up to two retries) and provides the LLM with the table info to generate more accurate queries. The table schema is only printed if it is successfully retrieved. All errors from retries are now passed to the LLM. The generated query is printed before the results, and the results are displayed in a pretty table format. The bot uses the Slack API to send and receive messages and parses the user's message to determine the action to take. The bot always responds in a thread to the original message.

This is a simple starting point for a Slack bot it just responds hi to a mention.

An app for Slack integration allowing the creation of public channels using the Slack API. This webhook app requires 'SLACK_BOT_TOKEN' to authenticate with slack api. It also requires channels:manage scope enabled to create channels. Further enchancements to prompts may allow the app to add the user to the channel.

A Slack app with search functionality for messages based on query, username, and channel name. Requires SLACK_USER_TOKEN with search:read users scope enabled.

This app listens for mentions in a Slack thread, excluding messages sent by bots and messages where the bot is mentioned. It then summarizes the thread using an LLM, providing a concise summary of 3 to 5 sentences. The summary is sent back to the same thread where the bot was mentioned. The app also improves the prompt given to the LLM, ensuring that the response consists of key takeaways in bullet points, is concise, and avoids repetition. It also handles errors when the app is mentioned directly without any thread.

This app allows users to schedule a status change on Slack by sending a direct message to the bot with their desired status, an optional emoji, and the start/end times. The app handles scheduling conflicts by prioritizing the most recent request and notifies the user accordingly. It also changes the user's Slack status at the scheduled times. If the user enters scheduling information in an incorrect format, the app sends a message explaining the correct format. The app uses the user's timezone from Slack for scheduling. Ensure the system clock is synchronized with the actual time to avoid scheduling issues. The app requires a user token to change the user's status.

This Slack Send & Post Message app will respond to messages sent to a channel. It will include the original message as a quote and the channel name in the private responses it sends. It will use the `llm_prompt` ability to generate responses. The app will ensure secure handling of Slack API credentials and log errors for maintenance and review. Make sure Event Subscriptions and `message.channels`, `message.im` and `message.groups` bot events have been enabled for your Slack App.

This app allows users to create polls on Slack using the /poll command. It posts an interactive message with poll options in the channel where the command was invoked, captures users' responses, and updates the poll message to display the current anonymous results. Users can change their votes, and the app will update the poll results accordingly. The app requires SLACK_BOT_TOKEN and SLACK_APP_TOKEN for authentication and must be subscribed to interaction events to capture votes.

This app, named "Slack Mention Jira Query Generator", is designed to assist you in generating Jira Query Language (JQL) queries directly from Slack. When you mention the app in a Slack message, it will generate a JQL based on your message and ask if you want to run the query. If you agree, it will execute the query on Jira and return the results in the same Slack thread. The app is designed to handle multiple users at the same time and ensures that the correct JQL is associated with the user who requested it. It also formats the JQL results to share the links of the issues instead of the actual issue object, making it easier for you to navigate to the issues directly from Slack. To use this app, you will need to provide the following environment variables: - SLACK_BOT_TOKEN: You can get this by creating a new app in your Slack workspace, adding the bot scope, and installing the app in the workspace. - SLACK_APP_TOKEN: This can be generated by enabling Socket Mode for the app in the Slack API settings and generating an App-Level token. - JIRA_API_TOKEN and JIRA_EMAIL: These can be generated from your Jira account settings. - JIRA_SERVER_URL: This is the URL of your Jira server.

This app listens to mentions of our app on Slack, sends a loading message, and then responds with a poem generated by an AI in the same thread as a reply to the original mention. The poem is based on the message sent by the user. The app requires two environment variables: SLACK_BOT_TOKEN and SLACK_APP_TOKEN. These tokens are used to authenticate the app with Slack. To generate these tokens, you need to create a new app in your Slack workspace, add the bot scope, install the app in the workspace, enable Socket Mode for the app in the Slack API settings, and generate an App-Level token.

This app fetches Jira issues that had status change in the last week, calculates the count of issues in different issue types, further breaks down each issue type by issue status, prepares a summary for it in form of a table using tabulate, posts the summary in a Slack channel, and schedules the app to run every time the server is started and then every week afterwards. The app requires the following environment variables to be set: - `JIRA_SERVER`: The URL of your Jira server. - `JIRA_USERNAME`: Your Jira username. - `JIRA_API_TOKEN`: Your Jira API token. - `JIRA_PROJECT_NAME`: The name of your Jira project. - `SLACK_TOKEN`: Your Slack token. - `CHANNEL_ID`: The ID of the Slack channel where the summary will be posted.

This app provides a summary of completed Jira tasks posted to a specific Slack thread every week. It uses the Jira API to download closed tickets from the current week. The query filters for tickets with the status 'Done' and last updated this week. The ticket details, including the ticket URL, are posted to Slack in a single thread. The required environment variables are JIRA_DOMAIN, JIRA_EMAIL, JIRA_API_TOKEN, SLACK_TOKEN, and SLACK_CHANNEL.

This bot will be designed to perform a variety of tasks on Discord, including counting metrics, tracking unique engaged members, tracking new members, and tracking members that have left. These metrics will also be sent as messages to a Slack channel every 7 days in the form of a data frame table converted to text. To make it work, it requires the following environment variables: DISCORD_TOKEN (your Discord bot token), SLACK_API_TOKEN (your Slack API token), and SLACK_CHANNEL (the ID of the Slack channel where the bot will send messages).

This app fetches data from BigQuery using a provided SQL query, formats the data into a table, and posts the table to a specified Slack channel. The data posting is scheduled to happen every day at 10 am UK time.

A Rest API that sends personal messages to Slack, supporting both direct private messages to user and posting messages in threads.