FeaturedPersonal Productivity#Pets#Pet Care#Vaccination Reminder#Telegram#DataTable#Loop

Daily Pet Care Reminder Loop

Find due pet-care tasks, send one reminder per record, mark each row as notified, and finish with a daily run summary.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Pets#Pet Care#Vaccination Reminder#Telegram#DataTable#Loop

Click a node to select it — same as the Heym editor; the panel shows its settings.

6 nodes · Free & source-available

Daily Pet Care Reminder Loop

Keep routine pet-care reminders organized with a deterministic scheduled workflow. This template reads due tasks from a Heym DataTable, loops through them one at a time, sends the configured Telegram reminder, and marks each row so the same task is not sent repeatedly.

What this workflow does

  1. PetCareSchedule starts the workflow each morning
  2. FindDueCareTasks selects due, enabled, and unsent care-task rows
  3. CareTaskLoop processes one pet task at a time
  4. SendPetCareReminder messages the configured household chat
  5. MarkReminderSent updates the exact source row and advances the loop
  6. DailyCareSummary runs only after every row has been handled

Use cases

  • Vaccination and booster reminders
  • Grooming, medication-administration, and preventive-care schedules
  • Multi-pet household task lists
  • Rescue or foster care coordination

Setup

Create a Pet Care Tasks DataTable with petName, taskLabel, nextDueDate, reminderEnabled, reminderStatus, chatId, and lastReminderAt columns. Connect a Telegram credential and review the destination chat IDs. This is an administrative reminder workflow; it does not diagnose conditions, prescribe treatment, or replace veterinary advice.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym