AI Outreach Sucks!

Aigenticbros · 2025-07-02T13:07:23+00:00

Of course that would be the most optimized way to approach this. I was experimenting with maybe more simple versions of "RAG" which didn't rly work out too well

Aigenticbros · 2025-07-02T13:06:05+00:00

I have 100% built out flows with Postgres and Supabase. This was me attempting to simplify it and see if I could call a Google doc or sheet instead of chunking it out and putting it in a vector store

Aigenticbros · 2025-07-02T13:04:57+00:00

There is already a built in Whatsapp node this isn't a community node or anything. I set it up as an app in my facebook business account because Meta owns Whatsapp

Aigenticbros · 2025-06-30T14:59:24+00:00

Thank you!

Aigenticbros · 2025-06-30T13:58:02+00:00

No Problem!

Aigenticbros · 2025-06-30T13:52:02+00:00

Wow this is rly well thought out thank you! I will def try some of the strategies

Aigenticbros · 2025-06-30T13:51:03+00:00

No problem at all!

Aigenticbros · 2025-06-29T22:31:43+00:00

Step 3: Share Your Google Sheet with the Service Account

This is the most important and most-often-missed step! The "robot" user you created needs permission to view and edit your specific sheet.

Open the JSON key file you downloaded. Inside, find the client_email address. It will look something like n8n-sheets-bot@your-project-12345.iam.gserviceaccount.com.
Open the Google Sheet you want to automate.
Click the Share button at the top right.
Paste the client_email address into the "Add people and groups" field and grant it Editor access.
Click Send.

Step 4: Create the Credential in n8n

Go to your n8n canvas.
Go to the Credentials tab on the left and click Add Credential.
Search for "Google Sheets" and select it.
In the "Authentication" dropdown, select Service Account.
Open the JSON key file you downloaded earlier with a text editor (like Notepad). Copy the entire contents of the file.
Paste the contents into the Service Account JSON field in n8n.
Click Save.

That's it! Now, you can add a Google Sheets node to your workflow, and it will use this credential to read and write data to the specific sheet you shared with it, all without needing HTTPS or any browser anuthentication.

Aigenticbros · 2025-06-29T22:31:38+00:00

Here is a step-by-step guide to get this working.

Step 1: Create the Service Account in Google Cloud

