Guide for upgrading Lindy SDK and migrating between versions. Use when upgrading SDK versions, migrating agents, or handling breaking changes. Trigger with phrases like "upgrade lindy", "lindy migration", "lindy breaking changes", "update lindy SDK".
npxskills add jeremylongshore/claude-code-plugins-plus-skills--skill lindy-upgrade-migrationLoading…
Lindy is a managed platform — agents run on Lindy's infrastructure. "Upgrades" mean reconfiguring agents for new capabilities, migrating agents between workspaces, or adapting to platform changes. Key concern: agents with webhooks, Lindymail, and phone numbers require reconfiguration after migration.
Document every agent before making changes:
| Agent Name | Trigger Type | Actions | Integrations | Webhook URL | Phone # |
|---|---|---|---|---|---|
| Support Bot | Email Received | Gmail Reply, Slack Notify | Gmail, Slack | N/A | N/A |
| Lead Router | Webhook | Sheets Update, Slack DM | Sheets, Slack | https://public.lindy.ai/... |
| N/A |
| Phone Screener | Call Received | Transfer, Agent Send | Phone | N/A | +1-555-0100 |
For each agent, document:
Phase 1: Internal-only agents (no customer impact)
→ Migrate, test, verify for 24-48 hours
Phase 2: Low-risk customer-facing agents (email triage, notifications)
→ Migrate during low-traffic window
→ Monitor for 24 hours
Phase 3: Critical agents (phone, live chat, lead routing)
→ Migrate with rollback plan ready
→ Keep old agent active in parallel for 48 hours
Option A — Template sharing:
Option B — Manual recreation:
These require special attention — they are NOT automatically transferred:
Webhooks:
Lindymail (Lindy-assigned email addresses):
Phone numbers:
Day 1-2: Both old and new agents active
→ Route test traffic to new agent
→ Compare task completion rates and output quality
Day 3: Gradual cutover
→ Redirect 50% of traffic to new agent
→ Monitor error rates and credit consumption
Day 4: Full cutover
→ Route 100% to new agent
→ Keep old agent paused (not deleted) for 7 days
Day 11: Cleanup
→ Delete old agent after 7-day safety window
When you have too many single-purpose agents:
## Billing, ## Technical, etc.)When Lindy adds new features (new actions, new models):
| Issue | Cause | Solution |
|---|---|---|
| Webhook URL changed | New agent gets new URL | Update all callers with new URL |
| Integration auth failed | OAuth not transferred | Re-authorize in new workspace |
| Knowledge base empty | Files not re-uploaded | Upload files to new agent's KB |
| Phone number unavailable | Not re-provisioned | Purchase new number in settings |
| Memory lost | Memories not exported | Manually re-create critical memories |
Proceed to Pro tier skills for advanced CI integration, deployment, and performance.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).