Directory
Search, filter by tool or topic, sort, and save ideas in this browser.
Loading directory…
Tools
Topics
28matches
The example distinguishes waiting reviews, requested re-reviews, and approved changes and prepares reminders containing the work's size and blocking context.
The scenario distinguishes customer-visible changes from internal work and drafts a recurring changelog with links back to the merged pull requests.
The scenario translates a business question into a warehouse query and keeps the query and returned data beside the answer for team verification.
The example groups CSAT and NPS comments into themes and examines how explicit feedback changed around a release or pricing update.
The scenario groups recent tickets by likely shared root cause and compares the cluster's timing with product changes to support investigation.
The example gathers promises from calls and email before coordinating the CRM change, handoff document, customer-success notification, kickoff, and welcome draft.
The example reads a linked article, summarizes its claims, and compares the implications with the team's documented plans before saving takeaways.
The scenario searches channels, threads, and attachments to retrieve a remembered artifact and the qualifications that accompanied it.
The published routine summarizes selected channels during an absence, puts direct mentions first, and allows a separately defined urgent escalation path.
The scenario uses the call transcript to prepare owned actions, a follow-up email, document updates, and a proposed next meeting.
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.
The scenario compares attendee availability and local working hours, proposes suitable slots, and books the selected option after confirmation.
The scenario watches connected calls and messages for explicit commitments, adds dated tasks, and reconciles completion and waiting states in a daily review.
The example combines missed conversations and recordings into a prioritized catch-up brief, including decisions and items assigned to the returning user.
Lindy's scenario identifies actionable bugs in an on-call channel, checks existing issues, and attaches new reports to the appropriate ticket.
The example tracks missing receipts, invoice approvals, and unanswered finance queries, then prepares staged reminders and a holdout list for the close owner.
The scenario combines ticket aging, unresolved dependencies, and SLA clocks into a daily escalation watch with draft status updates.
Lindy demonstrates turning a short product-video brief into a script, storyboard, and reviewable draft, with follow-up requests for concrete edits.
The example calculates daily cross-platform ROAS, CPA, and CTR and surfaces campaigns that need review rather than requiring separate platform checks.
The scenario combines marketing sources into a dashboard that the team can query and refine through natural-language requests.
The published example updates a deal from a Slack instruction and finds recent customer replies or commitments that have not reached the CRM record.
The scenario checks incoming invoices against order details, records the intake status, and prepares a query when an invoice includes an unquoted charge.
The scenario researches software vendors, verifies specific capabilities, and prepares a cost-and-tradeoff comparison sheet tailored to a team's needs.
The example narrows a funnel change by cohort and authentication path, then correlates analytics, tickets, and deployment history to investigate likely causes.
Lindy demonstrates building a recurring leadership deck from CRM, support, usage, and finance sources while preserving the team's slide template.
The example retrieves similar resolved Zendesk tickets to draft a response and uses past resolution context to suggest an owner for unfamiliar problems.
Lindy's published example combines scheduled competitor research with a separate pricing-page change watch and a Slack tracker update.
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.