Summary  
Orchestrating API interactions to create documents from generated content and update the same spreadsheet rows with text and links.

General domain of usage  
Content publishing automation

Your AI agents already generate content. Now you turn the long-form outputs into documents.

**LinkedIn post → Google Doc**
After the LinkedIn agent, add **Google Docs → Create a Document**.
Use a title like `LinkedIn post – {{RSS title}}`, map the agent’s text as the content, and select your prepared Drive folder.

**Blog post → Google Doc**
After the blog agent, add another **Create a Document** module.
Use `Blog post – {{RSS title}}` as the title and map the blog article text.
Each RSS item now creates two Docs.

### Update the Same Sheet Row With All Outputs

You already created a row when the RSS item entered the scenario. Now you fill that same row.



For each qualifying RSS item, your scenario now:

* Creates one row in Google Sheets
* Generates a tweet, a LinkedIn post, and a blog post
* Stores long-form content as Google Docs
* Updates the same row with text and document links

Everything stays organized, traceable, and easy to review.

Why do you use Update a Row instead of Add a Row when saving AI outputs to Google Sheets?

Storing AI Content in Docs and Sheets

Update the Same Sheet Row With All Outputs

Storing AI Content in Docs and Sheets

Update the Same Sheet Row With All Outputs