Recreate "Analyze GitHub PRs for vulnerabilities with AI" workflow from home page?

Questions
1

On the homepage at the moment there are a few example usages of n8n for some different roles (https://n8n.io/). The one under DevOps is interesting to me so I tried to recreate it but I can’t seem to find the right actions to do it. Is there a template for this somewhere that I can check out?

This is the workflow I am talking about:

image
image1016×512 38.3 KB

I can see the trigger For Github Pull Requests but the next node “Get git diff from github” doesn’t seem to exist. Then the Tool node in the AI Agent for “Understand GitHub PRs”, is this something that is built in or is it something custom?

  • n8n version: 1.36.4
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker (Azure App service)
  • Operating system: Linux
1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey @dkarzon Welcome to the n8n community! :tada:

The “Get git diff from GitHub” is also a GitHub node, and the “Understand GitHub PRs” is the Structured Output Parse node.

Let me tag someone from n8n team. They might help you.

@Jon @maxT

4

I’m also interested in the template for this workflow, “Analyze GitHub PRs for vulnerabilities with AI.” If someone could share it, that would be a great sample to follow!

5

Bumping this thread to see if anyone else can answer it.

6

bump

ps would be nice to have ‘git diff’ node

1 Like
7

Morning,

This is an interesting one, It looks like this workflow is just an idea of what you could create if you had some time so the “Get git diff from GitHub” node would need to be an HTTP request node to get the diff for the PR using /repos/{owner}/{repo}/pulls/{pull_number} and passing in an Accept header of application/vnd.github.diff

The tricky bit from there would be to create a tool or a prompt that knows what to do with this information.

1 Like
8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.