lindy-common-errors

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
version	1.15.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","lindy","debugging"]
compatibility	Designed for Claude Code

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

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

# 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