Google Docs + Telegram: client-ready ASO reports
You know the drill. Someone drops a Google Play link in a chat, and suddenly you’re juggling tabs for reviews, ratings, competitors, downloads, and “quick insights” that turn into an hour of copy-paste.
ASO consultants feel it during audit weeks. A growth marketer gets hit when leadership wants “a clean report by EOD.” And agency leads? Same pain, just multiplied by clients. This ASO report automation turns a single Play Store URL into a client-ready Google Doc, then sends the share link to Telegram.
Below you’ll see how the workflow runs, what results you can expect, and what you’ll need to set it up without getting lost in technical weeds.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Docs + Telegram: client-ready ASO reports
flowchart LR
subgraph sg0["Form Entry Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>Form Entry Trigger"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>External App Data Request"]
n2@{ icon: "mdi:robot", form: "rounded", label: "Generate ASO Narrative", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Format App Intelligence"]
n4@{ icon: "mdi:brain", form: "rounded", label: "OpenRouter LLM Connector", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Create Report Document", pos: "b", h: 48 }
n6@{ icon: "mdi:cog", form: "rounded", label: "Insert Report Content", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Notify via Telegram"]
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract Package Identifier"]
n3 --> n2
n8 --> n1
n1 --> n3
n2 --> n5
n5 --> n6
n6 --> n7
n0 --> n8
n4 -.-> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n2 ai
class n4 aiModel
class n1 api
class n3,n8 code
classDef customIcon fill:none,stroke:none
class n0,n1,n3,n7,n8 customIcon
The Problem: ASO reporting takes too long (and still looks inconsistent)
ASO research is easy to start and annoying to finish. You pull app details from one place, competitor notes from another, then skim reviews to find patterns you’ve seen a hundred times. After that comes the worst part: turning scattered notes into something you can actually send to a client or stakeholder without apologizing for formatting. And every time you do it manually, you introduce tiny errors. The wrong app version. An outdated rating. A competitor list you forgot to refresh. It’s not one big mistake. It’s a slow drip of friction that makes you dread the next request.
It adds up fast. Here’s where it usually breaks down.
- Finding and copying the right app data can eat about an hour per report, especially when you’re switching between tools and spreadsheets.
- Report structure changes from one analyst to the next, which means clients get inconsistent deliverables even when the analysis is good.
- Pulling reviews and summarizing themes is repetitive, so it’s easy to skip steps when you’re under time pressure.
- You still have to message someone “the doc is ready,” and that tiny task gets forgotten more than anyone wants to admit.
The Solution: Generate an ASO report in Google Docs and deliver it via Telegram
This workflow starts with a simple form submission (powered by a Jotform-style form trigger in n8n). You paste in a Google Play Store URL, and the automation extracts the package identifier so it can reliably pull the right app’s data. Next, an HTTP request fetches app intelligence data (SensorTower or a similar app intelligence API), then the workflow parses and formats that information into clean, usable fields. From there, an AI agent uses an OpenRouter-connected chat model to write a structured ASO narrative that reads like a professional report, not raw bullet points. Finally, n8n creates a Google Doc, inserts the formatted report content, and sends you a Telegram message with the share link so you can review or forward it immediately.
The flow begins when a Play Store link is submitted via the form. Data retrieval and parsing happen automatically in the middle, so the AI gets clean inputs instead of messy blobs. Then Google Docs becomes the final “deliverable,” and Telegram becomes the notification layer that keeps your day moving.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you handle 5 app audits in a week. Manually, you might spend about 30 minutes pulling basics and screenshots, another 30 minutes on competitors and market notes, and about an hour turning it into a clean report. That’s roughly 2 hours per app, or about 10 hours weekly. With this workflow, submitting the URL takes a minute, the AI and doc creation run in the background for maybe 10–20 minutes, and your Telegram message arrives with the share link. You still review and tweak, but the “blank page” work is gone.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Jotform (or n8n form trigger) to collect Play Store links
- Google Docs to generate shareable client-ready reports
- Telegram to receive the finished document link
- SensorTower API key (get it from your SensorTower account settings)
- OpenRouter API key (get it from the OpenRouter dashboard)
Skill level: Intermediate. You’ll connect accounts, paste API keys, and test with a real Play Store URL.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Form submission triggers everything. You submit a Google Play URL through the workflow’s form trigger, which keeps intake simple and consistent.
The workflow extracts the package ID and pulls data. A code step grabs the package identifier from the URL, then the HTTP request fetches app intelligence data from your provider so you’re not scraping or guessing.
AI writes the narrative using structured inputs. The workflow formats the raw response into clean fields and sends them through an AI agent connected to an OpenRouter chat model, producing sections like App Overview, Reviews themes, Competitor Analysis, Market Insights, and Recommendations.
Google Docs becomes the deliverable and Telegram becomes the alert. n8n creates the document, inserts the report content, and messages you in Telegram with the document link so you can share it right away.
You can easily modify the report sections to match your template or client type based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Form Trigger
Set up the workflow to start when a user submits the ASO report form.
- Add and open Form Entry Trigger.
- Set Form Title to
ASO Report. - In Form Fields, add a required field with Field Label set to
Play Store URL. - Connect Form Entry Trigger to Extract Package Identifier to begin processing submissions.
Step 2: Connect App Data Retrieval
Extract the package name and request app intelligence data from the external API.
- Open Extract Package Identifier and keep the provided JavaScript Code to parse the
idparameter from the submitted URL. - Open External App Data Request and set URL to
=https://app.sensortower.com/api/android/apps/{{ $json.packageName }}?country=US. - Confirm the connection order: Extract Package Identifier → External App Data Request → Format App Intelligence.
null and the API request will fail. Validate input URLs in the form.Step 3: Set Up Processing and AI Narrative Generation
Format app data and generate the ASO narrative using the LLM connector.
- Open Format App Intelligence and keep the provided JavaScript Code to produce
appInfo,reviewsText,competitorsText, andmarket. - Open Generate ASO Narrative and set Prompt Type to
define. - Set Text to the full prompt expression, starting with
=Create an ASO Report based on the following data.and including the input mappings like{{ $json.appInfo.name }}and{{ $json.market.revenue }}. - In Generate ASO Narrative, keep the message instruction starting with
=You are an ASO (App Store Optimization) Analyst.to ensure plain-text output. - Open OpenRouter LLM Connector and set Model to
google/gemini-2.0-flash-exp:free.
Step 4: Configure Document Creation and Notifications
Create a Google Doc report, insert the narrative, and notify via Telegram.
- Open Create Report Document and set Title to
={{ $('Format App Intelligence').item.json.appInfo.name }}. - Set Folder ID to your target Google Drive folder, for example
[YOUR_ID]. - Open Insert Report Content and set Operation to
updateand Document URL to={{ $json.id }}. - In Insert Report Content → Actions, set Text to
={{ $('Generate ASO Narrative').item.json.text }}with Action set toinsert. - Open Notify via Telegram and set Chat ID to
[YOUR_ID]. - Set Text to
=📄 New document for app analysis: {{ $('Format App Intelligence').item.json.appInfo.name }} 🔗 Document link: https://docs.google.com/document/d/{{ $json.documentId }}/edit?tab=t.0.
Step 5: Test and Activate Your Workflow
Run a manual test to verify the end-to-end flow before activating.
- Click Execute Workflow and submit the Form Entry Trigger with a valid Play Store URL.
- Confirm External App Data Request returns app data and Format App Intelligence outputs structured fields like
appInfoandreviewsText. - Verify Generate ASO Narrative returns a plain-text report in
text. - Check that Create Report Document creates a new Google Doc and Insert Report Content inserts the narrative.
- Ensure Notify via Telegram sends a message with the document link.
- When successful, toggle the workflow to Active for production use.
Common Gotchas
- Google Docs credentials can expire or need specific permissions. If things break, check the Google connection in n8n’s Credentials area first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30–60 minutes once you have your API keys.
No. You will mostly connect accounts and paste API keys. The workflow’s code steps are already built; you’re just configuring.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in app intelligence API costs (SensorTower varies by plan) and OpenRouter model usage, which is usually a few cents per report.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you probably should. You can adjust the sections in the “Generate ASO Narrative” AI node prompt, then update how the document is assembled in “Insert Report Content.” Common tweaks include adding your brand voice guidelines, changing the headings to match your template, and injecting a “Next steps” section tailored to your service package.
Usually it’s expired or revoked OAuth access. Reconnect Google Docs in n8n Credentials, then confirm the account has permission to create and edit docs in the target Google Drive. If it fails only on insert, check that the document ID coming from “Create Report Document” is actually being passed into “Insert Report Content.”
Plenty for normal agency volume. On n8n Cloud, your limit depends on plan executions per month; on self-hosted n8n there’s no hard cap, it’s mostly your server and API rate limits. In practice, most teams run a handful to a few dozen reports a week without any special tuning. If you start generating hundreds, you’ll want batching and stricter rate limiting on the HTTP request.
Often, yes. This workflow has several moving parts (data fetching, parsing, AI writing, doc creation, and message delivery), and n8n handles that kind of multi-step logic cleanly without turning your bill into a surprise. Self-hosting is also a real advantage if you run lots of executions. Zapier and Make can still be fine for simple “send a message when X happens” flows, but ASO reporting tends to get complex quickly. If you’re unsure, map your volume and how much customization you need, then choose based on that. Talk to an automation expert if you’re not sure which fits.
Once this is set up, a Play Store link becomes a shareable ASO report without the busywork. Honestly, the best part is the Telegram ping: you stop babysitting the process and just review the finished doc.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
