lindy-core-workflow-b
Configure Lindy triggers, scheduling, multi-agent delegation, and automation. Use when setting up trigger-based workflows, scheduling agents, building multi-agent societies, or configuring agent delegation. Trigger with phrases like "lindy automation", "schedule lindy agent", "lindy workflow automation", "lindy delegation", "lindy multi-agent".
Best use case
lindy-core-workflow-b is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure Lindy triggers, scheduling, multi-agent delegation, and automation. Use when setting up trigger-based workflows, scheduling agents, building multi-agent societies, or configuring agent delegation. Trigger with phrases like "lindy automation", "schedule lindy agent", "lindy workflow automation", "lindy delegation", "lindy multi-agent".
Teams using lindy-core-workflow-b should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lindy-core-workflow-b/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lindy-core-workflow-b Compares
| Feature / Agent | lindy-core-workflow-b | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure Lindy triggers, scheduling, multi-agent delegation, and automation. Use when setting up trigger-based workflows, scheduling agents, building multi-agent societies, or configuring agent delegation. Trigger with phrases like "lindy automation", "schedule lindy agent", "lindy workflow automation", "lindy delegation", "lindy multi-agent".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Lindy Core Workflow B: Triggers & Multi-Agent Automation
## Overview
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.
## Prerequisites
- Completed `lindy-core-workflow-a` (agent creation)
- Integrations authorized (Gmail, Slack, etc.)
- For delegation: multiple agents created
## Instructions
### Step 1: Configure Trigger Filters
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"
```
### Step 2: Multiple Triggers (Same Workflow)
One agent can respond to multiple trigger types feeding into the same workflow:
1. Create first trigger (e.g., Webhook Received)
2. Click **"New Trigger"** to add a second (e.g., Email Received)
3. Connect grey arrows from both triggers to the first action step
4. The agent processes both identically
### Step 3: Multiple Workflows (Different Triggers)
A single agent can run entirely different workflows based on trigger type:
- **Trigger A** (Email Received) -> Classify + Draft Reply
- **Trigger B** (Chat Message) -> Search KB + Respond in chat
Each trigger connects to its own action chain.
### Step 4: Schedule-Based Triggers
For recurring automation (daily reports, weekly digests):
1. Add trigger > **Schedule**
2. Configure timing: `Every weekday at 9:00 AM`
3. Options: daily, weekly, monthly, or custom cron
4. The agent runs automatically at the scheduled time
### Step 5: Calendar Event Trigger
For meeting-related automation:
1. Add trigger > **Calendar Event Start**
2. Set **Minutes Offset**:
- `-30` = trigger 30 minutes BEFORE event
- `+5` = trigger 5 minutes AFTER event starts
3. Use case: Pre-meeting briefing agent pulls attendee data and sends summary
### Step 6: Multi-Agent Delegation (Societies of Lindies)
Build modular agent systems where specialized agents collaborate:
**Architecture**:
```
[Lead Generator Lindy]
↓ Agent Send Message
[Outreach Lindy]
↓ Agent Send Message
[Meeting Scheduler Lindy]
```
**Setup**:
1. Give the receiving agent an **Agent Message Received** trigger
2. In the sending agent, add action: **Agent Send Message**
3. Select the target Lindy from the dropdown (shows all agents with Agent triggers)
4. Choose what context to pass — selective context reduces token cost
**Benefits**:
- **Modularity**: Change one agent without affecting others
- **Cost savings**: Send only relevant context, not full history
- **Specialization**: Each agent excels at one task
- **Shared memory**: Societies share memory across tasks
### Step 7: Linked Actions & Channels
**Linked Actions** create downstream execution paths after an action completes:
- Standard linked action: Immediate follow-up (email sent -> log to sheet)
- **Channel**: Listen for future events (email sent -> wait for reply -> process reply)
**Multi-channel example**:
```
Send Email → [Channel: Email Reply Received]
→ [Channel: Slack Message Received]
Each channel maintains its own conversation thread.
```
### Step 8: Looping
For batch processing (e.g., process 50 leads from a spreadsheet):
1. Add a **Loop** step
2. Configure:
- **Items**: Static list, dynamic data, or AI-generated
- **Max Cycles**: Limit iterations (prevent runaway)
- **Max Concurrent**: Parallel execution limit
- **Output**: Data passed from inside the loop to subsequent steps
3. Only defined loop output is accessible outside the loop
## Trigger Types Quick Reference
| 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 |
## Error Handling
| 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 |
## Resources
- [Triggers](https://docs.lindy.ai/fundamentals/lindy-101/triggers)
- [Delegation 101](https://www.lindy.ai/academy-lessons/delegation-101)
- [Action Configuration](https://www.lindy.ai/academy-lessons/action-configuration)
## Next Steps
Proceed to `lindy-common-errors` for troubleshooting.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".