---
title: "Lindy for recurring ops work"
canonical: "https://agenticfeats.com/c/lindy-for-recurring-ops-work/"
agents: ["Lindy"]
evidence_grade: "A"
outcome: "completed"
job_type: "Ops and IT"
roles: ["Founder or owner", "Operations"]
source_url: "https://app.therundown.ai/guides/build-a-lindy-agent-that-never-drops-a-follow-up"
source_date: "2026-09-04"
published: "2026-10-13"
updated: "2026-10-13"
---

> From Agentic Feats: sourced examples of AI agents at work. Map of the site for agents: https://agenticfeats.com/llms.txt

# Lindy for recurring ops work

Lindy, connected to Slack, Notion, Gmail and Calendar, analyzed a guide library, built a staff meeting deck, and created a Notion guide idea from Slack.

Result: Lindy produced a finished Monday staff meeting deck as a web link in 10 to 15 minutes and created a Notion page after approval.

## How it was set up

Lindy connected to Slack, Notion, Gmail, Google Calendar and Drive. Used suggested prompts and prebuilt routines, with approval required for actions through connected accounts.

## Worth knowing

Lindy works as a background teammate, so tasks take time. It asks for approval before creating items through a connected account.

## Prompt

```text
Review [set of documents or guides] from [time period] and summarize [trends, how coverage has changed, and what kind of content we make].
```

## Evidence note

Guide authors describe their own tests with screenshots; no repo or public output link

## Sources

- Original: https://app.therundown.ai/guides/build-a-lindy-agent-that-never-drops-a-follow-up

## The receipt

- Agent: Lindy
- Evidence: Shown (grade A, artifact linked)
- Outcome: Completed
- Job type: Ops and IT
- Roles: Founder or owner, Operations
- Source: Blog
- Published: 2026-09-04
- Added: 2026-10-13
