GitHub application for Slack

[stevenmartorella-source]

Introduce yourself

Hi everyone. My name is Steve Martorella. I'm interested in learning about GitHub's applications for developing a more automated system for teams to send inquiries through Slack and obtain responses from an organized and comprehensive database of data and information

Links (optional)

No response

Where are you in your GitHub journey?

Brand new to GitHub

And where are you going next on GitHub?

My next step is to explore and learn about GitHub products and support

What technical skills or projects are you working on?

I am exploring Girhin applications for use in Slack

Got a question for us? (optional)

No response

[maheerCodes]

hey @stevenmartorella-source 👋 welcome to github !
what youre describing sounds less like a github-specific feature and more like a slack bot /automation project ,,,github itself doesnt have a built-in "send inquiries through slack and pull from a database" product ,,,but its very doable by combining a few tools

the general shape of what youd build :

• slack app /bot ,,,create one at api.slack.com/apps ,,,this handles receiving messages / commands from your team in slack.
• automation layer,,,this is the part that connects slack to your data sourcee. tools like n8n (open source ,self-hostable)or zapier /make (no-code ,hosted) are great for this without needing to write a full backend from scratch.you set up a trigger(slack message / slash command) > query your database > format and send the response back
• database ,,,depends on what "organized and comprehensive database" means for you ,,,could be as simple as a notion /airtable base ,or a real database like postgres / mongodb if its more structured data

if you want a quick proof of concept without coding,,n8n has a slack trigger node + database query nodes built in,,,,you can wire up a basic version in an afternooon.

if youre more code-first,,,a simple node.js + express backend with the slack bolt sdk (@slack/bolt) gives you full control over the bot logic and you connect it to whatever db you choose .

happy to point you toward more specific resources once you know roughly which direction (no-code vs custom code) you want to go 💙💙.

[stevenmartorella-source]

Hi sheikh, Thank you for the great direction. My sense is to start more simply With a quick proof of concept without coding. I hope to introduce an idea for our sakes teams to send inquiries through a slack channel and receive instructions and maybe links to internal sites. I can take s look at slack app and explore n8n for the slack trigger node + database query nodes built in. Any other tips are appreciated Steve

…

On Fri, Jun 19, 2026 at 9:19 PM Sheikh Mohammad Ali Maheer < ***@***.***> wrote: hey @stevenmartorella-source <https://github.com/stevenmartorella-source> 👋 welcome to github ! what youre describing sounds less like a github-specific feature and more like a slack bot /automation project ,,,github itself doesnt have a built-in "send inquiries through slack and pull from a database" product ,,,but its very doable by combining a few tools the general shape of what youd build : - slack app /bot ,,,create one at api.slack.com/apps ,,,this handles receiving messages / commands from your team in slack. - automation layer,,,this is the part that connects slack to your data sourcee. tools like *n8n* (open source ,self-hostable)or *zapier /make* (no-code ,hosted) are great for this without needing to write a full backend from scratch.you set up a trigger(slack message / slash command) > query your database > format and send the response back - database ,,,depends on what "organized and comprehensive database" means for you ,,,could be as simple as a notion /airtable base ,or a real database like postgres / mongodb if its more structured data if you want a quick proof of concept without coding,,n8n has a slack trigger node + database query nodes built in,,,,you can wire up a basic version in an afternooon. if youre more code-first,,,a simple node.js + express backend with the slack bolt sdk ***@***.***/bolt) gives you full control over the bot logic and you connect it to whatever db you choose . happy to point you toward more specific resources once you know roughly which direction (no-code vs custom code) you want to go 💙💙. — Reply to this email directly, view it on GitHub <#199462?email_source=notifications&email_token=CGMUMVX2EAA2CJFSCPQNYZT5AXRB3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTG4YDOMBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17370708>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CGMUMVTK4TY6M4EMFVMLUCD5AXRB3AVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBSHA4TGMBVUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CGMUMVVP3ILWOTM374XXOFD5AXRB3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTG4YDOMBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CGMUMVSLKHHO3ORMNFLIIZT5AXRB3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTG4YDOMBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[maheerCodes]

hey Steve 👋.

sounds like a great use case for a poc ,,,heres a concrete starting structure for exactly what youre describing :

basic n8n workflow shape :

1. slack trigger node,,,set it to listen for messages in a specific channel(or a slash command like/askif you want it more structured than free text).
2. a simple keyword /intent matching step ,,, for a first poc you dont neeed full nlp ,,, a basic "if message contains X"(switch node in n8n)pointing to different responses works fine to start.you can upgrade to an llm node (openai api)later if you want smarter matching ,
3. lookup step ,,connect to wherever your internal links/ instructions live. if youre starting simple,,,,a google sheet or airtable base with columns like keyword | response | link is honestly the fastest poc,,,n8n has native nodes for both, no database setupp needed at all
4. respond in slack,,,n 8n sends the matched response back into the same channel /thread.

why this is a good poc starting point:

• you can build and test this in n8n in literallly an afternoon like i mentioned,,,,no code ,no hosting setup beyond n8n itself(they have a free cloud tier or you can self-host)
• a spreadsheet as your "database" means your sales team can update the answers themselves without touching the workflow at all ,,,good for early iteration before you commit to a real db.

one tip ,,,start with maybe 5-10 of your most common sales inquiries as your initial keyword / link mappings rather than trying to cover everything at once. get the pipeline working end to end first,,,,,,,,,,then expand coverage once the core flow is proven.

happy to help if you hit specific snags wiring up the n8n nodes💙💙💙💙 .