Troubleshoot common Lindy AI agent errors and workflow failures.

MITAuto-check passedDevelopment

Install Lindy Common Errors

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-common-errors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-common-errors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lindy-common-errors .claude/skills/lindy-common-errors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lindy-common-errors
GitHub stars
2.8k
Token cost
~1.9k tokens
SKILL.md length
784 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Troubleshoot common Lindy AI agent errors and workflow failures.

  • Works in 3 steps: Capture the failing run identifier,… → Reproduce the behavior in a test agent… → Apply the smallest trace-supported…
  • Encountering errors
  • SKILL.md covers Overview, Prerequisites, Instructions and Trigger Errors, plus 8 more sections
  • Calls curl; reaches public.lindy.ai

What it does

Lindy Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Troubleshoot common Lindy AI agent errors and workflow failures. Use when encountering errors, debugging agent failures, or resolving integration problems. Trigger with phrases like "lindy error", "lindy not working", "debug lindy", "lindy troubleshoot", "lindy agent failed".

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Development, covering Debugging and Webhooks. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Encountering errors
  • Debugging agent failures
  • Resolving integration problems
  • With phrases like lindy error

Example prompts

  • “lindy error”
  • “lindy not working”
  • “debug lindy”
  • “/lindy-common-errors”

Requirements

  • A credential in YOUR_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*), Grep

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Capture the failing run identifier, trigger payload shape, and first failing
  2. Reproduce the behavior in a test agent or disabled workflow using a bounded
  3. Apply the smallest trace-supported remediation, then rerun both the failure

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • public.lindy.ai

    Also links to:

    • docs.lindy.ai
    • status.lindy.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Lindy Common Errors loads about 1.9k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 784 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 784 words, ~1,858 tokens.

Download SKILL.mdSave it as .claude/skills/lindy-common-errors/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
lindy-common-errors
description
Troubleshoot common Lindy AI agent errors and workflow failures. Use when encountering errors, debugging agent failures, or resolving integration problems. Trigger with phrases like "lindy error", "lindy not working", "debug lindy", "lindy troubleshoot", "lindy agent failed".
allowed-tools
Read, Write, Edit, Bash(curl:*), Grep
compatibility
Designed for Claude Code
version
1.20.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, lindy, debugging

Lindy Common Errors

Overview

Troubleshooting guide for Lindy AI agent errors. Lindy agents fail at specific points in the workflow: trigger reception, action execution, condition evaluation, or exit condition evaluation. This guide covers each failure class.

