Zapier + Gmail CRM: 7 Automations a Small Team Actually Uses

If you run a two-person business out of Gmail, the CRM is rarely the problem. The problem is the tools around it: the website form, the booking link, the proposal doc, the invoicing app, the newsletter list. Every hand-off between them is a place where a lead quietly dies.

Here are seven Zapier automations small teams keep switched on a year later, each with the trigger, the action, why it matters and the gotcha. The patterns work with any Gmail CRM that has a Zapier app; we note specifics for Teamopipe, our own product, where they differ.

One note first: some older third-party comparisons say Teamopipe has no Zapier integration. That is out of date. Teamopipe has instant triggers, actions and searches on Zapier, a public API and built-in automations, all included on every plan.

When to automate, and when not to

A good rule for a two-person team: automate the hand-offs between tools, never the conversations.

Hand-offs are mechanical: a form submission becomes a contact, a booked call becomes a deal, a won deal becomes an invoice draft. Nobody adds value by retyping that data, and every retype is a chance to forget.

Conversations are where a small team beats bigger competitors, because the prospect can tell a human wrote the email. Automating the reminder to follow up is smart. Automating the follow-up itself usually is not.

The test for any Zap: does it move data between two systems, or talk to a customer on my behalf? Build the first kind. Think hard before the second.

The seven automations

1. Website form → contact in your CRM

Trigger: new submission in Typeform, Google Forms, Jotform, Tally or your website's form plugin. Action: find or create a contact, mapping the company field to an organisation rather than a note.

Why it matters: the highest-value Zap for a small team. Without it, Friday-afternoon inquiries get copied over on Tuesday, if at all.

Gotcha: duplicates. Use a "find or create contact" step instead of a plain "create" so the same person submitting twice stays one record. In Teamopipe, a deal created from Zapier does not yet link to the contact automatically, so let the form create the contact, then create the deal from the person's email thread in Gmail, which links the two.

2. Calendly booking → a deal in your pipeline

Trigger: new invitee in Calendly (or Cal.com, SavvyCal, or a Google Calendar event matching "intro call"). Action: create a deal in your pipeline's first stage, with the invitee name as the title and the meeting time in the description, plus a contact for the invitee.

Why it matters: every booked call becomes a deal you can follow up, and you get an honest inquiry-to-call conversion rate.

Gotcha: bookings often arrive from a different email than the original inquiry. Check for an existing contact before creating a new one. Teamopipe's help centre has a step-by-step guide to creating deals from Calendly bookings.

3. Deal reaches "Proposal sent" → a row in your proposals log

Trigger: deal updated, filtered to stage = Proposal sent. Action: append a row to a "Proposals" Google Sheet with date, deal, amount and owner, or create a Google Doc from a template with the deal details filled in.

Why it matters: six months in, the sheet answers "what share of proposals over $5,000 do we win, and how fast?" without exporting anything.

Gotcha: "deal updated" fires on any edit, so a Zapier filter on the stage is essential, and the row can be added twice if someone edits the deal again. Rename a stage in the CRM and the filter silently stops matching, so write down which Zaps depend on which stage names.

4. Deal marked Won → invoice draft plus a Slack message

Trigger: deal updated, filtered to status = won. Action: create a draft invoice in Stripe, QuickBooks or Wave from the deal value and contact, and post the deal name and amount to a Slack channel.

Why it matters: the gap between "they said yes" and "we sent the invoice" costs small businesses a week of cash flow. A draft keeps a human in the loop for line items and tax.

Gotcha: Zapier will happily send "4500" to a tool expecting cents. Test with a $1 deal and inspect the draft before turning it on.

5. Deal marked Lost → nurture list

Trigger: deal updated, filtered to status = lost. Action: add the contact to a Mailchimp or Brevo audience tagged "nurture," with the lost reason as a merge field.

Why it matters: much of "lost" is really "not now," and a quarterly email to that list is the cheapest pipeline you will build. On Teamopipe Growth, built-in email campaigns can reach the same people without an external list.

Gotcha: consent. A quote request is not a marketing opt-in. Check your region's rules, and consider adding only contacts lost on "timing" or "budget."

6. Deals going quiet → reminder to the owner

What people try: a Zap that pings the owner when a deal has had no activity for 10 days.

