Get weekly SEO insights without manual work. The workflow collects website analytics from Umami, asks an AI to explain what happened, and saves the results in Baserow for easy tracking. It is ideal for content and marketing teams that want fast, clear reports.

A schedule runs the job each week, and you can also run it by hand for testing. It pulls summary stats for the last seven days, then fetches page data for this week and last week to compare performance. Code steps clean and format the data so the AI can read it well. Two AI calls produce a plain language summary and a list of top pages. Finally, it writes Date, Summary, Top pages, and Blog name into a Baserow table so you can review trends over time.

You will need your Umami base URL and website ID, an API key for OpenRouter, and a Baserow API token. Create the Baserow table with the fields listed and map them in the node. Run a manual test to confirm data, then let the weekly schedule handle the rest. Expect to cut reporting time from hours to minutes and keep a clean history of SEO notes your team can use.

• Weekly schedule trigger plus a manual trigger for on demand runs
• Pulls last seven days of summary metrics from Umami
• Gets page stats for this week and last week for side by side comparison
• Code steps format URLs and counts so the AI can read the input clearly
• Sends two AI requests to create a summary and highlight top pages
• Saves results to Baserow fields: Date, Summary, Top pages, Blog name
• Header based authentication applied to each external request
• Adjustable date range and model settings for flexible reporting

• Reduce manual reporting from 2 hours to 5 minutes each week
• Automate 90% of SEO summary writing with clear AI notes
• Improve accuracy by removing copy and paste errors
• Connect Umami, OpenRouter and Baserow in one flow
• Keep a weekly history to track trends and content wins
• Scale analysis to hundreds of pages without extra effort

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, note your base URL and website ID. You can find the ID in Settings under the site you are tracking.
4. Create or obtain an API token for Umami if required. In the n8n credentials manager, create a new HTTP Header Auth credential named Umami Auth. Set the header name to Authorization and the value to Bearer YOUR_UMAMI_TOKEN.
5. Open each Umami HTTP Request node in n8n and select the Umami Auth credential. Update the URL to use your Umami base URL and website ID in all Umami request nodes.
6. In your OpenRouter account, create an API key. In the n8n credentials manager, create a new HTTP Header Auth credential named OpenRouter Auth with Authorization as the header name and Bearer YOUR_OPENROUTER_KEY as the value.
7. Open both Send data to A.I. nodes and choose the OpenRouter Auth credential. Review the model and prompt text and adjust if needed for your brand voice.
8. In Baserow, create a database table with columns: Date (date), Summary (long text), Top pages (long text), Blog name (long text). Generate a Baserow API token in your account settings.
9. In the n8n credentials manager, create a Baserow API credential with your token. Open the Save data to Baserow node and select this credential. Choose the correct database and table, and map the fields from the AI outputs.
10. Click Execute Workflow using the manual trigger. Confirm that Umami nodes return data, AI nodes return text, and a new row appears in Baserow with the expected fields.
11. Enable the Schedule Trigger so it runs weekly. Confirm the timezone and day align with your reporting needs.
12. Troubleshoot common issues: 401 errors mean the token or header is wrong, 404 means the website ID or base URL is incorrect, empty AI output suggests a prompt or rate limit issue, and Baserow errors usually come from field type mismatches.