Skip to main content
To learn how workflow creation works, this guide walks through a simple “Daily Digest” example. Follow the steps to understand adding nodes, configuring tools, and scheduling runs.

Overview

This guide shows how to build a Daily Digest workflow: gather Gmail emails, Google Calendar events, relevant news, then generate and send a structured HTML summary. You will use Input, Tool, Output, and Trigger nodes.

Final Flow (High-Level)

Trigger (Daily 08:00) → Input (email) → Tool: Gmail → Tool: Calendar → Tool: Web Search → Tool: Send Email → Output

Step-by-Step

Step-by-Step

1

Add Input Node

Drag Input node. Add field:
  • Name: email (Text, single line).
    Why: Establish a reusable variable (INPUT.email) so every downstream node can personalize output and send the digest to the right recipient.
2

Fetch Emails (Tool Node)

Add Tool node “Fetch emails”.
Integration: Gmail.
Tool: GMAIL_LIST_EMAILS.
Message example: “Fetch today’s and yesterday’s emails. Categorize: 1) Urgent attention, 2) Tasks, 3) Informational.”
Why: Collect raw inbox context and pre‑categorize so the digest highlights actions and priorities instead of dumping every email.
The AI infers search parameters; output accessible as FETCH_EMAILS.tool_result.
3

Fetch Calendar (Tool Node)

Add Tool node “Calendar”.
Integration: Google Calendar.
Tool: GOOGLE_CALENDAR_LIST_CALENDAR_EVENTS.
Message example: “Retrieve all events from now until end of day. Include title, start, end, location, description in chronological order.”
Why: Surface upcoming time commitments so the digest merges schedule + tasks for daily planning.
Output → CALENDAR.tool_result.
4

Web Search (Tool Node)

Add Tool node “Web search”.
Integration: App Default Tools.
Tool: Web Search.
Message example: “Search trending news based on my profession; return top 5 most relevant.”
Why: Add external context (industry/news) to enhance situational awareness in the same daily snapshot.
Output → WEB_SEARCH.tool_result.
5

Send Email (Tool Node)

Add Tool node “Send email” and connect outputs of the three previous Tool nodes.
Integration: App Default Tools.
Tool: Send Email Notification.
Set fields:
  • to: INPUT.email
  • subject: “Dume AI Daily Digest”
  • content (Message prompt): “Generate a polished HTML daily digest containing: 1 Today’s upcoming calendar events (CALENDAR.tool_result). 2 Summary of categorized emails (FETCH_EMAILS.tool_result). 3 Top 5 relevant news (WEB_SEARCH.tool_result). Use sections, headings, readable tables, and brief action items.”
    Why: Consolidates disparate data sources into one actionable, formatted deliverable sent automatically.
6

Add Output Node

Connect Output node to Send email node. Configure to return confirmation.
Why: Provide a structured completion result (e.g., status or email ID) for logging, monitoring, or chaining.
7

Schedule (Trigger)

Add Trigger node → connect to Input.
Type: Schedule.
Frequency: Daily at 08:00 (choose timezone).
Enable trigger. The workflow will auto-run without manual chat input.
Why: Automates daily execution so the digest arrives proactively without user intervention.
8

Save, Publish, Test

Save workflow. Publish to activate trigger.
Optional manual test: Run workflow and enter a test email to verify the digest arrives.
Why: Ensures configuration is stored, activated, and validated before relying on unattended runs.

Variable References

Use prior node outputs in prompts or mappings:

Components Used

Tips

  • Keep Tool node messages explicit about desired structure.
  • Use distinct node names for clearer variable references.
  • Start without Trigger to validate outputs, then enable scheduling.
  • Refine email prompt for formatting improvements (tables, headings, color accents).

Troubleshooting

Workflow created. Daily digest will be generated and sent automatically each morning.
Extend later: add Delay node for post-meeting recap or Condition node for priority filtering.