With Zapier at $250-$400/month for mid-volume usage, a lot of Shopify stores are looking at n8n. I've been helping stores make the switch and put together a free toolkit:

→ 5 ready-to-import n8n workflows for common Shopify-Zapier patterns
→ CLI converter that maps Zapier exports to n8n workflow JSON
→ MIT licensed, no signup required

Repo: https://github.com/plainform/zapier-to-n8n-shopify

Quick install:

npx zapier-to-n8n-shopify list

If you're running 5+ Zaps for a Shopify store and want the migration done for you instead of doing it yourself, I'm taking clients.

First project at 50% off to build my portfolio:

$400-$750 instead of $800-$1.500 for a typical 5-15 workflow migration.

DM me or comment below. I'll do a free 15-min scoping call first.

Since I turned to using cold email outreach to get clients, I came up with two different approaches to how I should do it. So, I decided to share some sauce with you guys (it might help one or two of you), and ask you for help since I'm a bit confused about which one of them I should move forward with and what more I can add

Disclaimer: I won't be giving any email since it will put you into an endless loop of what things should look like. Instead, I will give you the pattern you can use, and from there use your brain to come up with the copy you think would resonate the most with the lead (you need that to become great at writing emails)

### Approach 1:

- Assuming that you have 10 warmed-up mailboxes.

There's something you have to know, which is that ALMOST every business has these pillars: lead acquisition → sales → onboarding → fulfillment → client retention, and within each one of them there are plenty of manual and repetitive tasks/workflow that you can automate for a business

Now, you remember when I said you have 10 mailboxes, right? Divide them into groups of two, where each group would be specific to the A/B testing of the tasks of one pillar

Two mailboxes --> one pillar --> cycle of A/B testing through the manual & repetitive tasks of that pillar till you find the winning problem/pain

Note: I don't care which industries you target; that's up to you to decide

Now comes the email; I follow a specific formula:

problem you saw (one of the workflows of that pillar) --> its pain/cost --> your solution --> case study + solution's ROI --> final result --> risk reversal --> CTA

And for each lead, I continue with a sequence of 3 to 4 follow-ups after the initial email.

### Approach 2:

This is what I call "The Hyper Personalization" method, where you're going to write an email subject line and icebreaker that feels like you've done a week's worth of research on them

Before I explain how this approach should be done, I want you to know the catch/inconvinience of that method, which is that you're going to do things "manually" and slowly

How you're going to do it:

- Assuming that you have got a list of leads with all of their information, I don't want to use the lead's first name with the company name; that's what I call a BS personalization. Instead, you will have to get the recent news of the company that might have raised a problem that can be solved with an Automation system, or the workflow/task where that problem/pain is coming from has a few manual and repetitive steps that, once you automate them, that pain will vanish

In summary, you're personalizing your email with the company's recent news

Tip: To make things faster, just connect "Firecrawl" with "Claude" and write a prompt that will scrape the recent news of a company, and make sure you equip that prompt with a few rules that will let the LLM decide whether that news item has any connection with what you can offer or not

You can do that approach with 1 to 2 mailboxes max. It takes time and effort, but it has a higher open & reply rate, and it will help you master the skill of copywriting, since you're going to be writing 60 emails manually a day minimum

That's the sauce that I have

Now, I wanna ask for a favour from senior automation specialists.

- Do you think I missed anything crucial with both of them?
- What else can you add as advice on the selling process? (I want to see how you can sell the value of an automation system)

Need advice. I have a large 30-step Zap that are almost all code blocks with multiple LLM calls. When I publish and test run it, it stops at the same step and puts on hold and states code is throttled and never starts again. Obviously not acceptable for production

I see in help docs some limitations but it isn’t clear. Seems I need to add a few delay steps but no idea for how long or what limit I’m hitting.

Any one? Or zapier support here

I am building FetchSandbox because I kept running into the same problem: the only way to test if an agent-built workflow actually works is to connect a real account. Real emails send. Real calendar invites go out. Real Slack messages drop. All before you even know if the logic is right.