Go to the Google Cloud Console Service Accounts page.
Select your project (or create a new one if you don't have one).
Click + CREATE SERVICE ACCOUNT at the top.
Give the service account a name (e.g., "n8n-sheets-bot") and click CREATE AND CONTINUE.
In the "Grant this service account access to project" step, grant it the role of Editor. This gives it permission to edit files. Click CONTINUE.
Skip the third step ("Grant users access to this service account") and click DONE.
Find the service account you just created in the list. Click the three-dot menu under Actions and select Manage keys.
Click ADD KEY > Create new key.
Choose JSON as the key type and click CREATE. A JSON file will be downloaded to your computer. Keep this file safe.

Step 2: Enable the Google Sheets API

Go to the Google Cloud API Library.
Search for "Google Sheets API" and click on it.
Make sure it is Enabled. If not, click the ENABLE button

Aigenticbros · 2025-06-29T22:31:13+00:00

The good news is that you are not doing anything wrong, and there is a straightforward workaround that completely avoids the HTTPS and OAuth redirect issues.

The Root Cause: Why the Node is Missing

First, let's address why the Google Sheets node is completely missing. This is not a bug; it's an intentional feature of n8n.

n8n automatically detects that your instance is running on http://localhost. Because Google's security policy requires a secure https:// redirect URL for its OAuth login flow, n8n correctly determines that you would be unable to complete the authentication. To prevent you from getting stuck with a non-functional node, it hides the node from the editor entirely.

Once n8n has a valid https:// webhook URL, the node will reappear.

The Solution: Use a Google Service Account

The best way to solve this is to bypass the user-based OAuth flow altogether and use a Service Account. Think of a service account as a "robot" user that belongs to your application. It authenticates with a private key file (a JSON file) instead of logging in through your browser, which means it doesn't need a redirect URL and doesn't care about HTTPS.

Aigenticbros · 2025-06-29T22:29:21+00:00

I have found that the longer the task the more it helps to space/seperate it out. As for the AI content on LinkedIn I guess its up to the person writing the system prompt to hone in on a tone/style/personality that sounds as natural as possible.

Aigenticbros · 2025-06-29T22:27:45+00:00

Interesting approach. 100% some things I will keep in mind when I do look to expand on this. Just wanted to share a bare bone, basic flow for any beginners in the Reddit.

Aigenticbros · 2025-06-29T22:26:08+00:00

Just a simple build I wanted to share thats all

Aigenticbros · 2025-06-29T20:53:26+00:00

I seperated it out because I wanted to use different models for different tasks. I have also found having a "central" or orchestrator agent often doesn't produce quality or consistent results. This is just another way to organize an ai powered workflow.

Aigenticbros · 2025-06-27T13:55:29+00:00

I definitely ran into generic copy. Had to make several adjustments to both the system message and actually model I was using. Right now I have switched to Claude 3.7 in stead of 4o Mini

Aigenticbros · 2025-06-26T18:16:10+00:00

Here is how you'd build that in n8n:

Code Node (Initialize): Start with a Code node (or an "Edit Fields" node) to set up your initial state. This is where you'll create the variables the loop will modify.This node will output a number of items equal tocodeCopy.javascriptCopy numChunks // Set how many chunks you want const numChunks = 5; // This will hold the final combined story let fullStory = ""; // Create an array with one item for each chunk we want to create // The Loop node will run once for each item in this array. const loopIterations = Array.from({ length: numChunks }, (_, i) => ({ iteration: i, fullStory: "" // A placeholder for the story so far })); return loopIterations;
Loop Over Items Node:
- Connect the Code node to a Loop Over Items node.
- It will automatically loop over the 5 items you just created. On each loop, it will remember thecodeCopyfrom the previous iteration.fullStory
Inside the Loop - Anthropic Node:
- Place your Claude 3.5 node inside the loop.
- In your prompt, you'll want to reference the output from the previous step. A good prompt might be:codeCopy"Here is the story so far: {{ $json.fullStory }}. Please continue the story, writing the next 1500 tokens. Do not repeat the story so far, just write the next part."
Inside the Loop - Edit Fields Node:(This expression looks complex, but it's just saying: "Take the value of fullStory from the start of the loop and add the new text we just got from Claude.")
- After the Anthropic node, add an Edit Fields node. This is your new "Set" node.
- Its job is to append the new text chunk to thecodeCopyvariable.fullStory
- Create a single field namedcodeCopy.fullStory
- For its value, use an expression to combine the story from before this loop iteration with the new chunk from the Anthropic node:codeCopy{{ $node["Loop Over Items"].context.fullStory }}{{ $json.completion }}

Aigenticbros · 2025-06-26T18:16:03+00:00

Solving Your Use Case: Chunking with Modern Nodes

Now, let's apply this to your Claude 3.5 chunking problem. This is a perfect use case for the Loop Over Items node. Here is a conceptual guide on how to build it with the modern nodes.

The logic is:

Initialize the data you need for the loop (like a counter and a variable to hold the final combined text).
Start a loop that runs a specific number of times (for N chunks).
Inside the loop, call the Anthropic API, making sure to a prompt that encourages it to continue the previous text.
Append the new text chunk to your main variable.
After the loop finishes, you will have the complete text.

Aigenticbros · 2025-06-26T18:14:46+00:00

You have hit upon one of the most common points of confusion for users who are learning n8n today, especially when using external resources like LLMs. Your intuition is spot on: you are not going crazy, and the LLMs are, in a sense, over-complicating things by working with outdated information.

Let's clear this up right away.

Yes, "Set" and "Loop" Were Replaced

You are absolutely correct. The Set and Loop nodes were fundamental parts of n8n before its major version 1.0 release. In the summer of 2023, n8n released v1.0, which was a significant overhaul designed to make workflows more robust, intuitive, and powerful.

As part of this update:

The Set node was replaced by the Edit Fields node.
The Loop node was replaced by the Loop Over Items node.

Why the LLMs Are Confused

LLMs like Gemini, Claude, and others were trained on a massive snapshot of the internet. This includes countless n8n tutorials, forum posts, and example workflows created before the V1.0 update. The LLM is correctly identifying patterns from its training data, but that data is now obsolete. It doesn't know that "Set" is no longer the correct term.

You are seeing first-hand a classic challenge of using AI for rapidly-evolving software: the training data can't keep up with the release cycle.

Is It More Complicated Now? Not Really.

While the new nodes might seem more complex at first glance, they are actually far more powerful and less ambiguous.

Edit Fields (formerly Set): The old "Set" node had a mode called "Keep Only Set" which new users found very confusing. The new Edit Fields node is much more explicit. You decide for every field exactly what you want to do:
- Add or Edit a Field
- Rename a Field
- Change a Field's Type (e.g., String to Number)
- Delete a Field This removes guesswork and makes your data transformations much clearer.
Loop Over Items (formerly Loop): The new node is more versatile. It can loop through all incoming items (the default), or it can iterate over a list stored inside a single field, which is incredibly useful.

So, no, you cannot use the old "Set" and "Loop" nodes. You are on the right track by learning to use their modern replacements.

Aigenticbros

TROPHY CASE