From lindy-pack
Configures Lindy triggers (email, Slack, schedule, calendar), filters, multiple triggers/workflows, and multi-agent delegation for automation and agent societies.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin lindy-packThis skill is limited to using the following tools:
Configure trigger-based automation, scheduled agents, and multi-agent delegation
Guides creation and configuration of multi-step Lindy AI agent workflows with triggers, actions, conditions, prompts, and knowledge bases.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Configure trigger-based automation, scheduled agents, and multi-agent delegation ("Societies of Lindies"). Covers all trigger types, trigger filters, multiple triggers per agent, and the Agent Send Message delegation pattern.
lindy-core-workflow-a (agent creation)Trigger filters add conditional logic that determines WHICH events wake the agent. Filters are not case-sensitive and support AND/OR operators with condition groups.
Email trigger filter example:
Filter: sender contains "support" AND subject does not contain "auto-reply"
Slack trigger filter example:
Filter: channel equals "#help-desk" AND message contains "urgent"
One agent can respond to multiple trigger types feeding into the same workflow:
A single agent can run entirely different workflows based on trigger type:
For recurring automation (daily reports, weekly digests):
Every weekday at 9:00 AMFor meeting-related automation:
-30 = trigger 30 minutes BEFORE event+5 = trigger 5 minutes AFTER event startsBuild modular agent systems where specialized agents collaborate:
Architecture:
[Lead Generator Lindy]
↓ Agent Send Message
[Outreach Lindy]
↓ Agent Send Message
[Meeting Scheduler Lindy]
Setup:
Benefits:
Linked Actions create downstream execution paths after an action completes:
Multi-channel example:
Send Email → [Channel: Email Reply Received]
→ [Channel: Slack Message Received]
Each channel maintains its own conversation thread.
For batch processing (e.g., process 50 leads from a spreadsheet):
| Trigger | Filter Options | Use Case |
|---|---|---|
| Webhook Received | Headers, body fields | External API integration |
| Email Received | Sender, subject, label | Inbox automation |
| Schedule | Time, recurrence | Recurring reports |
| Chat Message | User, content | Interactive bot |
| Slack Message | Channel, keyword, user | Team automation |
| Agent Message | Sending agent | Multi-agent delegation |
| Calendar Event | Event type, offset | Meeting automation |
| Google Sheets Row | Sheet, column values | Data pipeline |
| Issue | Cause | Solution |
|---|---|---|
| Trigger fires too often | No filter configured | Add trigger filters with AND/OR conditions |
| Delegation fails | Target agent missing Agent trigger | Add Agent Message Received trigger to target |
| Schedule not firing | Timezone mismatch | Verify timezone in agent settings |
| Loop runs forever | No max cycles set | Always set Max Cycles limit |
| Channel never activates | Reply sent to wrong thread | Verify thread context in channel config |
| Context too large | Passing full history to delegate | Use selective context in Agent Send Message |
Proceed to lindy-common-errors for troubleshooting.