Tutorials
Tutorial: recurring operational report
Build a supported weekly workflow that reads connected-service data and sends or stores a summary.
Operations teamsAutomation buildersAdvancedAvailable
What this guide covers
- A Scheduled trigger can start a weekly workflow; App Action can read supported service data; AI Response can summarize supplied data; Slack, Gmail, Notion, Sheets, or Drive can receive supported output.
- Prerequisites: Connected source and destination apps, known data shape, weekly Scheduled trigger, and reviewed AI summarization instructions if AI is used.
- Result: The next controlled run reads the intended source and writes or sends one report to the selected destination.
- Limit: This tutorial is partly compositional: Yanola does not provide a dedicated Report node or arbitrary internal Analytics data source.
What this is and when to use it
A Scheduled trigger can start a weekly workflow; App Action can read supported service data; AI Response can summarize supplied data; Slack, Gmail, Notion, Sheets, or Drive can receive supported output.
| Use it when | Expected outcome |
|---|---|
The report data exists in a supported connected service or can be safely retrieved by a Function/HTTP Request. | The next controlled run reads the intended source and writes or sends one report to the selected destination. |
Before you begin
- Connected source and destination apps, known data shape, weekly Scheduled trigger, and reviewed AI summarization instructions if AI is used.
Prerequisites
Connected source and destination apps, known data shape, weekly Scheduled trigger, and reviewed AI summarization instructions if AI is used.
Complete the task
- Create a weekly Scheduled workflow and select timezone.
- Read data with a supported App Action, HTTP Request, or deployed Function.
- Validate empty/error results with Condition.
- Optionally summarize the supplied data with AI Response.
- Store or send output using a supported app action.
- Test with a bounded dataset and activate.
Confirm it worked
- The next controlled run reads the intended source and writes or sends one report to the selected destination.
Common problems
| Symptom | What to check |
|---|---|
A generic Yanola activity report is expected | The workflow must use an implemented source; there is no generic analytics-as-node action. |
Destination action lacks formatting | Match the exact fields supported by that integration action. |
Current limitations
This tutorial is partly compositional: Yanola does not provide a dedicated Report node or arbitrary internal Analytics data source.
Product boundary
This tutorial is partly compositional: Yanola does not provide a dedicated Report node or arbitrary internal Analytics data source.
Where to go next
Related documentation
Connected services overviewConnect supported external accounts and use their cataloged actions from the workflow App Action node.Run a workflow on a scheduleConfigure a Scheduled trigger for once, daily, weekly, or monthly workflow starts.AI features, privacy, and human reviewUse Yanola Agent, AI Response, Classifier, Extract Info, Detect Mood, and AI-assisted Function drafts responsibly.