Lindy Debug Bundle
SkillAI & models'Comprehensive debugging toolkit for Lindy AI agents.
Use Lindy Debug Bundle in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Lindy Debug Bundle and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Lindy Debug Bundle skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by jeremylongshore/tons-of-skills-marketplace in skills/.curated/lindy-debug-bundle/SKILL.md and read by ahel’s review.
Current State
!node --version 2>/dev/null || echo 'Node.js not installed'
!python3 --version 2>/dev/null || echo 'Python not installed'
!curl --version 2>/dev/null | head -1 || echo 'curl not installed'
Overview
Systematic diagnostics for Lindy AI agent issues. Collects environment info, tests API connectivity, reviews agent task history, and generates a support bundle for Lindy's support team.
Prerequisites
- Access to Lindy dashboard (https://app.lindy.ai)
- curl installed for API testing
- Agent ID and webhook URLs available
Instructions
Step 1: Collect Environment Info
# Local environment diagnostics
echo "=== Local Environment ==="
echo "Node: $(node --version 2>/dev/null || echo 'N/A')"
echo "Python: $(python3 --version 2>/dev/null || echo 'N/A')"
echo "OS: $(uname -srm)"
echo "Date: $(date -u '+%Y-%m-%d %H:%M:%S UTC')"
echo "LINDY_API_KEY set: $([ -n "$LINDY_API_KEY" ] && echo 'yes' || echo 'NO')"
echo "LINDY_WEBHOOK_SECRET set: $([ -n "$LINDY_WEBHOOK_SECRET" ] && echo 'yes' || echo 'NO')"
Step 2: Test Webhook Connectivity
# Test webhook trigger endpoint
echo "=== Webhook Connectivity ==="
WEBHOOK_URL="${LINDY_WEBHOOK_URL:-https://public.lindy.ai/api/v1/webhooks/YOUR_ID}"
# Test without auth (expect 401)
echo "Without auth (expect 401):"
curl -s -o /dev/null -w "HTTP %{http_code} in %{time_total}s\n" \
-X POST "$WEBHOOK_URL" \
-H "Content-Type: application/json" \
-d '{"test": true}'
# Test with auth (expect 200)
echo "With auth (expect 200):"
curl -s -o /dev/null -w "HTTP %{http_code} in %{time_total}s\n" \
-X POST "$WEBHOOK_URL" \
-H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
-H "Content-Type: application/json" \
-d '{"test": true, "debug": "bundle-test"}'
Step 3: Review Agent Task History
In the Lindy dashboard:
- Navigate to the failing agent
- Open the Tasks tab
- Filter by Failed status
- For each failed task:
- Note the timestamp
- Click to expand step-by-step execution
- Identify the failing step (marked red)
- Copy the error message and input/output data
- Look for patterns: same step failing? same time of day? same input type?
Step 4: Check Integration Health
# Test outbound connectivity to common Lindy integration targets
echo "=== Integration Targets ==="
for url in \
"https://public.lindy.ai" \
"https://slack.com/api/auth.test" \
"https://www.googleapis.com/gmail/v1/users/me/profile" \
"https://api.notion.com/v1/users/me"
do
status=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$url" 2>/dev/null)
echo "$url -> HTTP $status"
done
Step 5: Diagnose Specific Failure Types
Trigger not firing:
- Verify agent status: active (not paused)
- Check trigger filter conditions
- For webhooks: test URL with curl
- For email: re-authorize Gmail/Outlook
- For schedule: verify timezone settings
Action failing:
- Check integration authorization (re-auth if token expired)
- Verify field references:
{{step_name.field}}syntax correct - Test the target service independently
- Check if action is a Premium Action (requires Pro plan)
Agent step looping:
- Review exit conditions — are they achievable?
- Check credit consumption (rapid drain = looping)
- Reduce available skills to 2-4 focused ones
- Add a fallback exit condition
High credit consumption:
- Review model selection: Gemini Flash (cheap) vs GPT-4 (expensive)
- Check for unnecessary agent steps (use deterministic actions instead)
- Review loop configurations for unbounded max cycles
Step 6: Generate Support Bundle
Compile the following for a support ticket to support@lindy.ai:
## Lindy Support Bundle
**Account**: [your email]
**Agent Name**: [agent name]
**Agent URL**: agents/[agent-id]
**Issue Start**: [date/time UTC]
**Frequency**: [every time / intermittent / once]
### Environment
- Browser: [Chrome/Firefox/Safari version]
- Plan: [Free/Pro/Business/Enterprise]
- Credit Balance: [remaining credits]
### Reproduction Steps
1. [step 1]
2. [step 2]
### Failed Task IDs
- [task-id-1] at [timestamp]
- [task-id-2] at [timestamp]
### Error Messages
[Copy exact error text from task detail view]
### What I Tried
- [attempt 1]
- [attempt 2]
Output
Deliver a time-bounded support bundle containing the affected agent and task IDs, reproduction steps, sanitized error messages, environment facts, and the result of the webhook and integration checks. Remove credentials, personal data, and full webhook URLs before sharing the bundle outside the workspace.
Examples
If tasks begin failing after an integration reconnect, capture one failed task ID, the failing action name, the HTTP status from the target, and the time the connection was reauthorized. A bundle saying “agent failed” without a task ID, timestamp, and reproducible trigger is insufficient for escalation.
Diagnostic Decision Tree
Agent not working?
├── No task created → Check trigger configuration
│ ├── Webhook? → Test with curl (Step 2)
│ ├── Email? → Re-authorize + check filters
│ └── Schedule? → Check timezone + credit balance
├── Task created but failed → Check task detail view
│ ├── Trigger step failed → Auth/connectivity issue
│ ├── Action step failed → Integration auth expired
│ ├── Condition step failed → Ambiguous condition prompt
│ └── Agent step looping → Exit conditions unreachable
└── Task completed but wrong result → Prompt/config issue
├── Wrong output → Refine agent prompt
├── Missing data → Check field references
└── Partial execution → Review condition branches
Error Handling
| Symptom | Likely Cause | Resolution |
|---|---|---|
| All agents failing simultaneously | Lindy platform outage | Check status.lindy.ai |
| Single agent failing | Agent-specific config issue | Review task detail view |
| Intermittent failures | Rate limits or credit exhaustion | Check usage dashboard |
| Slow execution | Model too large or too many steps | Switch to Gemini Flash, consolidate steps |
Resources
- Lindy Community
- Lindy Documentation
- Lindy Status
Next Steps
Proceed to lindy-rate-limits for credit and rate management.
Signals
- GitHub stars
- 3k
- Forks
- 415
- Last commit
- Oct 2026
ahel review
K2info
exfiltration (in references/implementation-guide.md)
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Item type
- skill
- Key
lindy-debug-bundle- Source
- github.com/jeremylongshore/tons-of-skills-marketplace
github.com/jeremylongshore/tons-of-skills-marketplace
Related picks
Skill · thedaviddias
The pick for JavaScriptmodern-javascript-patterns
Skill · wshobson
The pick for JavaScriptpython-performance-optimization
Skill · wshobson
The pick for Pythonpython-pro
Skill · jeffallan
The pick for Pythonnotion-meeting-intelligence
Skill · openai
The pick for Notionnotion-spec-to-implementation
Skill · davila7
The pick for Notion