Tally to Notion, client intake done and handed off
Client intake sounds simple. Then the form comes in, you copy details into Notion, create a Drive folder, message the team, and somehow the budget field still ends up wrong.
Marketing leads feel it when new inquiries pile up. Agency owners lose time on admin instead of delivery. And ops folks get stuck cleaning up the mess. This Tally Notion automation turns every submission into a clean handoff your team can trust.
You’ll see how the workflow captures the submission, creates the right records and folders, then posts the details to Slack so nothing sits unnoticed.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Tally to Notion, client intake done and handed off
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Create folder", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Create a database page"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields1", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send a message"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge"]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract Client Fields"]
n5 --> n1
n4 --> n6
n2 --> n5
n0 --> n2
n6 --> n0
n6 --> n5
n1 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n1 database
class n4 api
class n6 code
classDef customIcon fill:none,stroke:none
class n1,n3,n4,n5,n6 customIcon
The Problem: Client Intake Breaks During Handoff
A client submits your Tally form and, in theory, you’re “good.” In reality, the work just moved into three different tools and a handful of tiny decisions that never get documented. Someone copies the name into Notion. Someone else makes a Google Drive folder. Another person posts a Slack message, but forgets the budget or links the wrong folder. If you run multiple projects at once, those little slips turn into missed follow-ups, confused delivery teams, and a pipeline you can’t reliably forecast.
It adds up fast. Here’s where it breaks down.
- You end up doing the same copy-paste work for every single lead, even when the form already has the data.
- Google Drive folders get created inconsistently, so files land in random places and searching becomes a time sink.
- Notion records are missing fields or formatted differently, which makes sorting and filtering unreliable later.
- Slack notifications happen “when someone remembers,” and that’s how good leads sit untouched for a day.
The Solution: Tally → Notion + Drive + Slack Handoff
This workflow listens for a new Tally submission via a webhook, then immediately turns that submission into organized, usable onboarding assets. First, it parses the form fields (name, email, project type, budget) and cleans them up so they’re consistent. Next, it creates a dedicated Google Drive folder using the client’s name and project type, which keeps your team’s files structured from day one. Then it writes a new record into your Notion database with the client details plus the Drive folder link. Finally, it posts a Slack message to the right channel with all the key onboarding info so your team can act right away.
The workflow starts when someone hits “Submit” on your Tally form. From there, n8n prepares the client fields, creates the Drive directory, and merges everything into one clean payload. Notion gets the new client item, and Slack gets the handoff message a moment later.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you get 10 Tally submissions a week. Manually, you might spend about 10 minutes creating a Drive folder, 10 minutes building a clean Notion record, and 5 minutes writing a Slack handoff (plus the usual back-and-forth). That’s roughly 4 hours a week of repetitive setup. With this workflow, the trigger is instant and the processing runs in the background, so your “time spent” is basically zero unless you want to review the record.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Tally to collect new client intake data.
- Notion to store client records in a database.
- Google Drive for automatic onboarding folder creation.
- Slack to notify the team and kick off onboarding.
Skill level: Beginner. You’ll connect accounts, pick your Notion database, and choose the Slack channel.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Tally submission triggers the workflow. n8n receives the form payload through an incoming webhook, so you don’t need anyone checking inboxes or spreadsheets.
The client fields get cleaned up and prepared. The workflow parses the submission, pulls out the important answers (like name, email, project type, and budget), and maps them into reliable fields you can reuse.
Google Drive and Notion get updated automatically. A new Drive folder is created for that client, then a Notion database item is added that includes the client info and the folder URL.
Slack gets the handoff message. Your channel receives a clear summary with the details your team needs to start onboarding, without chasing context.
You can easily modify the folder naming convention to include a timestamp or internal ID based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the entry point that receives client submissions and initiates the workflow.
- Add and open Incoming Webhook Trigger.
- Set HTTP Method to
POST. - Set Path to
/tally-submission. - Copy the test webhook URL for use when validating the flow.
Step 2: Connect Google Drive and Create the Client Folder
Create an onboarding folder in Drive based on the submitted client name.
- Open Generate Drive Directory.
- Credential Required: Connect your googleDriveOAuth2Api credentials.
- Set Resource to
folder. - Set Name to
={{ $json.name + " - Onboarding" }}. - Set Drive to
My Drive. - Set Folder (parent folder) to
[YOUR_ID].
⚠️ Common Pitfall: Replace [YOUR_ID] with your actual Drive parent folder ID, or the folder creation will fail.
Step 3: Parse and Map Client Inputs
Transform the webhook payload into clean fields, then map IDs used for downstream nodes.
- Open Parse Client Inputs and keep the JavaScript Code as provided to extract
name,email,projectType, andbudget. - Confirm that Parse Client Inputs outputs to both Generate Drive Directory and Combine Data Streams in parallel.
- Open Map Identifier Fields and set the first assignment to Name
uuidwith Value={{ $execution.id }}. - Add the second assignment with Name
idand Value={{ $json.id }}. - In Combine Data Streams, set Mode to
combineand Combine By tocombineByPosition.
Tip: The parallel paths ensure the Drive folder ID and parsed client data are combined correctly before creating the Notion record.
Step 4: Configure Notion and Slack Outputs
Create a Notion database entry and notify your team in Slack.
- Open Add Notion Record.
- Credential Required: Connect your notionApi credentials.
- Set Resource to
databasePageand Database to[YOUR_ID]. - Map properties using expressions: Name
={{ $json.name }}, Email={{ $json.email }}, Project Type={{ $json.projectType }}, Budget={{ $json.budget }}. - Set Onboarding Link to
=https://drive.google.com/drive/folders/{{$json["id"]}}. - Open Post Slack Alert.
- Credential Required: Connect your slackOAuth2Api credentials.
- Set Select to
channeland Channel to[YOUR_ID]. - Set Text to the provided message template with expressions such as
{{$json["property_name"]}}and{{$json["url"]}}.
⚠️ Common Pitfall: Ensure your Notion database property names match exactly (e.g., Name, Email, Project Type, Budget, Onboarding Link) or the fields will not populate.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow and then enable it for production use.
- Click Execute Workflow and send a sample POST payload to the Incoming Webhook Trigger test URL.
- Confirm that Generate Drive Directory creates a folder named like
Client Name - Onboarding. - Verify that Add Notion Record creates a new page in the
Clientsdatabase with all properties filled. - Check that Post Slack Alert posts the formatted message to your chosen channel.
- When the test succeeds, toggle the workflow to Active to start processing live submissions.
Common Gotchas
- Notion credentials can expire or need specific permissions. If things break, check your n8n Notion credential and the database share/access settings first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your accounts and Notion database are ready.
No. You’ll mostly connect accounts and match the form fields to your Notion properties.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in standard tool costs (like your Notion, Slack, and Google Workspace plans) if you’re not already using them.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you’ll probably want to. You can adjust the Google Drive folder naming inside the folder creation step (the Google Drive folder node) to include a date, a project code, or a unique client ID. In the “Map Identifier Fields” step, you can add more properties (like deadline, referral source, or notes) and pass them into the Notion record creation. Many teams also tweak the Slack message to mention an owner or add project tags.
Usually it’s permissions. Make sure the Notion integration is connected in n8n and that the specific database is shared with that integration. If you recently duplicated the database or changed properties, re-select the database in the Notion node so the field mapping refreshes. Also check that your required properties (like Name) still match what the workflow is trying to write.
A lot. On n8n Cloud Starter, you can run thousands of executions per month, and higher tiers handle more volume. If you self-host, there’s no platform execution limit (it depends on your server). Practically, most small teams can run this all day without noticing any slowdown unless Google or Notion starts rate limiting due to unusually high bursts.
Sometimes, yes. n8n is a better fit if you want more control over data cleanup, merging paths, and keeping the logic in one place without paying extra for every branch. It also gives you a self-hosting option, which is handy if you expect higher volume or want tighter control over data. Zapier or Make can be quicker for a very simple “form → Slack” scenario, frankly. If you’re torn, Talk to an automation expert and you can sanity-check the best approach in a few minutes.
Once this is live, every new client starts in the right place, with the right context, and the right people notified. Set it up once, then get back to work that actually needs you.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