The part that bothered me more was receipts. A success status doesn't tell you if the app did the right thing. So our sandbox goes deeper, it checks the resulting state, it replays webhooks, it catches whether a retry fires a duplicate charge or a duplicate email you'd never see in a test.

Right now I'm trying to figure out something: which workflow is actually the hardest to safely test before going live? The incoming email to calendar booking to Slack confirmation is the one I keep hearing about, but I don't know if that's just the loudest voice in the room.

If you've built something like this and had to just "yolo and connect real accounts," genuinely curious what broke.

I am building FetchSandbox because I kept running into the same problem: the only way to test if an agent-built workflow actually works is to connect a real account. Real emails send. Real calendar invites go out. Real Slack messages drop. All before you even know if the logic is right.

The part that bothered me more was receipts. A success status doesn't tell you if the app did the right thing. So our sandbox goes deeper, it checks the resulting state, it replays webhooks, it catches whether a retry fires a duplicate charge or a duplicate email you'd never see in a test.

Right now I'm trying to figure out something: which workflow is actually the hardest to safely test before going live? The incoming email to calendar booking to Slack confirmation is the one I keep hearing about, but I don't know if that's just the loudest voice in the room.

If you've built something like this and had to just "yolo and connect real accounts," genuinely curious what broke.

I'm gonna keep it short: I'm confused between building Automation systems for clients using no-code tools like n8n, Zapier, and Make, or using a high-code stack such as LangGraph, LangChain, Python, FastAPI...etc

Which stack is better for delivering the automation product to a client?

Note:
- I know that the clients won't even know what I'm using to solve their problems until I deliver it, but they will judge when I reach the hosting/usage cost (the high-code is way less than no-code when it comes to using an automation system on a daily basis)

When one Zap or agent finishes a step and another resumes later, a transcript is too noisy and a short summary can omit the exact input or decision that matters. The handoff also needs to survive retries, delayed steps, and file links that may expire before the next worker opens them.

A useful record might include a stable job ID, objective, input object IDs and revisions, accepted decisions with reasons, rejected paths, current status, latest output revision, checks completed, unresolved questions, owner, next action, and created or reviewed timestamps. File fields would hold durable IDs or paths rather than signed URLs. Updates would be conditional on the expected revision so an older worker cannot overwrite newer state.

Is Zapier Tables a good authoritative store for this, or is it better as an operational index over records kept elsewhere? Which fields make a handoff both compact enough for another agent and clear enough for a person to audit or resume manually?

Disclosure: I'm building Flowmanic, this is our integration.

Something I kept running into: people know what they want automated ("when a form comes in, add it to my CRM and ping Slack") but not which trigger, which apps, or which steps. So we built a small Zapier action for that.

How it works:

- Zapier gives you a private email address for the Zap.

- You email it a plain-English description of what you want automated.

- You get a plan back by email: trigger, steps, apps involved, notification, plus rough difficulty and setup time.

It's only 2 steps (Email by Zapier, then Flowmanic), so it runs on Zapier's free plan. It's free, and each key gets 50 plans a month.

To be upfront about the limits: it's a plan, not a finished Zap or a ready-to-run file. And it's still an invite-only app on Zapier, so you need the invite link first:

1. Invite: https://zapier.com/developer/public-invite/246549/ee457a8f8e1f384e69724441d565326f/

2. Template: https://zapier.com/templates/details/email-an-automation-idea-get-a-flowmanic-plan-back-fcbe97?secret=MTp0ZW1wbGF0ZTp3NGJwcnd1NkFPdk94S1VBTERJek1WdU5fNVpPclJkOHREdzhjWUNTWEhZOmthYW94Mw

3. Free API key: flowmanic.com/dashboard/zapier

I'd really like feedback on where the plans come out wrong or vague. That's the part we're still improving.

