Automated Employee Onboarding from Google Forms to Slack, Jira, and GitHub

Overview

This workflow automates the entire employee onboarding process triggered by a new Google Form submission. When a new hire's details are submitted (name, email, department, role, GitHub username), the workflow automatically provisions access across Slack, Jira, and GitHub based on the employee's department and team. It also tracks the onboarding status in Google Sheets, preventing duplicate processing and notifying an admin if the employee has already been onboarded.

This is particularly useful for HR teams, IT administrators, and growing companies that want to eliminate manual provisioning steps, reduce human error, and ensure every new hire gets consistent access from day one.

Step-by-Step Node Breakdown

1. New Google Form Response (Google Sheets Trigger — OAuth2) — Polls the specified Google Sheet every minute for new rows added via Google Forms. Configured to watch "Form Responses 1" sheet. Requires the Google Sheet ID to be set in the documentId field.

2. Map department and team configuration (Code Node — No auth) — A JavaScript code node that contains a configuration object mapping departments (Software, Marketing, Finance, Project) to Slack channel IDs and Jira project keys. It also maps team roles (FrontEnd, BackEnd, Mobile, etc.) to GitHub repository names and Jira component IDs. The code extracts the incoming form data, looks up the correct Slack channel, Jira project, component IDs, and GitHub repo for the employee, and outputs an enriched object with these mappings plus a boolean isSoftware flag.

3. Check if onboarding already completed (IF Node — No auth) — Checks the Status field from the incoming data. If the status equals "Completed", the workflow branches to notify the admin; otherwise, it proceeds with provisioning.

4. Notify admin if already processed (Slack Node — OAuth2) — Sends a direct Slack message to a specified admin user ID, informing them that the employee (name and email) was already processed with status "Completed". Requires a Slack connection and the admin's Slack user ID.

5. Add user to department Slack channel (Slack Node — OAuth2) — Uses the targetSlack value from the mapping node to invite the new employee to the appropriate department Slack channel. The node is configured to "join" the channel. If this fails (e.g., user already in channel), it continues without error.

6. Check if department is software (IF Node — No auth) — Evaluates the isSoftware boolean from the mapping node. If true, the workflow proceeds to add the user to GitHub; if false, it skips GitHub and goes directly to Jira invitation.

7. Add user to GitHub repository (HTTP Request Node — API Key auth via GitHub API credential) — Sends a PUT request to the GitHub API to add the employee as a collaborator to their team's repository with "push" permission. The URL dynamically constructs using the organization name (placeholder YOUR_ORG_NAME), the target repo from the mapping node, and the employee's GitHub username. Requires a GitHub API credential.

8. Invite user to Jira (HTTP Request Node — API Key auth via Jira Software Cloud API credential) — Sends a POST request to the Jira API to invite the employee by email address and assign them the Jira Software product. The URL uses a placeholder YOUR_SITE.atlassian.net. Requires a Jira Software Cloud API credential.

9. Create onboarding task in Jira (Jira Node — OAuth2) — Creates a new Jira issue (type "Task") in the project mapped to the employee's department. The summary includes the employee's email, and the description includes their department. The issue is assigned the appropriate component ID based on the employee's team role.

10. Update Google Sheet status to completed (Google Sheets Node — OAuth2) — Updates the Google Sheet row matching the employee's email address, setting the "Status" column to "Completed". This prevents the workflow from reprocessing the same employee in future runs.

Setup Instructions

Required Accounts & Services

• Google Account — For Google Sheets and Google Forms. You'll need a Google Sheet connected to a Google Form that captures new hire data.
• Slack Workspace — With appropriate department channels already created. You'll need Slack admin permissions to invite users.
• Jira Software Cloud — With projects and components set up for each department/team. You'll need admin permissions to invite users and create issues.
• GitHub Organization — With repositories for each team. You'll need admin permissions to add collaborators.

Credentials to Configure in n8n

1. Google Sheets OAuth2 — For both the trigger and update nodes. Connect your Google account.
2. Slack OAuth2 — For sending messages and inviting users to channels. Connect your Slack workspace.
3. Jira Software Cloud API — For inviting users and creating issues. Create an API token from your Atlassian account.
4. GitHub API — For adding collaborators. Create a personal access token with repo scope.

Placeholder Values to Replace

