See llms.txt for all machine-readable content.
This workflow runs weekly to read KPI rows from Google Sheets, merge them with benchmark KPI data from an HTTP API, calculate week-over-week trends, generate an executive summary with Google Gemini, then send the result via Gmail and Slack and log it back to Google Sheets.
This workflow is easy to adapt without changing the full structure.
Adjust the run day and time to match your reporting cycle.
Change the report title, date label format, or add extra fields such as business unit or reporting owner.
Switch the spreadsheet, use another tab, or filter source rows before normalization.
Replace the placeholder API with a live benchmark source such as an analytics API, CRM endpoint, ad platform API, or internal reporting service.
Add more fields from your spreadsheet, such as region, campaign, product line, or owner.
Change how external metrics are mapped so they match the same schema as your main KPI data.
Extend the logic to calculate rolling averages, status colors, weighted scoring, or alert thresholds.
Refine the prompt for a different writing tone, longer narrative summaries, or department specific outputs.
Switch model versions or tune generation settings if your summaries need more detail or tighter control.
Create separate message structures for leadership, sales, marketing, or clients.
Send to multiple recipients, use a group mailbox, or route through a different email provider.
Post into multiple channels, threads, or team specific destinations.
Add more columns such as workflow status, report owner, channel count, or execution ID.
You can extend this workflow with additional features such as:
This workflow supports several practical business scenarios, including these common examples:
Pull sessions, leads, and email metrics from Google Sheets, summarize movement, and post the result to leadership each Monday.
Collect weekly client metrics, draft a readable update with AI, and deliver the summary through email and Slack while saving a history log.
Track weekly process or service KPIs from a spreadsheet, calculate movement against target, and generate a management ready summary.
Create a short investor or founder style weekly snapshot from operational metrics without manually preparing a report every week.
Keep the placeholder benchmark branch during development to test merge logic, prompt quality, and final message formatting before switching to real external data.
There can be many more use cases for this workflow depending on your reporting structure, KPI sources, and communication channels.
| Issue | Possible Cause | Solution |
|---|---|---|
| Workflow does not start on schedule | Workflow is inactive or schedule settings are incomplete | Activate the workflow and recheck the Weekly KPI Schedule Trigger configuration |
| Google Sheets data is empty | Wrong spreadsheet, wrong tab, or missing access | Reconnect credentials and confirm the correct document and sheet are selected |
| KPI calculations look wrong | Source values are stored as text or fields do not match expected names | Review the source sheet columns and confirm Number conversion in the normalization step |
| Benchmark data looks irrelevant | Placeholder API is still active | Replace the Fetch Benchmark KPI Data node with your real benchmark source or remove the branch |
| Gemini summary is too generic | Prompt is too broad or test data is weak | Improve the Build Executive Summary Prompt node and use more realistic KPI inputs |
| Gmail node fails | Gmail credential expired or sending account lacks permission | Reconnect Gmail and test sending from the configured mailbox |
| Slack message is not posted | Wrong channel selected or Slack app lacks posting rights | Reconnect Slack, select the correct channel, and verify app permissions |
| Log row is not added to Google Sheets | Wrong log sheet or incorrect column mapping | Review the append node, log sheet destination, and mapped column names |
| Merge output is incomplete | One branch is not returning records | Test both normalization branches separately and confirm each one outputs items before the merge |
| AI output formatting is messy | The formatter node is not extracting the expected Gemini field | Review the Format Email and Slack Message node and confirm which response property contains the summary text |
This workflow can be a solid foundation for a reliable reporting system and it can be tailored further based on your exact business process. If you need help setting up this workflow, replacing the placeholder benchmark API with a production data source, improving the Gemini prompt, adding approval flows or extending the workflow with more channels and logic, WeblineIndia can help.
WeblineIndia can assist with: