Send a reviewer a contextual nudge when a pull request stalls
The example distinguishes waiting reviews, requested re-reviews, and approved changes and prepares reminders containing the work's size and blocking context.
Tool
Lindy use cases: 28 examples
Source-linked workflows that name Lindy. Part of the AI agent use cases on UsecaseBoard, or browse all use cases.
Turn merged pull requests into user-facing release-note drafts
The scenario distinguishes customer-visible changes from internal work and drafts a recurring changelog with links back to the merged pull requests.
Answer a Slack metric question with a visible warehouse query and result table
The scenario translates a business question into a warehouse query and keeps the query and returned data beside the answer for team verification.
Compare customer-survey themes before and after a product change
The example groups CSAT and NPS comments into themes and examines how explicit feedback changed around a release or pricing update.
Cluster differently worded support tickets into emerging failure patterns
The scenario groups recent tickets by likely shared root cause and compares the cluster's timing with product changes to support investigation.
Carry sales-cycle commitments into a customer-success handoff
The example gathers promises from calls and email before coordinating the CRM change, handoff document, customer-success notification, kickoff, and welcome draft.
Explain a shared research article in the context of the team's current work
The example reads a linked article, summarizes its claims, and compares the implications with the team's documented plans before saving takeaways.
Recover a previously shared file or number with its original Slack context
The scenario searches channels, threads, and attachments to retrieve a remembered artifact and the qualifications that accompanied it.
Receive one out-of-office digest with mentions prioritized
The published routine summarizes selected channels during an absence, puts direct mentions first, and allows a separately defined urgent escalation path.
Coordinate meeting follow-through across tasks, notes, and the next check-in
The scenario uses the call transcript to prepare owned actions, a follow-up email, document updates, and a proposed next meeting.
Audit a workweek for double bookings and avoidable meeting congestion
The example flags conflicting and back-to-back events, proposes feasible moves, and helps the user review meetings that may no longer serve a purpose.
Find a meeting slot that respects several calendars and working time zones
The scenario compares attendee availability and local working hours, proposes suitable slots, and books the selected option after confirmation.
Track new commitments and completed work in one evolving personal task list
The scenario watches connected calls and messages for explicit commitments, adds dated tasks, and reconciles completion and waiting states in a daily review.
Prepare a return-from-leave briefing across meetings, messages, and tickets
The example combines missed conversations and recordings into a prioritized catch-up brief, including decisions and items assigned to the returning user.
Consolidate repeated on-call reports into one evidence-rich bug ticket
Lindy's scenario identifies actionable bugs in an on-call channel, checks existing issues, and attaches new reports to the appropriate ticket.
Chase missing close documents with an owner-by-owner deadline list
The example tracks missing receipts, invoice approvals, and unanswered finance queries, then prepares staged reminders and a holdout list for the close owner.
Track which escalated customers are waiting and what would resolve each case
The scenario combines ticket aging, unresolved dependencies, and SLA clocks into a daily escalation watch with draft status updates.
Develop a launch-video storyboard and revise the generated cut in chat
Lindy demonstrates turning a short product-video brief into a script, storyboard, and reviewable draft, with follow-up requests for concrete edits.
Flag yesterday's ad campaigns that missed the team's performance targets
The example calculates daily cross-platform ROAS, CPA, and CTR and surfaces campaigns that need review rather than requiring separate platform checks.
Build a shareable live page for spend, return, and funnel metrics
The scenario combines marketing sources into a dashboard that the team can query and refine through natural-language requests.
Reconcile CRM next-step gaps with the latest customer email context
The published example updates a deal from a Slack instruction and finds recent customer replies or commitments that have not reached the CRM record.
Find an invoice across billing inboxes and challenge an unexplained overage
The scenario checks incoming invoices against order details, records the intake status, and prepares a query when an invoice includes an unquoted charge.
Build a vendor shortlist with source-checked requirements and seat-cost math
The scenario researches software vendors, verifies specific capabilities, and prepares a cost-and-tradeoff comparison sheet tailored to a team's needs.
Refresh the staff-meeting slide deck from this week's operating numbers
Lindy demonstrates building a recurring leadership deck from CRM, support, usage, and finance sources while preserving the team's slide template.
Reuse a previously solved support issue before assigning a harder case
The example retrieves similar resolved Zendesk tickets to draft a response and uses past resolution context to suggest an owner for unfamiliar problems.
Watch competitor pricing changes alongside a weekly product-and-hiring digest
Lindy's published example combines scheduled competitor research with a separate pricing-page change watch and a Slack tracker update.
Receive an AI-researched discovery-call brief before the meeting
Annika Helendi's Lindy trial describes a calendar-triggered call-prep template that researches the attendee with LinkedIn, Crunchbase, and web search, then emails a brief shortly before the meeting; she distinguishes this from more complex agent workflows.