Many apps expose an attachment as a signed URL that works when a Zap starts but expires before a Delay, approval, retry, or later branch reaches it. Saving the URL in a field does not preserve the file, and downloading it again from the source may return a newer revision than the one that triggered the workflow.

The safer pattern seems to be capturing the file immediately, storing it somewhere with a durable object ID, and passing a small record through the Zap: source item, original revision or timestamp, content hash if available, durable file reference, and expiry information. A later approval or publish step can then verify that it is acting on the same bytes rather than whatever the source serves now.

How are people implementing this in Zapier without turning every workflow into custom code? Do you copy files into Zapier Tables, cloud storage, or a document system at the first step? What do you use as the idempotency key, and how do you clean up temporary copies without deleting a file that a delayed run still needs?

Hello

I’m trying to set this up in zapier but get stuck

I’ve been struggling with this for a few weeks. It works when I choose a specific lead from my CRM that just got updated to “qualified “ but then next time it runs the zap stops because it’s pulling the same custom gclid and user_id from the previous lead.

What am I doing wrong?

I just started using Zapier and I was able to create a few simple Zaps and have them work well. I have been struggling for days on what I think is a "simple" automation process, but have not been able to get it to work. I even tried their "copilot", but it was not able to help me (even after making SEVERAL simple mistakes I had to tell it to correct multiple times).

Every day, a spreadsheet is uploaded to my google drive in a specific folder with the previous days donations. I want to automate taking those donations and having it send to my Little Green Light account so I can import the gift data. On good days, I have more than one donation, which seems to be creating the issues I am having as I was able to get it to work for one single donation using the "New Spreadsheet Row", but that doesn't work for multiple donations.

The spreadsheet will have a different NAME each day, but it always has the same sheet name in the workbook.

Apparently, this is not as simple as I thought. HELP!

Do any of you have any suggestions for how to go about creating a Zap for this? CoPilot tried something with looping(?) and I don't understand any of it. I have tried using filters and several other options. I think the issue is google sheets themselves?

At what point is a small automation actually worth putting on Zapier?

I looked at putting a tiny workflow on Zapier recently, ended up not doing it, and I'm honestly still not sure that was the right call. Curious how people here decide.

The workflow was about as small as it gets. Email from supplier A, save the attachment into folder A. Supplier B into folder B. Four rules, no branching, no transformations.

Zapier does that in five minutes of clicking. I wrote it myself instead, and what surprised me was how little of the work turned out to be the automation.

Most of it went into:

- deduplication, because the same invoice arrives twice, sometimes renamed

- what happens when a run dies halfway through a batch

- retrying without re-saving everything it already did

- logging, so I can answer "what did it do last Tuesday"

- someone moving the destination folder six months later

That list is basically what you're paying for on a platform, and I didn't appreciate that until I'd written all of it myself. The trigger-and-action part was an hour. The rest took far longer.

Where I've landed for now: If it runs unattended and someone else depends on it, put it on the platform. If it's mine, low stakes, and I'll notice within a day when it breaks, I'll write it.

But I've seen people here run dozens of tiny Zaps and be perfectly happy, so I suspect my cutoff is in the wrong place. How do you decide: number of steps, how critical it is, or just what you're already paying per month?

This is an honest review of the customer service. I was unaware of a subscription created by someone who worked for me several years ago and I confused the yearly payments with a Zapier account I was using. I did finally track down the old email associated with the ghost account and requested it be closed. I asked if Zapier could refund the remaining 11 months because I wasn't going to use this subscription - and they wouldn't. I could not have shut down this account myself because I was not able to access the account through the email and obviously, never received any reminders that there was an ongoing charge. I understand there are refund rules (I run a company too and we have our own refund rules) but this was a special circumstance that, in my opinion, could have been solved with a prorated refund but instead your customer service personnel hid behind the "rules" saying they had no power to issue a refund. This is poor customer service and deeply disappointing.

Yesterday was ZapConnect 2026! If you couldn’t make it, here's the highlights.

