Back to Catalog

Provision new employee accounts to Google Workspace, Slack, Jira, and Salesforce

yuta tokumitsuyuta tokumitsu
122 views
2/3/2026
Official Page

Provision new employee accounts to Google Workspace, Slack, Jira, and Salesforce

This workflow streamlines the employee onboarding process by automatically provisioning user accounts across your organization's tech stack. By connecting HR input to IT operations, it eliminates manual data entry, reduces errors, and ensures new hires have access to the right tools from day one.

Depending on the employee's department, the workflow intelligently routes the provisioning process to create specific accounts (e.g., Jira for Engineering, Salesforce for Sales) alongside standard company-wide access.

Who is it for

  • IT Administrators looking to automate identity management and access provisioning.
  • HR Operations Managers who want to speed up the onboarding handover process.
  • Startup Founders needing a scalable way to manage new hire accounts without expensive SaaS management tools.

How it works

  1. Data Intake: The workflow is triggered by a Webhook (connected to a form like Typeform, Google Forms, or BambooHR) containing the new hire's details.
  2. Configuration: A central "Set" node establishes global variables, such as the default temporary password, welcome email subject, and the main Slack channel ID.
  3. Core Provisioning: It simultaneously creates a Google Workspace account and invites the user to a general Slack channel.
  4. Department Routing: A generic logic switch checks the department field:
    • If Engineering: It creates a Jira user.
    • If Sales: It creates a Salesforce user.
  5. Notification: Once all accounts are successfully provisioned, the workflow uses a generic email service (Gmail node) to send a welcome email to the new employee with their login details.

How to set up

  1. Credentials: You will need to configure credentials for the following nodes: Google Workspace Admin, Slack API, Jira Software, Salesforce, and Gmail (or your preferred email provider).
  2. Configuration: Open the node named βš™οΈ CONFIGURATION. Update the Slack_Channel_ID (where new users are invited) and the Default_Password to match your company's security policy.
  3. Webhook: Copy the Webhook URL from the start node and add it to your HR form or applicant tracking system.

Requirements

  • n8n: Version 1.0 or later recommended.
  • Access: Admin privileges for Google Workspace, Slack, Jira, and Salesforce to generate the necessary API keys/tokens.

How to customize the workflow

  • Add Departments: Edit the "Check Department" Switch node to add routes for Marketing, Finance, etc., and connect them to relevant apps (e.g., HubSpot, Xero).
  • Change Notification: Swap the Gmail node for Microsoft Outlook or Slack DM depending on how you notify managers.
  • Enhance Security: Add a step to force a password reset on the first login if the identity provider supports it.

Provision New Employee Accounts to Google Workspace, Slack, Jira, and Salesforce

This n8n workflow automates the provisioning of new employee accounts across multiple services: Google Workspace, Slack, Jira Software, and Salesforce. It streamlines the onboarding process by creating accounts in these essential platforms based on a single trigger.

What it does