Why not to build it in Zapier: Zapier fires on events, and "nothing happened for ten days" is the absence of one. You end up polling the whole pipeline daily and burning tasks. Use the CRM instead: Teamopipe's reporting dashboard (Growth and Pro) flags stale deals automatically, with a threshold you set; Streak and NetHunt have their own reminders and workflows. Better still, schedule the follow-up task when the deal changes stage, so it never goes quiet in the first place (see below).

7. New paying customer → onboarding pipeline

Trigger: successful payment or new subscription in Stripe, Lemon Squeezy or Paddle. Action: find or create the organisation and contact, then create a deal in a separate "Onboarding" pipeline.

Why it matters: the sale is not the end of the pipeline. Kickoff, access granted, first deliverable and a 30-day check-in are stages too, and tracking them stops you losing the customers you just won.

Gotcha: make sure a self-serve purchase does not also fire automation 1 and create a duplicate lead.

Built-in automations vs Zapier

Anything that happens inside the CRM belongs in the CRM's own automation builder. Anything that crosses into another tool belongs in Zapier, or the API if you have a developer.

In Teamopipe, built-in automations trigger when a deal is added, changes stage, has a field changed, or is won or lost. They can create tasks with due dates, update fields, add comments and assign records, with up to five actions in a row and no per-task cost. That covers the CRM-side half of automations 3, 4 and 5: for example, "when a deal moves to Proposal sent, create follow-up tasks due in 2, 5 and 10 days." Zapier then only does the hand-off to Sheets, Stripe or Mailchimp. Starter includes 3 automations, Growth 10 and Pro 25.

Two honest trade-offs. Teamopipe's integration catalogue is smaller than HubSpot's, so for some tools Zapier is the only bridge. And built-in automations do not send emails; for automatic follow-ups that stop when someone replies, use sequences on the Growth plan.

What automation costs across Gmail CRMs

Per user per month, as listed on each vendor's pricing page in October 2026:

Streak's free plan has no pipelines, and Zapier and automations need Pro+. NetHunt's workflow automation, sequences and API start on Business. Zapier itself is a separate bill on top of any of these. See the Streak and NetHunt comparisons, or our Zapier integration page.

What Zapier itself costs

Zapier bills by task, roughly one action run. The free tier allows a limited number of simple Zaps and tasks a month; paid tiers unlock multi-step Zaps, filters and more tasks. Several automations above use a filter or a search step, which usually means a paid tier. Limits change often, so check zapier.com/pricing rather than any blog post, this one included. Watch task counts in the first month: a busy form can use more tasks than everything else combined.

A 30-minute setup plan

1. Minutes 0–5: write down your pipeline stage names. Every Zap depends on them not changing.
2. Minutes 5–15: build automation 1 with a find-or-create step. Submit a test entry and check the contact appears.
3. Minutes 15–22: build automation 4. Mark a $1 test deal Won and inspect the draft invoice.
4. Minutes 22–27: in the CRM, add a built-in automation that creates follow-up tasks when a deal moves to Proposal sent.
5. Minutes 27–30: turn on Zapier's error notifications. Add automations 2, 3, 5 and 7 next week, one at a time.

Connecting Teamopipe takes a workspace API key from Settings → Integrations; the Zapier help article lists every trigger, action and ready-made template. The 14-day trial includes Growth features and needs no card.

FAQ

Does Teamopipe integrate with Zapier?

Yes, on every plan. Teamopipe has instant triggers when a contact, deal, organisation or task is created, updated or deleted; actions to create or update contacts, organisations and deals and to create tasks; and find or find-or-create searches.

How do I connect a website form to my CRM with Zapier?

Use your form tool's new-submission trigger, then a find-or-create contact action in your CRM, mapping name, email, phone and company. Test with your own entry before turning the Zap on.

Should I use Zapier or my CRM's own automations?

Use the CRM's automations for anything that stays inside the CRM, such as stage-change rules, tasks and field updates. Use Zapier for hand-offs to other tools like Calendly, Google Sheets, Stripe or Mailchimp.

Can Zapier trigger on won or lost deals?

Yes. Use the CRM's "deal updated" trigger with a Zapier filter on status. Bear in mind it may fire again if the deal is edited after being marked won.

Which Gmail CRM is cheapest if I need automation?

As of October 2026, Teamopipe Starter at $19 per user per month (annual) includes Zapier, the API and 3 built-in automations. Streak needs Pro+ at $69 for Zapier and automations, and NetHunt needs Business at $60 for workflow automation.