Skip to main content
skill CX Codex

lindy-core-workflow-b — Claude Code skill: what it does

lindy-core-workflow-b is a Claude Code skill for configuring Lindy triggers, Cron schedules, and multi-agent delegation.

MIT 1 installs ★ 2,935 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code
Open on GitHub

What lindy-core-workflow-b does

The skill equips Claude Code with instructions for Lindy automation flows. It covers case-insensitive trigger filters with boolean logic alongside Cron schedules. Calendar triggers support minute offsets.

A core section focuses on multi-agent collaboration via the Agent Send Message action. Delegation fails if the target Lindy lacks an Agent Message Received trigger. For batch jobs, loop steps require an explicit Max Cycles cap to prevent runaway processes.

Setup requires completing lindy-core-workflow-a first and authorizing services such as Gmail or Slack. The skill also advises passing selective context rather than full histories to keep token usage down.

What it helps with

  • configure Lindy triggers with case-insensitive filters
  • set up scheduled runs using Cron or calendar offsets
  • delegate tasks across Lindy agents via Agent Send Message
  • prevent infinite loops by defining a Max Cycles limit

Example prompts for the agent

  • Configure a daily scheduled report in Lindy that posts to Slack
  • Set up delegation between a lead generator Lindy and an outreach agent
  • Add an email trigger filter that excludes auto-replies

How to install lindy-core-workflow-b

1Skills CLI (Vercel)

npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code

2Manually: put the files in place

~/.claude/skills/lindy-core-workflow-b/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/lindy-core-workflow-b/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about lindy-core-workflow-b

How to install lindy-core-workflow-b in Claude Code?

Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-core-workflow-b -a claude-code in your terminal. The configuration is saved to ~/.claude/skills/lindy-core-workflow-b/SKILL.md.

What does lindy-core-workflow-b do?

It guides the assistant through configuring triggers, scheduling, and multi-agent delegation patterns in Lindy.

What are the prerequisites for this skill?

You must complete lindy-core-workflow-a first and connect the necessary integrations like Slack or Gmail.

Source text

SKILL.md · MIT
---
name: lindy-core-workflow-b
description: '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".

  '
allowed-tools: Read, Write, Edit, Bash(curl:*)
version: 1.20.0
license: MIT
author: Jeremy Longshore <[email protected]>
tags:
- saas
- lindy
- workflow
compatibility: Designed for Claude Code
---
# 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 |

## Output

Produce a production-ready workflow handoff: trigger contract, action sequence,
idempotency strategy, escalation behavior, and test results for both success
and failure paths. State which downstream system owns each side effect.

## Examples

For an inbox-triage workflow, receive one message event, classify it against a
fixed policy, create one follow-up task only when the policy requires it, and
write the event ID to the idempotency store. Replaying the fixture demonstrates
that the same message cannot create a duplicate task.

## 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.

© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace

Similar skills

All skills for Automation and no-code: n8n, Zapier, Make →

From the same set139

The whole set →
posthog-webhooks-events posthog-webhooks-events registers PostHog webhook destinations through the API, handles the incoming payloads, and runs bounded event queries with HogQL or the private API. CX Codex +1 1installs instantly-webhooks-events instantly-webhooks-events guides the setup and operation of Instantly API v2 webhooks with schema checks, deduplication, and privacy safeguards. CX Codex +1 1installs windsurf-data-handling The windsurf-data-handling skill maps data flows, sets context exclusions, and gathers evidence for privacy and compliance reviews around Devin Desktop, formerly Windsurf. CX Codex +1 1installs windsurf-flows-automation windsurf-flows-automation — a skill for building and managing Windsurf Flows, the automation scripts for repetitive dev work. Turn routine tasks into one-command flows. CX Codex +1 1installs deepgram-core-workflow-b The deepgram-core-workflow-b skill outlines real-time transcription with Deepgram over WebSocket. Use it when adding live captions, voice controls, or speech features to an app. CX Codex +1 1installs code-documentation-analyzer Auto-activating skill for auditing code documentation: API references, user guides, architecture docs. Triggers on phrases like "code documentation analyzer" or "code analyzer". CX Codex +1 1installs retellai-policy-guardrails retellai-policy-guardrails sets boundaries and tool limits for Retell AI phone voice agents. Useful when you need reliable call workflows with human handoffs. CX Codex +1 1installs openevidence-deploy-integration openevidence-deploy-integration plans an OpenEvidence rollout for a clinical workflow, covering the pilot, staff training, governance checks, and rollback conditions. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open