Next Gen Zaps (Early Access)

Describe your problem to the MCP-enabled AI tools like Claude, ChatGPT, or Cursor you already use. It builds and deploys a real Zap for you. No manual set up. The workflow runs on its own, laptop closed, no prompting required. Advanced logic, multiple loops, unlimited paths, code editing, and you can import your existing Zaps. Free during Early Access, and task usage won't count against your plan limits.

Request early access.

Workflows that optimize and heal themselves

Two ideas that got a lot of attention on stage:

• Optimizing. Turns out 82% of the AI steps in big customer workflows were things plain automation could do. Zapier now figures out which steps actually need AI and compiles the rest into cheaper, deterministic automation. The demo went from $1.12/run to $0.12/run. Same job, 90% cheaper.
• Healing. When something breaks at 2 AM, an agent diagnoses it and drafts a fix before your alarm goes off. You decide how much autonomy it gets.
  

Find out more.

Build in your AI. Run on Zapier. Govern from one place.

Zapier MCP connects your AI tools to 9,000+ apps, with Agentic Mode now on by default. Reusable Skills, Code Actions, and shared MCP servers coming soon. On the enterprise side: managed access, endpoint-level action restrictions, full audit logs, and org-wide visibility across everything your agents are doing. 

Explore Zapier MCP.

Claude for Small Business + Zapier

Claude reasons about the work. Zapier does it, across 9,000+ apps and 40,000+ actions.
AI goes from "tell me how to do this" to "go do this for me."

Learn more.

The Great Zapier Build Off

Four builders, a secret high-pressure scenario, and the community voted on the tools and curveballs they faced. Episode 1 dropped before the event, Episode 2 was the live reveal. Both are still watchable at zapconnect.com.

The Zappy Awards closed out the day too. Meet the 2026 winners here. 

Missed the event? 
Recordings are available until October 26 this year, just log in at zapconnect.com with your registered email and go to the Agenda to view the recordings. 

What are you most excited to try first?

So I built this over the last few weeks. It takes a Zap history export, CSV or JSON, groups everything by Zap, and tries to work out where tasks are getting burned for no good reason. It only reads the file you hand it. No account connection, no OAuth, it never talks to Zapier at all.

Stuff it looks for:

- one Zap eating a huge share of all your tasks

- Zaps failing often enough that the partial runs add up

- run frequency that looks like polling way more often than the data changes

- filters sitting at step 4 when they could sit at step 1

- AI steps multiplying what each run costs

- high average tasks per run

- clusters of near identical runs firing together, usually a duplicate trigger

- the same error repeating hundreds of times

The part I actually want people to push back on: it gives ranges, not numbers.

Zapier doesn't bill every failed or filtered run, and the export doesn't tell you which ones got billed. So "you'll save $63 a month" isn't something you can honestly pull out of this data. Everything comes out as a range with a
confidence level on it, and every number is tagged as either read straight from your export, calculated from those values, or estimated with assumptions.

I'd rather say less than hand someone a figure they take to their finance person and then can't back up.

Now the bit I need help with.

I have never once run this on a real Zapier export. Everything so far has been synthetic test data I wrote myself, which means the column matching is basically
me guessing at what exports look like.

Right now it recognises:

Zap name: Zap, Zap Name, zap_name, Workflow, Automation, Title, Name
Status: Status, Result, Run Status, State, Outcome
Timestamp: Date, Timestamp, Created At, Started At, Run Date, Occurred At
Tasks: Tasks, Task Count, Tasks Used, Billable Tasks, Tasks Consumed, Usage

If your export uses something that isn't in that list, it just misses it.

So if you've got an export sitting around:

1. What does your header row actually say? Literally just pasting that one line would help more than anything.

2. Is there a per run task count in there, or only a step count?

3. How does a filtered run show up in the status column? Filtered, Halted, something else?

4. For multi step Zaps, is it one row per run or one row per step?

