Turn your website analytics into a clear weekly SEO report without manual work. It pulls data from your Umami server, asks an AI to explain what changed, and stores the results in Baserow for tracking over time. This is helpful for content teams, agencies, and site owners who want fast, readable insights.

The run can be scheduled weekly and you can also test it by hand. It starts by fetching summary stats from Umami for the last seven days. A code step formats the numbers so the AI can read them well, and the first AI call returns a plain language summary. Next, it requests page level stats for this week and last week, compares the views, and sends that result to the AI for deeper findings and top pages. Finally, it writes the date, the summary, the top pages, and the blog or site name into Baserow.

You need access to your Umami API, an OpenRouter API key, and a Baserow table with the right fields. Expect to shrink weekly reporting time from hours to minutes and keep a clean history for content planning. This setup fits blogs, media sites, and agencies that want regular SEO insights with less effort.

• Weekly schedule trigger plus a manual test trigger for safe runs
• Pulls seven day summary metrics from your Umami server
• Parses and formats analytics with code steps for clean AI input
• Sends stats to an AI via OpenRouter to generate readable summaries
• Fetches page level data for this week and last for direct comparison
• Creates a second AI analysis focused on top pages and changes
• Saves the date, summary, top pages, and site name into Baserow
• Uses header based credentials for secure API access

• Reduce manual weekly reporting from 2 hours to 10 minutes
• Automate 80% of repetitive analytics review work
• Improve data accuracy by removing copy and paste errors
• Connect Umami, AI, and Baserow into one smooth flow
• Create a consistent history of SEO insights for trend tracking

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 Umami, OpenRouter and Baserow. See the Tools Required section above for links to create accounts with these services.
3. In your Umami dashboard, find your website ID under Settings then Edit. Note your Umami base URL and ensure API access is enabled. Create or locate your API token if your server requires one.
4. In n8n, open Credentials and create a new HTTP Header Auth credential for Umami. Add key Authorization with value Bearer your token. Save the credential.
5. Create an OpenRouter account and generate an API key. In n8n Credentials, create another HTTP Header Auth credential. Set Authorization to Bearer your OpenRouter key. Save it.
6. In Baserow, create a database and a table with these fields: Date date, Summary long text, Top pages long text, Blog name long text. Generate a personal API token in Baserow.
7. In n8n Credentials, create a Baserow credential using your API token. Select it in the Save data to Baserow node and choose the correct table and fields.
8. Open the Get view stats from Umami node and update the URL with your Umami domain and website ID. Repeat for the other Umami request nodes so they point to your server and site.
9. Check the two AI request nodes. Confirm the URL is https://openrouter.ai/api/v1/chat/completions and that the model and body fields are set. Select your OpenRouter credential in both nodes.
10. Run the workflow with the manual trigger. Verify you get data from Umami, see AI text outputs, and confirm a new row appears in your Baserow table.
11. Open the Schedule Trigger and choose your weekly day and time. Enable the workflow to start automatic runs.
12. Troubleshooting: 401 errors mean the token or header is wrong. 404 errors often mean a bad Umami URL or website ID. 429 from AI means rate limits, so retry later or slow the schedule. If Baserow rejects data, check field names and types.