Getting Started with Zapier: Build Your First Automated Connection, Step by Step
If you manage a team, you already know the feeling: three people on your team are copying data from one app into another, and none of them think that's part of their job. A sale…
If you manage a team, you already know the feeling: three people on your team are copying data from one app into another, and none of them think that's part of their job. A salesperson pasting form responses into a spreadsheet. A support lead retyping a ticket into a CRM. A project manager manually updating a status doc after every standup.
That drudgery isn't a people problem. It's a workflow problem — and it's the exact kind of problem Zapier was built to fix.
Zapier is the "glue" of the business software world. It lets you connect over 9,000 apps — from your email and CRM to your Slack, your PM tool, and your accounting software — and move data between them automatically, without writing a single line of code. For a manager, that means you can prototype an automation in an afternoon, prove it saves your team hours, and hand the working Zap to whoever should own it.
The Core Concept: Triggers and Actions
Every automation in Zapier follows a simple "If This, Then That" logic, which Zapier calls Triggers and Actions.
- Trigger: The event that starts the automation (e.g., "A new row lands in a Google Sheet" or "A deal moves to Won in the CRM").
- Action: The task the system performs automatically (e.g., "Post a Slack message to the team" or "Create a task in the PM tool").
In this guide, we'll build one concrete Zap together: every time someone fills out a form, an instant alert with their details lands in a Slack channel so the right person on the team sees it immediately. No code, about five minutes of your time. Follow along with Zapier open in your browser and you'll have a working automation by the end — and a pattern you can replicate for dozens of other team workflows.
Before You Start
- A Zapier account — create one at zapier.com if you don't have one. (The free plan includes one active "multi-step" Zap, which is all this guide needs. Teams typically put company automations on a paid seat.)
- A form your team uses — Google Forms, Typeform, HubSpot, or the contact form on your website. Google Forms is free and takes a minute to set up if you need one for the demo.
- Slack (or Teams) — a channel where the team wants alerts to land. A dedicated
#leadsor#new-requestschannel keeps alerts from drowning out everyday chatter.
Your Zap: "New Form Entry → Slack Alert"
Step 1: Create the Zap and pick your trigger app.
Log in to Zapier and click Create a Zap (the plus button at the top right). On the "What makes this Zap start?" screen, type google in the search box and select Google Forms. This is your trigger app — the thing that starts the workflow.
Step 2: Choose the trigger event. Zapier asks what event should start the Zap. Select New Form Response. This means: "Whenever a new response is submitted, run everything that follows."
Step 3: Connect your Google account. Click the button to connect your Google account. A browser window opens where Google asks you to Allow Zapier access to read your forms. Click Allow. Back in Zapier, you'll see your account confirmed with a green checkmark. (You only do this once — future Zaps will remember the connection. Note: if your company uses SSO or has admin policies for third-party apps, you may need to loop in IT before connecting.)
Step 4: Choose which form to watch. Zapier shows a dropdown of your Google Forms. Pick the form you want to monitor — for example, a "Contact Us" or "Request a Quote" form. If you don't have one yet, create it at forms.google.com with a few simple fields (Full Name, Email, Message).
Step 5: Test the trigger. Zapier offers to fetch a sample response so you can see the data it will receive. If your form already has at least one submission, Zapier pulls it in and shows you the fields — Name, Email, Message — exactly as they'll arrive. If your form is brand new and empty, fill it out once in the browser first, then click Continue. You need one real response for the test to show anything.
Step 6: Pick your action app.
Now choose what should happen. Type slack in the search box and select Slack. This is your action app — the thing that does something in response.
Step 7: Choose the action event. Select Send Channel Message. That's it — the whole job is: post a message to a channel.
Step 8: Connect your Slack workspace. Just like with Google, Zapier opens a Slack permission page. Click Allow to let Zapier post messages in your workspace, then pick the workspace to use.
Step 9: Choose the channel.
In the Channel field, select where the alert should land — for this example, #leads.
Step 10: Write the message — and map the data. This is the heart of the Zap. In the Message field, type your template, then use the field pickers to plug in the live data from the form. For example:
New lead just now! Name: {{Full Name}} Email: {{Email}} Message: {{Message}}
Here's how the mapping actually works: as you type, click the dropdown arrows that appear at the start of the line (the + / field picker) to open Zapier's field list. It shows every field from your Google Form response — Full Name, Email, Message. Click one and it inserts as a placeholder like {{Full Name}}. That placeholder is replaced with the real value every time the Zap runs. You can also open Format Data (the magic-wand option) if you want cleaner names or want to skip empty fields.
Step 11: Test the action.
Click Test this step (or "Test" in the Slack step). Zapier runs the message using your sample form response and posts it to #leads. Switch to Slack and confirm the message appears with the test values. If you don't see it, double-check that the channel exists and that the message isn't empty.
Step 12: Name it and turn it on.
Give the Zap a descriptive name — something like Google Form → Slack Lead Alert. Then flip the Zap switch to On (it starts out Off). When it's On, every new form submission will trigger the message automatically. Old submissions won't replay; only responses that arrive after you turn it on.
Step 13: Decide who owns it. A Zap you built in an afternoon needs a named owner before it becomes "nobody's problem" in six months. Options:
- You — if it's small and central to how you run the team.
- An ops or team-lead seat — the Zapier team plan lets you assign the Zap to a specific member, so alerts and edits land with them.
- IT — if your company centralizes automation there; hand them the Zap ID and this guide.
How to Verify It's Really Working
- Fill out your form in the browser with a real test submission.
- Wait ~15–30 seconds (Google Forms "New Form Response" is near-real-time; some other triggers on the free plan poll every 15 minutes).
- Watch
#leadsfor the alert. If it shows up with the correct name/email/message, your automation is live. - Check the Zap's Task History tab — you should see a green "Success" entry for your test.
Troubleshooting the Common Stumbles
- Nothing posted after a real submission — Confirm the Zap is switched On (not "Paused"). Check the Zap's Task History tab: if the Zap shows "Errors," click the entry to see why (usually a missing permission or a field name mismatch).
- The channel shows
#unknown— You selected the channel before connecting Slack, or the channel was renamed. Re-run Step 9. - A field is blank in the Slack message — The field name in your form changed. Re-open the message step and re-pick the correct field from the dropdown.
- Google/Slack asks you to re-approve — Permissions can expire or be revoked. Just re-approve when prompted; your Zap structure is preserved.
- IT blocks the OAuth — Many companies restrict third-party app access. Zapier has an enterprise tier (Zapier Central) built for this: SSO, SCIM, and centralized admin. If you hit policy walls, that's the path to take rather than working around IT.
Why This Matters (and Where to Go Next)
This isn't just about getting a notification. By mastering this basic Trigger → Action flow, you've built the foundational infrastructure for more complex agentic workflows — and for a manager, the payoff is leverage. One automation you can point at says "this is how we handle X now," and the team stops doing it by hand.
Once the "glue" is in place, the next steps get interesting:
- Add a second action: After the Slack message, create the lead in your CRM (HubSpot, Pipedrive, Salesforce) so the data lands in one system of record.
- Add a filter: Only alert for responses where "Budget" or "Team Size" is above a threshold, so the team stops getting pinged on low-fit inquiries.
- Add an AI step: Use an AI step to summarize the message, classify the lead's intent, or draft a first reply before a human ever sees it.
- Add a person step: Route high-intent leads to a specific owner in your team instead of a channel.
- Build a catalog: Keep a one-page doc of every Zap your team runs — what it does, who owns it, what it costs. It becomes the ops backbone of your automation strategy.
The takeaway: Start small. One automation at a time. Every Zap you build teaches you the same three moves — pick a trigger, pick an action, map the data — and those three moves scale from a five-minute Slack alert to a full multi-agent pipeline that runs parts of your operation without anyone touching it. The "agents" become much easier to deploy once the "glue" is in place.