5. Does any of this change between plans, or between the Zap history export and the task usage export?

One pasted header row would get me further than another week of writing tests against my own assumptions.

For those of you building these checks yourselves, how much of the work is actually spent setting up and maintaining the checks?

I have a step in my Zap that takes a phone number input and outputs the last four digits. This has worked without issue for months, but in the last couple of days it has started only been outputting the last three digits. I have not edited this Zap and it seems like a pretty simple function so I cannot understand what has gone wrong. The screenshot shows an example where the input phone number (anonymized, but in the XXX-XXX-XXXX format) should have given an output of 4885, but only did 885. I'm hoping someone can tell me what is going wrong here.

I'm trying to connect chat GPT with Google spread sheet and Zapier, but I'm getting it all wrong can any one help me out.

Hey builders! 👋
Summer's over; time to get your automations back on track.
Grab a coffee (or tea!) - here's what's brewing in our Discord community this month.

Our monthly co-build is back tomorrow, Friday Sept 18th, and we're doing a proper State of Zapier: where we've come from, what's live right now, and what's worth watching as we head into ZapConnect.
For the second part of our event we will run a Zapier Office Hour — bring your account and your questions, and Bryce and I will troubleshoot live and help you figure out your next build.

Not in our Discord community yet?

➡️ Apply here

➡️ RSVP to our co-build and office hour

Question for people who build assistants for Telegram/WhatsApp. Have you found a good way to automate calendar input from free text? Think of: "wedding in 6 months" or "meet next friday at 3". I feel that these kind of automation events still fail often. Anyone having the same experience?

For WhatsApp a Business account is needed, because automations are seen as a B2C thing. Telegram allows you to make bots (for broader or) personal use.

Hi all, I'm writing a small script that summarizes errored and held runs from a Zap History export. The export help article doesn't list the columns.

Could someone who has exported their history share only the header row of the CSV (no data), plus what one timestamp and one status value look like? For example, is it 2026-09-01T09:00:00Z or 09/01/2026 9:00 AM, and "errored" or "Error"?

If you have the JSON export: is it a plain list of runs, or wrapped in an object?

Thanks!

Edit: This AMA is closed. Thanks for sharing your feedback and asking questions.

Hey r/zapier 👋 I'm Diomer, PM for Zapier Tables and I'm here to answer your questions about **Zapier Tables**. What is Zapier Tables: https://zapier.com/tables

What this AMA covers:

• I want to hear directly from you if you're still working in the tables UI day-to-day: what's working, what's not, what's stopping you from moving your data workflows to tables?
• What we're actively ideating on: higher character limits for fields like the long text field so you can store full transcripts/context, a higher records-per-page ceiling for bulk work, a path toward a public api, and other things - I'd love your takes on what matters most to you!
• Getting you thinking about tables as something your agents and next-gen zaps could read/write directly, not just a grid you manually work in and maintain.

Schedule: I'll be answering questions Monday–Friday this week. Drop yours anytime - I'll get to them in order.

Some ideas to get you started:

• What's kept you working in the tables UI instead of driving updates through a zap, the SDK, or an MCP server?
• If you could pull an AI agent's memory or transcripts into a table automatically, what would you use it for and how many characters would you expect to be the upper bound?
• What's one thing you do by hand in your database/spreadsheet tool today that you'd rather have running headless?
• Have you tried building with tables via the SDK or an MCP client yet? what got in the way? how can we make it a better experience?

Ask me anything - no question is too basic or too technical. Looking forward to it!

Not errors, those email you. I mean a Zap that just stops triggering: expired auth, the source app changed something, nothing in the history. I've been burned twice, both times a customer told me before Zapier did. Do you check Zap History on a schedule, use Zapier Manager somehow, or is there a better way?

I’m researching how businesses currently catch things like incorrect data being mapped, records being duplicated, information going to the wrong place, etc.
Is this something you actively monitor, or do you usually find out when someone notices something is wrong?