See llms.txt for all machine-readable content.

GitHub and Team Up integration

Save yourself the work of writing custom integrations for GitHub and Team Up and use n8n instead. Build adaptable and scalable Development, workflows that work with your technology stack. All within a building experience you will love.

How to connect GitHub and Team Up

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

GitHub and Team Up integration: Create a new workflow and add the first step

Pyragogy AI-driven handbook generator with multi-agent orchestration

AI-Driven Handbook Generator with Multi-Agent Orchestration (Pyragogy AI Village) This n8n workflow is a modular, multi-agent AI orchestration system designed for the collaborative generation of Markdown-based handbooks. Inspired by peer learning and open publishing workflows, it simulates a content pipeline where specialized AI agents act in defined roles, enabling true AI–human co-creation and iterative refinement. This project is a core component of Pyragogy, an open framework dedicated to ethical cognitive co-creation, peer AI–human learning, and human-in-the-loop automation for open knowledge systems. It implements the master orchestration architecture for the Pyragogy AI Village, managing a complex sequence of AI agents to process input, perform review, synthesis, and archiving, with a crucial human oversight step for final approval. How It Works: A Deep Dive into the Workflow's Architecture The workflow orchestrates a sophisticated content generation and review process, ideal for creating AI-driven knowledge bases or handbooks with human oversight. Webhook Trigger & Input: The process begins when the workflow receives a JSON input via a Webhook (specifically at /webhook/pyragogy/process). This input typically includes details like the handbook's title, initial text, and relevant tags. Database Verification: It first verifies the connection to a PostgreSQL database to ensure data persistence. Meta-Orchestrator: A powerful Meta-Orchestrator (powered by gpt-4o from OpenAI) analyzes the initial request. Its role is to dynamically determine and activate the optimal sequence of specialized AI agents required to fulfill the input, ensuring tasks are dynamically routed and assigned based on each agent’s responsibility. Agent Execution & Iteration: Each activated agent executes its step using OpenAI or custom endpoints. This involves: Content Generation: Agents like the Summarizer and the Synthesizer generate new content or refine existing text. Peer Review Board: A crucial aspect is the Peer Review Board, comprised of AI agents like the Peer Reviewer, the Sensemaking Agent, and the Prompt Engineer. This board evaluates the output for quality, coherence, and accuracy. Reprocessing & Redrafting: If the review agents flag a major_issue, they trigger redrafting loops by generating specific feedback for the Synthesizer. This mechanism ensures iterative refinement until the content meets the required standards. Human-in-the-Loop (HITL) Review: For final approval, particularly for the Archivist agent's output, a human review process is initiated. An email is sent to a human reviewer, prompting them to approve, reject, or comment via a "Wait for Webhook" node. This ensures human oversight and quality control. Content Persistence & Versioning: If the content is approved by the human reviewer: It's saved to a PostgreSQL database (specifically to the handbook_entries and agent_contributions tables). Optionally, the content can be committed to a GitHub repository for version control, provided the necessary environment variables are configured. Notifications: The final output and the sequence of executed agents can be sent as a notification to Slack, if configured. Observe the dynamic loop: orchestrate → assign → generate → review (AI/human) → store Included AI Agents This workflow leverages a suite of specialized AI agents, each with a distinct role in the content pipeline: Meta-Orchestrator: Determines the optimal sequence of agents to execute based on the input. Summarizer Agent: Summarizes text into key points (e.g., 3 key points). Synthesizer Agent: Synthesizes new text and effectively incorporates reprocessing feedback from review agents. Peer Reviewer Agent: Reviews generated text, highlighting strengths, weaknesses, and suggestions, and indicates major_issue flags. Sensemaking Agent: Analyzes input within existing context, identifying patterns, gaps, and areas for improvement. Prompt Engineer Agent: Refines or generates prompts for subsequent agents, optimizing their output. Onboarding/Explainer Agent: Provides explanations of the process or offers guidance to users. Archivist Agent: Prepares content for the handbook, manages the human review process, and handles archiving to the database and GitHub. Setup Steps & Prerequisites To get this powerful workflow up and running, follow these steps: Import the Workflow: Import the pyragogy_master_workflow.json (or generate-collaborative-handbooks-with-gpt4o-multi-agent-orchestration-human-review.json) into your n8n instance. Connect Credentials: Postgres: Set up a Postgres Pyragogy DB credential (ID: pyragogy-postgres). OpenAI: Configure an OpenAI Pyragogy credential (ID: pyragogy-openai) for all OpenAI agents. GPT-4o is highly suggested for optimal performance. Email Send: Set up a configured email credential (e.g., for sending human review requests). Define Environment Variables: Define essential environment variables (an .env.template is included in the repository). These include: API base for OpenAI. Database connection details. (Optional) GitHub: For content persistence and versioning, configure GITHUB_ACCESS_TOKEN, GITHUB_REPOSITORY_OWNER, and GITHUB_REPOSITORY_NAME. (Optional) Slack: For notifications, configure SLACK_WEBHOOK_URL. Send a sample payload to your webhook URL (/webhook/pyragogy/process): { "title": "History of Peer Learning", "text": "Peer learning is an educational approach where students learn from and with each other...", "tags": "education", "pedagogy"], "requireHitl": true } Ideal For This workflow is perfectly suited for: Educators and researchers exploring AI-assisted publishing and co-authoring with AI. Knowledge teams looking to automate content pipelines for internal or external documentation. Anyone building collaborative Markdown-driven tools or AI-powered knowledge bases. Documentation & Contributions: An Open Source and Collaborative Project This workflow is an open-source project and community-driven. Its development is transparent and open to everyone. We warmly invite you to: Review it: Contribute your analysis, identify potential improvements, or report issues. Remix it: Adapt it to your specific needs, integrate new features, or modify it for a different use case. Improve it: Propose and implement changes that enhance its efficiency, robustness, or capabilities. Share it back: Return your contributions to the community, either through pull requests or by sharing your implementations. Every contribution is welcome and valued! All relevant information for verification, improvement, and collaboration can be found in the official repository: 🔗 [GitHub – pyragogy-handbook-n8n-workflow

Build your own GitHub and Team Up integration

Create custom GitHub and Team Up workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

GitHub supported actions

Supported API Endpoints for Team Up

To set up Team Up integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Team Up to query the data you need using the API endpoint URLs you provide.

See the example here

These API endpoints were generated using n8n

n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Team Up official documentation to get a full list of all API endpoints and verify the scraped ones!

GitHub and Team Up integration details

GitHub

GitHub

GitHub is the number one platform for developers. It boosts their software development and enhances their collaboration options. The tools offered by Github help you automate your tasks and facilitate your work, that is why it is preferred by millions of developers around the world.

Team Up

Team Up

TeamUp is a versatile scheduling platform that simplifies team coordination. This software offers intuitive calendar tools, easy event creation, and real-time collaboration features. With customizable views and seamless sharing options, TeamUp provides a comprehensive app for streamlined scheduling and team organization.

Other integrations with GitHub and Team Up

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQ about GitHub integrations

Need help setting up your GitHub and Team Up integration?

Discover our latest community's recommendations and join the discussions about GitHub and Team Up integration.

  • DupervalAI

    How do I download a binary file using the GitHub node?

    DupervalAI

    Hi, How am I supposed to download a binary file that I fetch with the “Get a file” feature of the GitHub node? I see the file in my execution but it has a downlad button in it that I need to click manually, it seems. I…

    Open topic
  • Семен Буров

    Github Node Error: Could not get the SHA of the file, when try edit file with # or Emoji in name

    Семен Буров

    Describe the problem/error/question I try to use many templates for N8N Backup to github. For example: Github N8N Backups: How to backup workflows with folder structure instead of tags? And in my case i have an error w…

    Open topic
  • Piotr Sikora

    Github List Files Node - How to change branch?

    Piotr Sikora

    Describe the problem/error/question I’m using Github List node. I want to list files and directories from specific branch. As you can see above - there is no option to change the branch. Do you have any option to do…

    Open topic
  • Ammar Aamir

    Environements Control

    Ammar Aamir

    Is environmental control only available for the Enterprise subscription? Is N8N planning to make it available for the community version? This is literally an essential feature.

    Open topic

Looking to integrate Slack and VirusTotal in your company?

Trusted by teams building smarter workflows.

Why

Why use n8n to integrate GitHub with Team Up

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship