HumationHuman + Automation
Back to Catalog

Client onboarding automation: Tally Forms to Google Drive, Notion & Slack

Muhammad AhmadMuhammad Ahmad
549 views
2/3/2026
databasemysqlwordpresscsvexport
Official Page

📝 Automation: Instantly Onboard New Clients from Tally Form to Notion, Google Drive & Slack This automation streamlines the client onboarding process by integrating Tally, Notion, Google Drive, and Slack. When a potential client submits a Tally form, the automation is triggered via a webhook, automatically handling all onboarding steps without manual intervention.

⚙️ How It Works – Step-by-Step Form Submission Triggered A new Tally form submission is received via a webhook.

Client Data Extraction The automation extracts essential client details from the form, including:

-Name

-Email

-Project Type

-Budget

Google Drive Folder Creation A dedicated Google Drive folder is generated using the client’s name and project type for storing onboarding assets.

Notion Database Entry Creation A new item is added to a specified Notion database, storing:

Client information

Project scope

Folder link

Slack Team Notification A Slack message is sent to your designated team channel containing all onboarding details, ensuring the team is informed instantly.

✅ Pre-Conditions / Requirements A published Tally form collecting client data.

A connected Google Drive account with folder creation permissions.

An existing Notion database with columns for name, email, budget, etc.

A Slack workspace with an active bot/token integrated with the automation tool.

🛠️ Notion Database Structure Your Notion database should include at least the following fields:

-Name (Text)

-Email (Email)

-Project Type (Select)

-Budget (Select)

-Onboarding Folder Link (URL)

🧩 Customization Guidance You can modify the Google Drive folder naming convention to include a timestamp or custom ID.

Adjust Slack message formatting to include project-specific tags or mention specific team members.

Extend the Notion entry to include more fields like project deadline or contact notes.

Client Onboarding Automation: Tally Forms to Google Drive, Notion, & Slack

This n8n workflow automates the client onboarding process by integrating Tally Forms submissions with Google Drive, Notion, and Slack. It streamlines the creation of client folders, updates a client database, and notifies teams, ensuring a smooth and efficient onboarding experience.

What it does

  1. Triggers on Tally Form Submission: Listens for new submissions from a Tally Form.
  2. Processes Form Data: Extracts relevant client information from the Tally Form submission.
  3. Creates Client Folder in Google Drive: Generates a new folder in a specified Google Drive location for the new client.
  4. Updates Notion Database: Adds a new item to a Notion database, populating it with client details and a link to their Google Drive folder.
  5. Notifies Team via Slack: Posts a notification to a designated Slack channel, informing the team about the new client and providing quick access to their resources.
  6. Merges Data: Combines data from various steps to ensure all necessary information is available for subsequent actions.
  7. Edits Fields: Transforms and structures data as needed for compatibility with different services.
  8. Executes Custom Code: Utilizes a Code node for any specific data manipulation or logic required during the process.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Tally Forms Account: A Tally Form configured to collect client onboarding information.
  • Google Drive Account: A Google Drive account with a designated parent folder for new client folders.
  • Notion Account: A Notion database set up to store client information.
  • Slack Account: A Slack workspace with a channel for onboarding notifications.
  • n8n Credentials: Configured credentials for Google Drive, Notion, and Slack within your n8n instance.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Webhook:
    • Activate the "Webhook" trigger node.
    • Copy the webhook URL and configure your Tally Form to send submissions to this URL.
  3. Configure Credentials:
    • Update the "Google Drive" node with your Google Drive credentials and specify the parent folder ID for new client folders.
    • Update the "Notion" node with your Notion credentials and specify the database ID where client information should be added.
    • Update the "Slack" node with your Slack credentials and specify the channel ID for notifications.
  4. Customize Data Mapping:
    • Review the "Edit Fields" (Set) node and the "Code" node to ensure the data mapping from your Tally Form submission matches the expected fields in Google Drive, Notion, and Slack. Adjust as necessary.
  5. Activate the Workflow: Once all configurations are complete, activate the workflow.

Now, every time a new client submits your Tally Form, this workflow will automatically create their Google Drive folder, update your Notion client database, and notify your team on Slack.

Related Templates

Daily Magento 2 customer sync to Google Contacts & Sheets without duplicates

