OpenRuna
Sign in
← Workflows

Slack-GitHub User Info

4 nodes · webhook, graphql, slack

Engine
n8n
Nodes
4
Trigger
scheduled/triggered
Source file
1063_Slack_Graphql_Automation_Webhook.json

Workflow flow

IntegrationsWebhookGraphqlSlackFunction
100%
TRIGGER

Webhook

Webhook

GraphQL

Graphql

Function

Function

Slack

Slack

4 steps · flows top to bottom, branches left to right

Browse by integration

webhookgraphqlslack
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Slack-GitHub User Info. 4 nodes across webhook, graphql, slack, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"Slack-GitHub User Info" is an n8n automation built from 4 nodes spanning webhook, graphql, slack. 4 nodes · webhook, graphql, slack Execution begins at the scheduled/triggered trigger and flows through the 4 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Use it as a starting template when wiring webhook, graphql, slack — adjust node parameters to your accounts and record IDs.
  • Import "Slack-GitHub User Info" into n8n, reconnect credentials for webhook, graphql, slack, and run the same automation in your own workspace.
  • Share it with your team as a documented reference for scheduled/triggered automations in the webhook stack.
  • Study how data moves from webhook to graphql before building your own variant.

Example output

Imported into n8n, "Slack-GitHub User Info" exposes 4 configured nodes. Trigger type: scheduled/triggered. Integrations: webhook, graphql, slack. Open each node after import to map credentials to your own webhook and graphql accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Slack-GitHub User Info" into Claude and ask it to explain each of the 4 nodes. Claude is good at suggesting credential mappings for webhook, graphql, slack, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Slack-GitHub User Info" to your accounts — which webhook, graphql, slack credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 4 nodes.

Frequently asked questions

How do I import "Slack-GitHub User Info" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Slack-GitHub User Info" use?
It uses: webhook, graphql, slack. The flow diagram above shows how each service connects across the 4 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own webhook and graphql credentials in n8n after import.
What trigger type does "Slack-GitHub User Info" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Slack-GitHub User Info" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for webhook, graphql, slack.

Related resources