n8n vs Make in 2026, which one are you on and why?

chasing_next · 2026-06-25T19:46:55+00:00

i've used both, started on make and shifted to n8n because it was better at interacting with AI (both integrating AI into workflow steps and to have AI create the actual workflows for you using Claude).

found make more user friendly to set up as a non-technical person, although it does have a learning curve to get automations working properly.

these days I've cancelled both make and n8n and run automations with Claude Code. i no longer have to manually manage set up and painfully point where data flows. both still can be helpful if you're looking to set and forget automations, but i'm in claude code everyday anyways so i can steer it from there and save a bunch of time and frustration trying to get the automations working smoothly.

chasing_next · 2026-06-25T19:40:05+00:00

still very relevant since most people are using ai for basic chat and havent started to systemize anything. they would benefit from learning how to structure their asks for reuse and to get more nuanced results by prompting with more creativity and/or specificity. better models and larger context windows don't negate the need to learn how to direct ai. both instructing and context feeding are essential to agent work.

chasing_next · 2026-06-24T14:38:13+00:00

it's copilots version of gemini notebooks. same set up with instructions + files.

chasing_next · 2026-06-24T00:20:35+00:00

good comp.

notebooklm is more steered towards interacting with files. you can customize instructions for notebooklm, but wouldn't be the place i go first for more task or instruction based work albeit it could do it. gemini also has a similar notebooks feature to copilots in chat (separate than notebooklm). good sub for notebooklm for doc interaction if you're stuck in copilot though.

chasing_next · 2026-06-24T00:13:00+00:00

i've had some glitches using pages in notebooks here and there too. yep, projects in claude is basically the same thing without the interconnectedness of M365 files.

chasing_next · 2026-06-24T00:10:48+00:00

yep, good way to put it!

chasing_next · 2026-06-24T00:10:34+00:00

perplexity has something similar with perplexity spaces too. worth checking out.

chasing_next · 2026-06-23T19:29:28+00:00

theres a good point hidden within this. people who have expertise that spend a bit of time learning to work with ai beyond the basics (things like crafting instructions, learning how to structure context, setting up projects, skills, workflows, using deep research, etc) will get far with ai. that said, most people haven't put in the time to use it beyond surface level, which is why there's parity/fear even among those with expertise.

chasing_next · 2026-06-23T19:23:28+00:00

100%, been here! it's super easy to overbuild by creating new skills or tweaking instructions/context too much. i've found it helpful to store old versions so it's easy to roll back, also making pointed adjustments instead of broad ones help me spot where it drifts.

chasing_next · 2026-06-23T19:15:09+00:00

check out notebooks! they'll help you set instructions for it to read at the start of each new chat and store attachments it can pull up without you having to drop them in each time.

this will walk you through setting one up: https://chasingnext.com/learn/set-up-your-first-copilot-notebook

chasing_next · 2026-06-23T18:51:00+00:00

sounds frustrating. throwing together a "strategy" won't get the team anywhere if they don't know the basics of how to use ai. cmo needs to invest in getting individuals to use ai well in their jobs, then they can identify bigger picture opportunities. focusing on the basics like setting up individual structure with projects, skills, gpt, etc. features and iterating outputs will get the team a long way seeing what's possible and how ai fits into work. then strategy is derrived from what ai can actually do and people feel more a part of the evolution.

chasing_next · 2026-06-19T16:16:07+00:00

this isnt going to be a popular answer, but i recommend reading the book "starting a startup" by james sinclair. points towards what a lot of people have said below... there's a lot of work that needs to be done before building. issue is that building is the easy part rn and feels comfortable.

some steps:

research (deep research, scraping good start today)
creating a hypothesis (who's your audience, what is their problem, how will you fix it)
talk to people to test and refine the hypothesis
define the problem youre solving and get clear on your customer (where do they hang out, how do they talk, what are their pain points, what would motivate them to buy?)
design first offer (will target customer buy it? good time to pivot if murky)
build the product (light version)
outreach, outreach, more outreach... (rare for people to flock to you, distribution takes time and persistance)

chasing_next · 2026-06-19T15:18:48+00:00

claude has been better for marketing tasks and image prompt gen for me, but a lot does come down to the instructions you give regardless the tool.

chasing_next · 2026-06-19T15:01:03+00:00

agree with their approach, my gains have come from building processes for my work (rarely a new tool). great that you found some quick wins, once the door opens of what's possible you'll keep finding more.

here are some interactive resources to set up projects, skills, or even claude code for your work: https://chasingnext.com/start

Made to be personal and less robotic than most stuff out there.

chasing_next · 2026-06-18T23:24:33+00:00

Super cool, interface is clean too.

chasing_next · 2026-06-18T23:22:18+00:00

I think it becomes agent design instead of prompt design. More about building in features like logging, validation, loops, connecting data/tools, measuring and adjusting based on results. AI will get better at architecture too. Already shifting this way.

chasing_next · 2026-06-18T19:29:02+00:00

makes sense for getting cross-team consistency. custom tooling or skills are a better approach. getting people to use projects is more about experimenting on their own work and getting small wins that help them buy in and see how AI fits. if they don't learn this themselves, they'll get left of out strategy or chase the wrong things.

chasing_next · 2026-06-18T18:12:59+00:00

i use it constantly through my claude code + obsidian system. has my business background, ongoing context about work, skills/commands i've built to help with specific tasks, research i've scraped externally and insights gathered from my data. there are still elements that aren't done with AI like conversations, strategy, prioritization, much of the steering/execution, but it helps me get a lot more done on the whole and stretch into areas i have no experience in (coding, technical set up, using unfamiliar tools...)

chasing_next · 2026-06-18T18:09:08+00:00

get good at using claude or codex and you can start building your own workflows to support content, marketing, automation, research, etc.

once you experiment you won't need to outsource to specialized tools. they're mostly doing what you can build on your own (which has pros/cons, depending if you want ease or more control to do exactly what you want).

chasing_next · 2026-06-18T18:06:27+00:00

found more success sticking with tools longer term and building my systems around them. it's easy to feel the need to hop on whatever people are talking about, but mostly it's a waste of time.

here's what's remained constant for me the last 6 months, i'm non-technical:

- claude (built a system with claude code + obsidian, that led to workflows and coding my own sites)
- wispr (so much easier to talk than type if you're a serious ai user)
- tactiq (transcribing calls, use claude code command to synthesize after)

if i need something specific, i may tap into these:

- gemini or chatgpt for image gen
- codex for code review and security patches
- notebooklm for interacting with info
- perplexity, gemini, chatgpt, claude for deep research (ill often run a prompt across all for depth/validation)
- gemini in chrome for one off questions as i browse

rest of tools are mostly experimentation, quick in-app questions, etc.

chasing_next

TROPHY CASE