Prerequisites

  • Access to Lindy dashboard (https://app.lindy.ai)
  • Ability to view agent Tasks tab for error details
  • For webhook debugging: curl installed

Instructions

  1. Capture the failing run identifier, trigger payload shape, and first failing step without copying sensitive fields into the incident record.
  2. Reproduce the behavior in a test agent or disabled workflow using a bounded input.
  3. Apply the smallest trace-supported remediation, then rerun both the failure fixture and a normal-success fixture before restoring schedules.

Trigger Errors

Webhook Not Firing

Symptoms: No task created when webhook is sent Causes & Solutions:

CauseDiagnosticFix
Wrong URLCheck webhook URL in agent configCopy exact URL from trigger settings
Missing authcurl -v shows 401Add Authorization: Bearer <secret> header
Agent inactiveDashboard shows agent pausedActivate the agent
Filter blockingTrigger filter too restrictiveReview filter conditions, test with broader filter
Wrong HTTP methodUsing GET instead of POSTLindy webhooks require POST
bash
# Diagnostic: Test webhook connectivity
curl -v -X POST "https://public.lindy.ai/api/v1/webhooks/YOUR_ID" \
  -H "Authorization: Bearer YOUR_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"test": true}'
# Expect: 200 OK
Email Trigger Not Activating

Symptoms: Emails arrive but agent does not wake up Solutions:

  1. Verify Gmail/Outlook authorization is current (re-authorize if expired)
  2. Check label filter — Lindy Email Received trigger can filter by label
  3. Confirm email matches trigger filter conditions (sender, subject, etc.)
  4. Check that agent is active, not paused
Schedule Trigger Missed

Symptoms: Agent did not run at scheduled time Solutions:

  1. Verify timezone settings match your expectation
  2. Check credit balance — agents stop if credits exhausted
  3. Review schedule configuration (daily vs weekday vs custom)

Action Errors

Slack Send Failed
ErrorCauseFix
Channel not foundChannel name wrong or privateUse exact channel name; ensure bot is invited
Not authorizedSlack token expiredRe-authorize Slack in Lindy integrations
Rate limitedToo many messagesReduce trigger frequency or batch messages
Gmail Send Failed
ErrorCauseFix
Authentication expiredOAuth token expiredRe-authorize Gmail in Settings
Recipient rejectedInvalid email addressValidate email format in prior step
Draft not foundThread ID mismatchVerify thread context in action config
HTTP Request Action Failed
ErrorCauseFix
Connection refusedTarget API downVerify target URL is reachable
401 UnauthorizedAuth header misconfiguredCheck Authorization header value
TimeoutTarget API slowIncrease timeout or optimize target endpoint
SSL errorInvalid certificateEnsure target uses valid HTTPS cert
bash
# Diagnostic: Test target API independently
curl -v -X POST "https://api.yourapp.com/endpoint" \
  -H "Content-Type: application/json" \
  -d '{"test": true}'
Run Code Action Failed
ErrorCauseFix
Import errorLibrary not availableUse only pre-installed libraries (pandas, numpy, etc.)
Type errorInput variable is stringCast explicitly: int(var), json.loads(var)
TimeoutLong-running computationOptimize code; avoid infinite loops
Return value emptyNo return statementAdd explicit return with result data
Show full SKILL.md (327 more words)Show less
Knowledge Base Returns No Results
CauseFix
Fuzziness at 0 (keyword only)Increase to 100 for semantic search
Content not indexedTrigger Resync Knowledge Base action
Query too vagueSwitch field to AI Prompt mode with specific instructions
File too large (>20MB)Split into smaller files

Agent Step Errors

Agent Loops Indefinitely

Cause: Exit conditions never satisfied Fix: Add measurable, achievable exit conditions:

Primary: "Found at least 3 relevant results"
Fallback: "Made 5 search attempts without finding results"
Agent Picks Wrong Condition Branch

Cause: Ambiguous condition prompt Fix: Make conditions mutually exclusive with clear criteria:

Branch A: "Go down this path if the email mentions billing, payment, or invoice"
Branch B: "Go down this path if the email mentions a technical issue, bug, or error"
Branch C: "Go down this path for all other topics"
Credit Overrun Warning

Symptom: "Task using more resources than expected" pause Cause: Agent step consuming too many credits (complex reasoning) Fix: Simplify prompt, reduce available skills (2-4 max), use smaller model

Debugging Checklist

  1. Open agent Tasks tab — find the failed task
  2. Click into the task — review each step's input/output
  3. Identify the failing step (red indicator)
  4. Check the step's error message and stack trace
  5. Verify integration authorizations are current
  6. Test the trigger independently (curl for webhooks)
  7. Test the action independently (manual run)
  8. Check credit balance — insufficient credits halt execution

Error Handling

Error CategoryHTTP StatusRetry?Notes
Auth failure401NoRe-authorize integration
Rate limited429YesWait for credit reset
Agent not found404NoVerify agent exists and is active
Action timeout504YesSimplify step or increase timeout
Run Code error500MaybeFix code, then retry
Credit exhausted402NoUpgrade plan or wait for monthly reset

Output

Return a compact incident record: observed error, failing trigger or action, correlation ID, reproduction input, remediation applied, and the verification result. Separate platform failures from errors in the connected service.

Examples

When an agent step times out, replay the same bounded input in a test agent, inspect the step trace, reduce the action payload or timeout only where the trace identifies the bottleneck, then rerun the original fixture before re-enabling the production schedule.

Resources

Next Steps

Proceed to lindy-debug-bundle for comprehensive diagnostics.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/lindy-common-errors of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md
  • references/implementation.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lindy Common Errors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lindy Common Errors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lindy Common Errors this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.9kAutomated safety check: PassMIT
Shopify DebuggingMicrock/ordinary-claude-skills404—~3.8kAutomated safety check: PassCustom licence
Make Scenario Operationsintegromat/make-skills128—~1.2kAutomated safety check: PassMIT
Tg Bot Opsserejaris/personal-corp-os229—~1.6kAutomated safety check: NotesMIT
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Gumroad Prod Consoleantiwork/gumroad9.8k—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Shopify Debugging

    Microck/ordinary-claude-skills

    Complete debugging and troubleshooting guide for Shopify including Liquid errors, theme preview debugging, API error handling, JavaScript console debugging, network request inspection, cart issues…

    404 GitHub stars~3.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Make Scenario Operations

    integromat/make-skills

    A skill your agent uses when running a scenario, switching it on or off, reviewing or debugging executions, or investigating a webhook that receives nothing.

    128 GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Tg Bot Ops

    serejaris/personal-corp-os

    A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.

    229 GitHub stars~1.6k tokensUpdated 2 days ago
    Backend & APIsAuto-check: notes
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • LangBot Plugin Development

    langbot-app/LangBot

    Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.

    18k GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Lindy Common Errors

What does Lindy Common Errors do?

Troubleshoot common Lindy AI agent errors and workflow failures. Lindy Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Troubleshoot common Lindy AI agent errors and workflow failures.

When should I use Lindy Common Errors?

Lindy Common Errors fits situations like: encountering errors; debugging agent failures; resolving integration problems; with phrases like lindy error.

How do I install Lindy Common Errors in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-common-errors -a claude-code`. Or copy the skill folder (skills/.curated/lindy-common-errors in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-common-errors in your project. Claude Code loads it when a task matches its description.

How do I install Lindy Common Errors in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-common-errors -a codex`. Or copy the skill folder (skills/.curated/lindy-common-errors in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-common-errors in your project. Codex loads it when a task matches its description.

Can I use Lindy Common Errors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-common-errors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lindy-common-errors, .gemini/skills/lindy-common-errors, .github/skills/lindy-common-errors and .opencode/skills/lindy-common-errors in your project.

What does Lindy Common Errors need to run?

Going by SKILL.md and its folder, Lindy Common Errors needs the command-line tools its instructions call (curl). Our summary lists: A credential in YOUR_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Lindy Common Errors access the network?

SKILL.md names 3 domains. In commands or code: public.lindy.ai; the agent is likely to contact it when it follows the instructions. As links in the text: docs.lindy.ai and status.lindy.ai. This is read from the text; nothing was executed.

Is Lindy Common Errors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lindy Common Errors use?

Lindy Common Errors is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lindy Common Errors use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Lindy Common Errors?

Skills that share tags, products or a category with Lindy Common Errors: Shopify Debugging (Microck/ordinary-claude-skills, 404 stars), Make Scenario Operations (integromat/make-skills, 128 stars), Tg Bot Ops (serejaris/personal-corp-os, 229 stars) and Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lindy Common Errors?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.