Get GitHub Contributor Info via Slack Slash Command

Trigger a Slack slash command to fetch detailed GitHub user info like name, email, location, and commit emails from pull requests. Ideal for dev teams to quickly gather contributor details.

n8n
Get GitHub Contributor Info via Slack Slash Command

This n8n workflow enables seamless integration between Slack and GitHub, allowing users to invoke a slash command in Slack (e.g., /githubuser username) to retrieve comprehensive contributor information. It uses a webhook to capture the command, queries the GitHub GraphQL API for user details including name, company, location, avatar, public email, and recent pull request commits to extract associated emails. A custom function processes the data, matching commit author names to compile a list of unique emails.

Benefits include rapid access to contributor contact info without leaving Slack, saving time on manual GitHub searches. It's particularly useful for open-source maintainers, HR in tech teams, or project leads verifying contributor identities. The workflow handles nested GraphQL responses efficiently, providing formatted output ready for Slack posting (assumed final node).

Use cases: Onboarding new contributors by auto-fetching emails; auditing pull request authors; team notifications with profiles. Requires a GitHub personal access token. Scalable for workspaces with high GitHub activity, enhancing productivity in development workflows.

$9.99
Last updated October 17, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Productivity workflows

More from Fred Garcia

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.