r/zapier

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'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)

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)

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.