My Workflow is pulling no content across

Can anyone please explain why i am not getting any content pulled across.

I am running an HTTP request, and going through chat GPT and then onto a google doc.

The nodes are running with no errors, but there is no content on the doc?

I feel as if my setup on chat gpt is where i am going wrong. Am i using the wrong Open AI node?

{
“name”: “NFL Weekly Newsletter Automation”,
“nodes”: [
{
“parameters”: {
“url”: “https://newsapi.org/v2/everything?q=NFL&from=2025-03-01&to=2025-03-07&sortBy=publishedAt&apiKey=IGNORE”,
“options”: {}
},
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.2,
“position”: [
840,
-80
],
“id”: “bc83747f-9d58-4455-a8ba-4ba6aa78d609”,
“name”: “Fetch NFL News”
},
{
“parameters”: {
“resource”: “chat”,
“prompt”: {
“messages”: [
{
“role”: “system”,
“content”: “You are a content writer for MVP Travel, a UK-based sports travel company specialising in unforgettable trips to sporting events like NFL games. Write a 600-800 word weekly round-up article summarising the biggest NFL news stories from the most recently dated articles. Use UK English spelling and grammar.\n\nStart with a catchy, SEO-friendly title that includes ‘NFL News Round-up’ and the date range (e.g., ‘NFL News Round-up: [Start Date] to [End Date]’). Add a friendly intro aimed at UK NFL fans, explaining why staying up to date is key for anyone thinking of travelling to the US or attending the London Games.\n\nCover at least 5 major stories, each with a clear subheading (H2), a 3-5 sentence summary, and an outbound link to a trusted source (like nfl.com, espn.com, or Yahooist Teil der Yahoo Markenfamilie). Format the links as clickable hyperlinks using Markdown syntax (e.g., [Read more](https://example.com)).\n\nWhere relevant, explain why each story matters to UK fans – especially those thinking of booking an NFL trip. For example, highlight how a player’s performance might impact the London Games or how a rule change could affect the fan experience.\n\nUse natural, conversational language – no jargon overload. Do not use emojis at any point in the article. Tie the article up with a friendly closing paragraph, encouraging readers to check out MVP Travel’s NFL trips and packages. Include a strong call-to-action (CTA) with links to specific packages like Super Bowl trips or London Games experiences.\n\nOptimise the content for SEO by naturally including terms like NFL news, UK NFL fans, travel to NFL games, NFL London Games, Super Bowl trips, and UK sports travel.”
},
{
“role”: “user”,
“content”: “News Articles:\n{{$node["Fetch NFL News"].json.articles.slice(0, 7)}}\n\nGenerate the newsletter based on the above articles.”
}
]
},
“options”: {},
“requestOptions”: {}
},
“type”: “n8n-nodes-base.openAi”,
“typeVersion”: 1,
“position”: [
1100,
-80
],
“id”: “3b25e8bd-2597-4315-99ea-80125e36d91a”,
“name”: “OpenAI”,
“credentials”: {
“openAiApi”: {
“id”: “dlzuJyNenSEvzglV”,
“name”: “OpenAi account”
}
}
},
{
“parameters”: {
“driveId”: “=myDrive”,
“folderId”: “=1kh1Nq3QrFPUeaQPH3Glf92d90BaWAEIJ”,
“title”: “Weekly NFL News - {{$now.format(‘YYYY-MM-DD’)}}”,
“content”: “={{$node["OpenAI"].json.choices[0].message.content}}”,
“operation”: “create”
},
“type”: “n8n-nodes-base.googleDocs”,
“typeVersion”: 2,
“position”: [
1380,
-80
],
“id”: “093e5742-3139-41b5-a97a-a708a420388c”,
“name”: “Google Docs”,
“credentials”: {
“googleDocsOAuth2Api”: {
“id”: “IGNORE”,
“name”: “Google Docs account 2”
}
}
},
{
“parameters”: {},
“type”: “n8n-nodes-base.manualTrigger”,
“typeVersion”: 1,
“position”: [
600,
-80
],
“id”: “IGNORE”,
“name”: “When clicking ‘Test workflow’”
}
],
“connections”: {
“Fetch NFL News”: {
“main”: [
[
{
“node”: “OpenAI”,
“type”: “main”,
“index”: 0
}
]
]
},
“OpenAI”: {
“main”: [
[
{
“node”: “Google Docs”,
“type”: “main”,
“index”: 0
}
]
]
},
“When clicking ‘Test workflow’”: {
“main”: [
[
{
“node”: “Fetch NFL News”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“active”: false,
“settings”: {
“executionOrder”: “v1”
},
“id”: “IGNORE”,
“tags”:
}

Hey @Ryan_Roodt can you try pasting your code into these code tags. I cant import it this way.

type or paste code here
1 Like

{
“name”: “My workflow”,
“nodes”: [
{
“parameters”: {},
“type”: “n8n-nodes-base.manualTrigger”,
“typeVersion”: 1,
“position”: [
1420,
-60
],
“id”: “931d1e5b-a7d3-4296-8f86-459084bc4638”,
“name”: “When clicking ‘Test workflow’”
},
{
“parameters”: {
“resource”: “chat”,
“prompt”: {
“messages”: [
{
“role”: “system”,
“content”: “You are a content writer for MVP Travel, a UK-based sports travel company specialising in unforgettable trips to sporting events like NFL games. Write a 600-800 word weekly round-up article summarising the biggest NFL news stories from the most recently dated articles. Use UK English spelling and grammar.\n\nStart with a catchy, SEO-friendly title that includes ‘NFL News Round-up’ and the date range (e.g., ‘NFL News Round-up: [Start Date] to [End Date]’). Add a friendly intro aimed at UK NFL fans, explaining why staying up to date is key for anyone thinking of travelling to the US or attending the London Games.\n\nCover at least 5 major stories, each with a clear subheading (H2), a 3-5 sentence summary, and an outbound link to a trusted source (like nfl.com, espn.com, or Yahooist Teil der Yahoo Markenfamilie). Format the links as clickable hyperlinks using Markdown syntax (e.g., [Read more](https://example.com)).\n\nWhere relevant, explain why each story matters to UK fans – especially those thinking of booking an NFL trip. For example, highlight how a player’s performance might impact the London Games or how a rule change could affect the fan experience.\n\nUse natural, conversational language – no jargon overload. Do not use emojis at any point in the article. Tie the article up with a friendly closing paragraph, encouraging readers to check out MVP Travel’s NFL trips and packages. Include a strong call-to-action (CTA) with links to specific packages like Super Bowl trips or London Games experiences.\n\nOptimise the content for SEO by naturally including terms like NFL news, UK NFL fans, travel to NFL games, NFL London Games, Super Bowl trips, and UK sports travel.”
},
{
“content”: “News Articles:\n{{$node["Fetch NFL News"].json.articles.slice(0, 7)}}\n\nGenerate the newsletter based on the above articles.”
}
]
},
“options”: {},
“requestOptions”: {}
},
“type”: “n8n-nodes-base.openAi”,
“typeVersion”: 1,
“position”: [
1980,
-60
],
“id”: “d38ebba4-1072-4f46-9c74-4d7c4153773d”,
“name”: “OpenAI”,
“alwaysOutputData”: true,
“credentials”: {
“openAiApi”: {
“id”: “dlzuJyNenSEvzglV”,
“name”: “OpenAi account”
}
}
},
{
“parameters”: {
“driveId”: “=myDrive”,
“folderId”: “=1kh1Nq3QrFPUeaQPH3Glf92d90BaWAEIJ”,
“title”: “Weekly NFL News - {{$now.format(‘YYYY-MM-DD’)}}”
},
“type”: “n8n-nodes-base.googleDocs”,
“typeVersion”: 2,
“position”: [
2260,
-60
],
“id”: “bc2e4d16-5b65-44ec-9dd9-7ba023ee3e9e”,
“name”: “Google Docs”,
“credentials”: {
“googleDocsOAuth2Api”: {
“id”: “FrZgm95avlahgbTX”,
“name”: “Google Docs account 2”
}
}
},
{
“parameters”: {
“url”: “https://newsapi.org/v2/everything?q=NFL&from=2025-03-01&to=2025-03-07&sortBy=publishedAt&apiKey=763d9d30b078427fb49e07570924f93b”,
“options”: {}
},
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.2,
“position”: [
1720,
-60
],
“id”: “917b3ffa-86b1-476c-aa35-5c12935301d2”,
“name”: “Fetch NFL News1”
}
],
“pinData”: {},
“connections”: {
“When clicking ‘Test workflow’”: {
“main”: [
[
{
“node”: “Fetch NFL News1”,
“type”: “main”,
“index”: 0
}
]
]
},
“OpenAI”: {
“main”: [
[
{
“node”: “Google Docs”,
“type”: “main”,
“index”: 0
}
]
]
},
“Fetch NFL News1”: {
“main”: [
[
{
“node”: “OpenAI”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“active”: false,
“settings”: {
“executionOrder”: “v1”
},
“versionId”: “1ed1a10e-58b6-457c-9ef9-96db0694ce83”,
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “b2c10e6627b4579d9d8e6499bce4229d68e7d96a9fe3ea9404d2670220372510”
},
“id”: “cxz7a7X3R0AWEv8X”,
“tags”:
}

Hey @Ryan_Roodt,

Please place your code inside a code block.

Like this

Hey @Ryan_Roodt few things I noticed:

  • You shared your API key for the news API, you’ll probably want to invalidate that one and change it.

  • You could use header auth for that to share the workflow in a more secure way HTTP Request credentials | n8n Docs

  • At least in the shared piece of the workflow you didn’t turn on expressions (see attached) so the model actually doesn’t receive the content.


    vs

  • The data from the API seems to be cut off (content of the article) that something you’ll probably should look at.

  • I would strongly recommend using a stronger model than GPT-3.5

  • If all that works you should actually see the output from OpenAI - with that validated you should be able to also write the content to google sheets (however you will have to also update that document you are creating in the last step

Thanks for your help @jksr - I got rid of the API key (sorry about that). I made the changes you suggest and they have appeared to work.


but the google doc is populating with no content and i cant work out why.

I do apologies, I am new to this and trying to figure as much out as a i can on my own.

your help is appreciated

Don’t worry! Happy to help :slight_smile: Did you add that additional Google Docs update node? Because create will only put a blank document and give you the ID and with update you’d actually write to that document.

I updated the expression on the google doc:

but still no content coming through : I feel like i am getting one step closer each time.

You need a second node - you are using a wrong field for the content.
You take the ID:


And use it for the update node :+1:

something like this

1 Like

Still not content :frowning:

Can you compare with yours?
For me it works

It worked! Thank you so much!
If i set up a schedule node to run once a week, will it create a new article every time or just overide the existing on?

It should create a new document each time with the date in the title (like you set it up)

Thanks for your help @jksr - It is appreciated

You’re welcome ! Congrats on completing the workflow :+1: Would appreciate it if you could mark my answer as the solution.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.