This workflow simplifies new employee onboarding by performing the following steps:

  1. Listens for a Webhook Trigger: The workflow starts when it receives an HTTP POST request to its webhook URL. This webhook is expected to contain the new employee's details.
  2. Edits Fields: It processes the incoming data, likely extracting and formatting the necessary employee information (e.g., name, email, department) for subsequent steps.
  3. Creates Google Workspace Account: It provisions a new user account in Google Workspace (formerly G Suite) using the provided employee details.
  4. Creates Slack Account: It creates a new user account in Slack, enabling the new employee to join team communications.
  5. Creates Jira Software Account: It creates a new user account in Jira Software, granting access to project management and issue tracking.
  6. Creates Salesforce Account (Conditional): It checks a condition (using a "Switch" node) to determine if a Salesforce account should be created for the new employee.
    • If the condition is met, it creates a new user account in Salesforce.
  7. Sends Gmail Notification: After provisioning the accounts, it sends a notification email via Gmail, likely to an HR or IT administrator, confirming the successful account creation.
  8. Merges Data: It merges the output from the various account creation steps, potentially for a consolidated log or further processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Webhook Source: An external system or application configured to send employee data to the n8n webhook URL.
  • Google Workspace Admin Account: An active Google Workspace account with administrative privileges and the necessary n8n credentials configured.
  • Slack Account: An active Slack workspace and the necessary n8n credentials configured.
  • Jira Software Account: An active Jira Software instance and the necessary n8n credentials configured.
  • Salesforce Account: An active Salesforce instance and the necessary n8n credentials configured.
  • Gmail Account: A Gmail account configured with n8n credentials to send notification emails.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:
    • Locate the "Google Workspace Admin", "Slack", "Jira Software", "Salesforce", and "Gmail" nodes.
    • For each of these nodes, click on the "Credential" field and either select an existing credential or create a new one, providing the necessary API keys, OAuth tokens, or login details for your respective accounts.
  3. Configure Webhook:
    • Open the "Webhook" node.
    • Note down the "Webhook URL". This is the endpoint where your external system will send new employee data.
    • Ensure the "HTTP Method" is set to POST.
  4. Configure "Edit Fields":
    • Adjust the "Edit Fields" (Set) node to correctly extract and map the incoming data from your webhook to the fields required by Google Workspace, Slack, Jira, and Salesforce (e.g., firstName, lastName, email, department).
  5. Configure "Switch" Node (Salesforce Conditional Logic):
    • Review the "Switch" node to understand the condition that determines if a Salesforce account is created. Modify this condition based on your organization's requirements (e.g., {{ $json.department === 'Sales' }}).
  6. Configure "Gmail" Notification:
    • Adjust the "Gmail" node to send notifications to the appropriate recipients with relevant details about the new employee and the accounts provisioned.
  7. Activate the Workflow:
    • Click the "Activate" toggle in the top right corner of the n8n editor to enable the workflow.

Now, whenever your external system sends a POST request with new employee data to the webhook URL, n8n will automatically provision accounts and send notifications as configured.

Related Templates

Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack

🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. πŸ‘₯ Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness β€” no custom code required. βš™οΈ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌀️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) πŸš€ Setup (quick) Open Set β†’ Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. πŸ›  Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.

nodaBy noda
52

Translate documents to multiple languages with Google Drive and DeepL

Who's it for This workflow is perfect for content creators, international teams, and businesses that need to translate documents into multiple languages automatically. Whether you're localizing documentation, translating marketing materials, or creating multilingual content, this workflow saves hours of manual work. What it does Automatically monitors a Google Drive folder for new documents (PDF, DOCX, TXT, or Markdown) and translates them into multiple languages using DeepL API. Each translated document is saved with a language-specific filename (e.g., documenten.pdf, documentzh.pdf) in a designated folder. You receive an email notification when all translations are complete. How it works Monitors a Google Drive folder for new files Detects file format (PDF/DOCX/TXT/Markdown) and extracts text Translates the content into your chosen languages (default: English, Chinese, Korean, Spanish, French, German) Saves translated files with language codes in the filename Sends an email notification with translation summary Optional: Records translation history in Notion database Set up instructions Requirements Google Drive account (for file storage) DeepL API key (free tier: 500,000 characters/month) Gmail account (for notifications) Notion account (optional, for tracking translation history) Setup steps Create Google Drive folders: Create a "Source" folder for original files Create a "Translated" folder for output Copy the folder IDs from the URLs Get DeepL API key: Sign up at DeepL API Copy your API key Configure the workflow: Open the "Configuration (Edit Here)" node (yellow node) Replace folder IDs with your own Set your notification email Choose target languages Set up credentials: Add Google Drive OAuth2 credentials Add DeepL API credentials Add Gmail OAuth2 credentials Activate the workflow and upload a test file! Customization options Change target languages: Edit the targetLanguages array in the Configuration node (supports 30+ languages) Adjust polling frequency: Change trigger from "every minute" to hourly or daily for batch processing Enable Notion tracking: Set enableNotion to true and provide your database ID Add more file formats: Extend the Switch node to handle additional file types Filter by file size: Add conditions to skip files larger than a certain size Supported languages EN (English), ZH (Chinese), KO (Korean), JA (Japanese), ES (Spanish), FR (French), DE (German), IT (Italian), PT (Portuguese), RU (Russian), and 20+ more. Performance Short files (1 page): ~30 seconds for 6 languages Medium files (10 pages): ~2 minutes for 6 languages Large files (100 pages): ~15 minutes for 6 languages Technical Details Trigger: Google Drive folder monitoring (1-minute polling) Translation: DeepL API with automatic source language detection Loop implementation: Split Out + Aggregate pattern for parallel translation Error handling: Catches API failures and sends email alerts Storage: Original file format preserved in translated outputs Notes DeepL free tier provides 500,000 characters/month (approximately 250 pages) For high-volume translation, consider upgrading to DeepL Pro The workflow creates new files instead of overwriting, preserving translation history Google Docs are automatically converted to the appropriate format before translation What You'll Learn This workflow demonstrates several n8n patterns: File format detection and routing (Switch node) Loop implementation with Split Out + Aggregate Binary data handling for file operations Conditional logic with IF nodes (optional features) Cross-node data references Error handling and user notifications Perfect for learning automation best practices while solving a real business problem!