• YOUR_GOOGLE_SHEET_ID_HERE — Found in the Google Sheet URL between /d/ and /edit.
• YOUR_SLACK_ADMIN_USER_ID_HERE — Your Slack member ID (right-click profile → Copy member ID).
• YOUR_SOFTWARE_SLACK_CHANNEL_ID etc. — Slack channel IDs (right-click channel → Copy link → extract ID).
• YOUR_SOFTWARE_JIRA_PROJECT_KEY etc. — Jira project keys (e.g., "DEV", "MKT").
• YOUR_FRONTEND_COMPONENT_ID etc. — Jira component IDs (from Jira project settings → Components).
• YOUR_ORG_NAME — Your GitHub organization name.
• YOUR_SITE — Your Atlassian site name (e.g., "mycompany" from mycompany.atlassian.net).
• Repository names in the Code node's teams object — Must match actual GitHub repo names.

Use Cases & Variations

Primary Use Case

Automated employee onboarding for companies using Google Forms for HR intake, with Slack for communication, Jira for task management, and GitHub for development.

Variations & Adaptations

• Different HR Systems — Replace the Google Sheets trigger with a webhook from BambooHR, Workday, or any HRIS system.
• Additional Tools — Add nodes to provision accounts in other services like AWS IAM, Okta, or 1Password.
• Department-Specific Logic — Modify the Code node to handle more departments, different permission levels, or conditional access to multiple repositories.
• Notification Enhancements — Add email notifications via Gmail or SendGrid, or send a welcome message to the new hire in Slack.
• Approval Workflow — Insert a manual approval node (e.g., Slack message with buttons) before provisioning access.
• Offboarding — Reverse the logic to deprovision access when an employee leaves (triggered by a status change in the sheet).
• Multi-Cloud — Extend to add users to cloud providers like AWS IAM groups or Azure AD groups based on department.

{
  "meta": {
    "instanceId": "984de408a5cad88d157768c66d3889d41083cb00b76637dbc690936e2e4bdbf0",
    "templateCredsSetupCompleted": true
  },
  "nodes": [
    {
      "id": "297e6687-be2f-41b2-9829-f3c82da3369f",
      "name": "Workflow Explanation",
      "type": "n8n-nodes-base.stickyNote",
      "position": [
        -2656,
        -256
      ],
      "parameters": {
        "width": 723,
        "height": 1214,
        "content": "## Overview\nThis workflow automates employee onboarding using data submitted through a Google Form. Based on the employee's department and role, it provisions access to Slack, Jira, and GitHub, and tracks onboarding status.\n\n## Who's it for\n- HR teams managing employee onboarding\n- IT administrators handling access provisioning\n- Companies using Google Forms for new hire intake\n- Teams using Slack, Jira, and GitHub for collaboration\n\n## How it works\n1. A new response is submitted via Google Forms\n2. The workflow checks if the employee has already been processed\n3. If already completed, the admin is notified\n4. If not:\n   - User is added to the appropriate Slack channel\n   - If in the Software department, GitHub access is granted\n   - User is invited to Jira\n   - A Jira onboarding task is created\n5. The Google Sheet is updated to mark onboarding as completed\n\n## Setup Steps\n1. **Google Sheets**: Connect your account and update `YOUR_GOOGLE_SHEET_ID_HERE` in both the trigger and update nodes\n2. **Slack**: Connect your account and update:\n   - Department channel IDs in the Code node config\n   - Admin user ID in \"Notify admin\" node\n3. **Jira**: Connect your account and update:\n   - Project keys in the Code node config\n   - Component IDs in the Code node config\n   - Your site URL in the \"Invite user to Jira\" node\n4. **GitHub**: Connect your account and update:\n   - Organization name in the HTTP node URL\n   - Repository names in the Code node config\n\n## Requirements\n- Google Sheets with form responses\n- Slack workspace with appropriate channels\n- Jira Software Cloud instance\n- GitHub organization with repositories\n\n## Customization\n- Modify department mappings in the Code node to match your org structure\n- Update Slack channel IDs for each department\n- Adjust GitHub repository names for each team\n- Configure Jira component IDs for different roles"
      },
      "typeVersion": 1
    },
    {
      "id": "117f0260-e835-4f4e-be3a-d36a995e22d1",
      "name": "Group: Sorting Office",
      "type": "n8n-nodes-base.stickyNote",
      "position": [
        -1840,
        -80
      ],
      "parameters": {
        "color": 4,
        "width": 992,
        "height": 544,
        "content": "### Data processing and validation\nProcesses form input and checks if onboarding was already completed."
      },
      "typeVersion": 1
    },
    {
      "id": "177cf43c-e5fa-4ae3-8c6b-67ed68fd1dd7",
      "name": "Group: Digital Onboarding",
      "type": "n8n-nodes-base.stickyNote",
      "position": [
        -800,
        -80
      ],
      "parameters": {
        "color": 5,
        "width": 1312,
        "height": 544,
        "content": "### User provisioning and onboarding\nCreates accounts, assigns access, and sets up onboarding tasks."
// ... truncated (copy to see full JSON)