n8n vs zapier vs make vs dugong
I find make the easiest => zapier=> n8n. Anyone can help with things n8n can which cannot. It’ll help choose the platform for future complex scenarios.
I find make the easiest => zapier=> n8n. Anyone can help with things n8n can which cannot. It’ll help choose the platform for future complex scenarios.
Has anybody found a simple solution to connect Whatsapp + Gemini / Claude to automate responses in incoming messages?
I rely heavily on Make and Zapier, and my recent OpenAI bill just made me sick.
I checked my logs and saw that GPT-4o is handling literally everything. I'm paying premium prices for things like simple paragraph summaries and basic grammar checks.
I’d love to just route the easy stuff to GPT-4o-mini or Llama 3, but trying to build a dynamic routing system based on prompt complexity inside Make/Zapier feels way too complicated for what it is.
How are you guys handling this? Are there any good tricks or simple setups to stop bleeding money on easy prompts?
I'm setting up Zapier to connect data from our sales software to our new CRM database we just launched. I believe I need the Zapier Professional account. Appreciate if folks can confirm that it will be sufficient for our needs! (or if we could get away with the free account)
Is each piece of data associated with a trigger one task? E.g. if we're sending a new contact record over, with 10 pieces of data (name, email, address, etc.) that counts as 15 tasks? If so I count 600 to 1,000 tasks per month and we need to upgrade to Professional tier 2
thanks so much!
6 client zaps, pdf step at the end. test runs fine. live form at 11pm, empty attachment, three error emails, im the one getting paged.
tried built in converter, docsautomator, that monkey template everyone swears by. success badge green. pdf blank or 47 pages of css garbage??
two afternoons and my notion fix list is embarrassing. dont open it.
one pdf per airtable row, dynamic fields, under 2mb. cant babysit at 2am..
Built a workflow this week that watches a project inbox for incoming revision requests, uses an AI node to parse what the client actually asked for, logs it against the right project in a tracking sheet, and fires back an acknowledgment with a turnaround window before anyone has to manually touch it. The problem it solves is pretty simple: when an inbox gets busy, revision requests get buried, clients assume they were ignored, and whoever is running the project is now doing damage control instead of actual work. This is one example of the kind of back-office work we put on autopilot for businesses - the stuff that is invisible until it breaks. Put a walkthrough on YouTube if you want to see how it's wired together.
Hi everyone,
My name is Zekun Wu, and I am a researcher at Saarland University, Germany.
I am currently conducting a short research survey on how people use workflow automation tools such as n8n. In particular, I’m interested in a simple but exciting idea: what if, after an AI helps complete a task, it could leave behind an editable workflow that users can inspect, fix, and reuse?
This survey helps us understand how real workflow users think about workflow understanding, debugging, and reuse in practice. It should only take about 5–10 minutes to complete.
Survey link:
https://forms.gle/uXmWdavWJuRqnFfr8
As a small thank-you, we will select up to 10 participants who provide especially thoughtful and relevant responses to receive a €10 Amazon eGift card. This is not based on whether your opinions are positive or negative — detailed and honest experiences are what we value most.
Your feedback would be very helpful for shaping our future research and prototype design. I would really appreciate it if you could take a few minutes to fill it out. Feel free to also share any thoughts or examples in the comments.
Thank you very much!
Best,
Zekun
Hi specifically, how do you all handle designing a dynamic pdf template and generating it via an automation in Zapier?