Daiki TakayamaBy Daiki Takayama
341

Seo blog content automation with GPT-4o-mini and human approval in Google Docs

Overview This n8n workflow automates the entire content creation process for SEO blog posts, from topic submission and AI drafting to human approval, revision, and final storage in Google Docs. It ensures high-quality, SEO-optimized content is generated efficiently while keeping a human in the loop for quality control. Prerequisites To use this workflow, you need the following accounts and credentials: Google Sheets Account: To manage the content tracker. The sheet must contain columns for Topic, Reference URL, Title, Status, and Link to document. OpenAI API Key (for GPT-4o-mini): To power the initial content drafting and subsequent revisions. Gmail Account: To send the content for human approval and wait for feedback. Google Docs Account: To create and store the final approved blog posts. How It Works The workflow operates in four main stages: Topic Submission, AI Content Creation, Human Approval & Revision Loop, and Final Publishing. Stage 1: Topic Submission and Tracking This stage captures a new blog topic and adds it to the content tracker. On form submission (Form Trigger): The workflow is initiated when a user submits a Topic and an optional Reference link through the form. Append row in sheet (Google Sheets): The new topic and reference link are added as a new row in your content tracker sheet. Get Topic from Google Sheets: The workflow fetches the newly added row, including the system-generated row_number for tracking updates. Stage 2: AI Content Creation (Initial Draft) The workflow uses an expert AI agent to generate the first draft of the blog post. Copywriter AI Agent: Acting as an expert SEO content strategist, the agent receives the topic and reference URL. The agent improves the provided topic into an SEO-optimized title. It writes a complete, conversational, SEO-friendly blog post (800–1200 words) using proper Markdown headings and lists. OpenAI Chat Model (GPT-4o-mini): Powers the agent's generation. Structured Output Parser: Ensures the output is in a JSON format with separate title and content keys. Set Data: The AI-generated title and content are mapped to workflow variables (Topic Title, Content) for easy use in subsequent nodes. Stage 3: Human Approval and Revision Loop This is the critical quality control step where a human reviews the draft and decides on the next action. Send Content for Approval (Gmail): The generated title and content are sent via email to the approver (<your email>). This uses a custom form that allows the user to choose Yes (Approve), No (Request Revision), or Cancel. The form also includes a Content Feedback textarea. Approval Result (Switch): The workflow pauses until the approver submits the form, and then directs the flow based on their choice. If "Yes" (Approved): Proceeds to the final publishing stage. The Update Topic Status on Google Sheets node is executed, setting the Status to Approved and logging the new Title. If "No" (Revision Requested): Proceeds to the revision loop. Copywriter Revision Agent: This agent takes the original content, the topic title, and the user's Content Feedback. It is instructed to incorporate the feedback, preserving the existing structure and tone, and outputs a revised blog post. The flow loops back through the Set Data node and then returns to the Send Content for Approval node for a new review. If "Cancel": Stops the workflow, and the Update Topic Status on Google Sheets node is executed. Stage 4: Final Publishing Once approved, the content is stored in Google Docs and the tracker is updated. Create Blog file (Google Docs): A new Google Doc is created using the approved Topic Title. Add blog content in file (Google Docs): The final Content (in Markdown format) is inserted into the newly created document. Update sheet with blog post link (Google Sheets): The final tracker update logs the Link to document and the Published date. Customization Tip Recommend using AI humanazier and AI detector tools before approval to make the SEO score better.

Priyanka RanaBy Priyanka Rana
528