Get contributors information from GitHub in Slack

Needs changes

by Harshil Agrawal ✓ · 729 views · created 2020-07-28 · Engineering

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.

What this workflow does

This workflow has 4 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects GraphQL and Slack.

How it runs

Trigger: When an HTTP POST request hits its webhook URL.

GraphQL: uses GraphQL
Function: runs custom JavaScript (legacy Function node)
Slack: uses Slack

Services it uses

GraphQL Slack

Before you upgrade to n8n 3.0

1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:

Function (legacy) in Function: replace with Code node, mode 'Run Once for All Items'.

Removed in 3.0	Replace with
Function (legacy) Function	Code node, mode 'Run Once for All Items'

Nodes used (4)

Webhookn8n-nodes-base.webhook
GraphQLn8n-nodes-base.graphql
Functionn8n-nodes-base.function
Slackn8n-nodes-base.slack

From the author

Get your contributors GitHub information with a slash command in your Slack Workspace.
Excerpt from Harshil Agrawal's description on n8n.io.

View the original on n8n.io → Check your own copy

Get contributors information from GitHub in Slack

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (4)

From the author

Get the weekly “what broke” email