Agent skill · data analytics · jeremylongshore
lindy-common-errors
Troubleshoot common Lindy AI agent errors and workflow failures.
Why this skill is useful
Provides specific troubleshooting commands and integration patterns for the Lindy AI agent that the AI wouldn't reliably generate on its own.
What it needs
Requires curl installed locally. Requires lindy account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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: Cause Diagnostic Fix ------- ----------- ----- Wrong URL Check webhook URL in agent config Copy exact URL from trigger settings Missing auth curl -v shows 401 Add Authorization: Bearer <secret> header Agent inactive Dashboard shows agent paused Activate the agent Filter blocking Trigger filter too restrictive Review filter conditions, test with broader filter Wrong HTTP method Using GET instead of POST Lindy webhooks require POST 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-common-errors