Automatically sync newly registered Magento 2 customers to Google Contacts and Google Sheets every 24 hours — with full duplication control and seamless automation. This workflow is a plug-and-play customer contact automation system designed for Magento 2 store owners, marketers, and CRM teams. It fetches customer records registered within the last 24 hours (from 00:00:00 to 23:59:59), checks against an existing Google Sheet to avoid reprocessing, and syncs only the new ones into Google Contacts. This ensures your contact list is always fresh and up to date — without clutter or duplicates. ✅ What This Workflow Does: Automates Customer Syncing Every day, it fetches newly registered Magento 2 customers via API based on the exact date range (midnight to midnight). Deduplicates Using Google Sheets A master Google Sheet tracks already-synced emails. Before adding a customer, the workflow checks this list and skips if already present. Creates Google Contacts Automatically For each unique customer, it creates a new contact in your Google Contacts, saving fields like first name, last name, and email. Logs New Entries to Google Sheets In Google Sheets, it even records magento 2 customer group, createdat, websiteid & store_id After syncing, it adds each new email to the tracking sheet, building a cumulative record of synced contacts. Fully Scheduled & Automated Can be scheduled with the Cron node to run daily (e.g., 12:05 AM) with no manual intervention required. 🔧 Modules Used: HTTP Request (Magento 2 API) Date & Time (for filtering registrations) Google Sheets (for reading/writing synced emails) Google Contacts (for contact creation) Set, IF, and Merge nodes (for control logic) Cron (for scheduling the automation) 💼 Use Cases: Keep your email marketing tools synced with Magento 2 customer data. Build a CRM-friendly contact base in Google Contacts without duplicates. Share customer data with sales or support teams through synced Google Sheets. Reduce manual work and human error in data transfer processes. 🔒 Credentials Required Magento 2 Bearer Auth: Set up as a credential in n8n using your Magento 2 API access token. Google API 📂 Category E-commerce → Magento 2 (Adobe Commerce) 💬 Need Help? 💡 Having trouble setting it up or want to customize this workflow further? Feel free to reach out — I’m happy to help with setup, customization, or Magento 2 API integration issues. Contact: Author 👤 Author Kanaka Kishore Kandregula Certified Magento 2 Developer https://gravatar.com/kmyprojects https://www.linkedin.com/in/kanakakishore

Kanaka Kishore KandregulaBy Kanaka Kishore Kandregula
163

Send RSS feed data to webhook

Filters articles based on keywords, checks against MongoDB for unique links, then sends results to different webhooks

daveBy dave
3968

Run bulk RAG queries from CSV with Lookio

This template processes a CSV of questions and returns an enriched CSV with RAG-based answers produced by your Lookio assistant. Upload a CSV that contains a column named Query, and the workflow will loop through every row, call the Lookio API, and append a Response column containing the assistant's answer. It's ideal for batch tasks like drafting RFP responses, pre-filling support replies, generating knowledge-checked summaries, or validating large lists of product/customer questions against your internal documentation. Who is this for? Knowledge managers & technical writers: Produce draft answers to large question sets using your company docs. Sales & proposal teams: Auto-generate RFP answer drafts informed by internal docs. Support & operations teams: Bulk-enrich FAQs or support ticket templates with authoritative responses. Automation builders: Integrate Lookio-powered retrieval into bulk data pipelines. What it does / What problem does this solve? Automates bulk queries: Eliminates the manual process of running many individual lookups. Ensures answers are grounded: Responses come from your uploaded documents via Lookio, reducing hallucinations. Produces ready-to-use output: Delivers an enriched CSV with a new Response column for downstream use. Simple UX: Users only need to upload a CSV with a Query column and download the resulting file. How it works Form submission: User uploads a CSV via the Form Trigger. Extract & validate: Extract all rows reads the CSV and Aggregate rows checks for a Query column. Per-row loop: Split Out and Loop Over Queries iterate rows; Isolate the Query column normalizes data. Call Lookio: Lookio API call posts each query to your assistant and returns the answer. Build output: Prepare output appends Response values and Generate enriched CSV creates the downloadable file delivered by Form ending and file download. Why use Lookio for high quality RAG? While building a native RAG pipeline in n8n offers granular control, achieving consistently high-quality and reliable results requires significant effort in data processing, chunking strategy, and retrieval logic optimization. Lookio is designed to address these challenges by providing a managed RAG service accessible via a simple API. It handles the entire backend pipeline—from processing various document formats to employing advanced retrieval techniques—allowing you to integrate a production-ready knowledge source into your workflows. This approach lets you focus on building your automation in n8n, rather than managing the complexities of a RAG infrastructure. How to set up Create a Lookio assistant: Sign up at https://www.lookio.app/, upload documents, and create an assistant. Get credentials: Copy your Lookio API Key and Assistant ID. Configure the workflow nodes: In the Lookio API call HTTP Request node, replace the apikey header value with your Lookio API Key and update assistantid with your Assistant ID (replace placeholders like <your-lookio-api-key> and <your-assistant-id>). Ensure the Form Trigger is enabled and accepts a .csv file. CSV format: Ensure the input CSV has a column named Query (case-sensitive as configured). Activate the workflow: Run a test upload and download the enriched CSV. Requirements An n8n instance with the ability to host Forms and run workflows A Lookio account (API Key) and an Assistant ID How to take it further Add rate limiting / retries: Insert error handling and delay nodes to respect API limits for large batches. Improve the speed: You could drastically reduce the processing time by parallelizing the queries instead of doing them one after the other in the loop. For that, you could use HTTP request nodes that would trigger your sort of sub-workflow. Store results: Add an Airtable or Google Sheets node to archive questions and responses for audit and reuse. Post-process answers: Add an LLM node to summarize or standardize responses, or to add confidence flags. Trigger variations: Replace the Form Trigger with a Google Drive or Airtable trigger to process CSVs automatically from a folder or table.

Guillaume DuvernayBy Guillaume Duvernay
293