Create ready to publish Q and A content for every service your team supports. It pulls items from Google Sheets, fills answers with AI, and saves clean JSON files in Google Drive. Ideal for marketing and documentation teams that manage many integrations at once.

Inside the flow, a manual start or an internal trigger kicks off batch runs per sheet type. The workflow reads services from selected Google Sheets tabs, uses a Switch to pick the right template for native, credential only, non native, or category content, and sends any missing text to an AI model for completion. Questions are split and merged, then formatted into a single JSON object. Files are named with the service and date, saved to a chosen Drive folder, and the status is updated back in the sheet. Optional nodes can push the JSON to your CMS using WordPress, Webflow, Strapi, or a generic HTTP call.

Setup is simple once accounts and credentials are ready. Point the Google Sheets nodes to your document and confirm the sheet names. Set or pass the Google Drive folder where files should go. Expect faster output, consistent structure, and clear tracking in your sheet. Use it for integration pages, help center Q and A, and SEO collections that need a steady, reliable format.

• Manual and internal triggers to start single runs or nested jobs
• Reads services from Google Sheets tabs and filters by status
• Switch logic selects native, credential only, non native, or category templates
• AI model completes missing answers for natural and clear content
• Batch and list handling to process many questions and services safely
• Builds a single JSON file per service and saves it to Google Drive with date based names
• Updates the sheet row to done so teams can see progress in real time
• Optional publish steps for WordPress, Webflow, or Strapi using built in nodes

• Reduce manual drafting from 4 hours to 15 minutes per service
• Streamline content production by about 70 percent using batch runs from a single sheet
• Improve consistency with reusable Q and A templates across all services
• Unify Google Sheets, AI, Google Drive, and your CMS in one flow
• Track progress with automatic status updates on each processed row

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Sheets, Google Drive, OpenAI, WordPress, Webflow and Strapi. See the Tools Required section above for links to create accounts with these services.
3. Connect Google Sheets in n8n Cloud: double click the Google Sheets nodes, open the Credential to connect with dropdown, click Create new credential, then follow the on screen steps to authorize your Google account.
4. Connect Google Drive: double click the Google Drive node, create a new credential, and complete Google authorization. Copy the target Drive folder ID from Google Drive if you prefer to set it directly.
5. Add your OpenAI key: double click the OpenAI or AI nodes, create a new OpenAI credential, and paste the API key from your OpenAI account API page.
6. WordPress connection: double click the WordPress node, create a new credential, then follow the on screen steps to authenticate. Use your site URL and account method supported by your WordPress host.
7. Webflow connection: double click the Webflow node, create a new credential, and authorize with your Webflow account so the node can create or update items.
8. Strapi connection: double click the Strapi node, create a new credential, and provide your Strapi base URL and API token if needed.
9. Set your Google Sheet: in the Google Sheets Get Services node, choose your document and confirm each sheet name matches the list in the Define Sheets node. Make sure the status column exists.
10. Choose the Drive output folder: either keep the expression that reads outdir from the Execute Workflow Trigger or set the folderId directly in the Google Drive Create From Text node.
11. Enable optional CMS posting: unpause the Strapi, WordPress, or Webflow nodes and map fields to the JSON produced earlier. Run a test on a draft collection first.
12. Test the run: click Execute on the manual trigger, confirm a JSON file appears in the Drive folder, and check that the sheet status changed to done. If a row does not update, verify the row number and status mapping in the Update Row Status node.