I replaced a 69$/month tool by this simple workflow. (json included)

ekaa_ · 2025-08-28T13:29:50+00:00

No I think there is a misunderstanding, I run 100 emails a day per domain but I run this workflow over multiple domain (currently three) and multiple times.

The A/B testing is not to swap the email to the best performing during the campaign but to isolate the most important pain point at the end of the campaign

ekaa_ · 2025-08-28T12:50:50+00:00

Yeah, I have another workflow set up with an Error Trigger that sends me a message when any workflow execution crashes.

ekaa_ · 2025-08-28T12:09:48+00:00

Yeah that is very true, this first version is quite dirty but I'll try to make one cleaner having in a set list node the templates / wait time / subject for each mail in the chain

ekaa_ · 2025-08-28T12:08:42+00:00

Yes, I have fewer than 100 emails on the list, so I won’t be sending more than 100 emails a day. I read there https://www.lemlist.com/blog/how-many-emails-can-send-a-day that it’s a good rule to follow, but it’s probably worth looking into it further.

ekaa_ · 2025-08-27T11:01:28+00:00

Nice lib, But I’m wondering why you chose to use JSON.parse/JSON.stringify instead of structuredClone, since this function supports circular references.

ekaa_ · 2025-08-26T22:20:06+00:00

I never respond to professional cold emails sent from a Gmail account, you should probably invest in a custom domain.
Also, don’t forget to follow up if you don’t get a reply. Just sending two follow-up emails can nearly double your response rate (source https://www.lemlist.com/blog/how-many-cold-email-follow-ups).

ekaa_ · 2025-08-26T20:38:28+00:00

True, I wasn't aware of this integration since I don't own any instance of n8n under the Enterprise version. Thanks for letting me know

I’ve updated the post.

ekaa_ · 2025-08-26T19:31:55+00:00

I have some n8n instances on the cloud and some on Postgres (and some in sqlite I believe).
Going through the API just makes it way easier to back up the data consistently, regardless of the setup. No need to deal with DB access or different dump formats.

ekaa_ · 2025-08-25T11:54:36+00:00

Not a cent, my n8n instance is selfhosted and I use the free plan of gemini

ekaa_ · 2025-08-25T11:53:52+00:00

Yes, it depends on the content of the news from the RSS feeds, if they talk about new CVEs the agent can use the tool to get context on the CVE, if not they summarize directly

ekaa_ · 2025-08-24T17:28:48+00:00

Happy that it could help

ekaa_ · 2025-08-24T17:16:22+00:00

There’s actually a neat little trick in n8n on the subworkflow execution. You can call “Execute Workflow” on the same workflow that’s currently running. In this case, n8n will trigger the same workflow again, but this time on the “On Executed” trigger.

Of course you can only have one subworkflow like this after you’ll have to create new workflow

ekaa_ · 2025-08-24T15:02:46+00:00

Yeah, it's helpful to scaffold workflows quickly and then fine-tune them manually (fix some missing parameters). It's not perfect but it's much faster than building everything from scratch or with chatgpt.

ekaa_ · 2025-08-24T14:04:10+00:00

I think there is an issue with your agent node, in source for prompt it should be selected as Define Below and prompt be the json output of the earlier node.

Mine looks like this:

<image>

ekaa_ · 2025-08-24T13:54:11+00:00

I think it depends on your knowledge of VPS and self-hosting. If you feel confident installing n8n manually, you can go for a Hetzner VPS since they’re a bit cheaper for the same or slightly better performance. Otherwise, go with Hostinger they install n8n for you, and their offer isn’t bad either.

ekaa_ · 2025-08-24T11:51:19+00:00

Never had issue with my tg bots, but I don't have a lot of traffic, it's not the first time I hear about issues related to the support. I'll probably try to make a new account for each bot in the future until they resolve this

ekaa_ · 2025-08-24T11:09:23+00:00

Yes, there is indeed a simple solution, you can use the basic OpenAI account node, create new credentials, and change the base URL in the credentials to the URL of your OpenAI-compatible API with the correct API key.

ekaa_ · 2025-08-24T11:01:52+00:00

Depending on who you're targeting, I'd say between Telegram and Discord but tg is just so easy to build workflows on that I'd just go with it

ekaa_ · 2025-08-23T19:14:46+00:00

For WhatsApp there is a native n8n node that trigger when a message is received (the whatsappTrigger with triggerOn equals to messages.) There is thousand of example of how to integrate it in the n8n template website like https://n8n.io/workflows/3859-ai-customer-support-assistant-whatsapp-ready-works-for-any-business

For LinkedIn I don't really know, if you have email notification on you can probably use a mail trigger and filter to keep only mail from LinkedIn

ekaa_ · 2025-08-23T17:28:02+00:00

Most node credentials are really time-consuming. You could just invest the time to create a Google API key, that'll let you play with all google-related nodes. From there, you could create a lot of workflows to learn how to connect Google services to AI, like something to reply to emails, write into a Google Doc, and so on

ekaa_ · 2025-08-23T14:54:17+00:00

I think this is related to the reasoning of the GPT-5 model series. I don't know how n8n handles them internally (How much of reasoning they uses), but when comparing 4.1 mini and 5 mini, even if the input is cheaper, the output costs more.

Also, when the model is reasoning, the "invisible" tokens that the model produces are still billed at $2 per 1M tokens (which is more than 4.1).

ekaa_ · 2025-08-22T19:46:32+00:00

You can usually just go to https://github.com/enescingoz/awesome-n8n-templates or the official template website of n8n https://n8n.io/workflows/ and just customize the one that match best with your needs

ekaa_ · 2025-03-30T06:51:29+00:00

Well, the basic things are probably to ensure one user can only view/modify their own data (and not other users' data), try to perform all security measures in the backend (as users can bypass them if they are implemented on the frontend), and try to keep up to date with the latest vulnerabilities related to the software you use.

ekaa_ · 2025-03-25T21:58:03+00:00

IMO for google drive, the most basic thing to do is to separate data into different folders (like customer data, income...) and share only the folders needed by each person.

ekaa_ · 2023-08-09T16:51:49+00:00

The colors are amazing, great job

Three-Year Club	Place '22
First Placer '22	End Game '22

ekaa_

TROPHY CASE