Agent trigger update to new agent version

[Pwuts]

Problem

When updating an agent to a new version, webhook trigger URLs do not migrate to the new version. This creates a poor user experience because:

1. New URL required for each version: When an agent is updated (v1 → v2), triggering the old webhook URL still calls v1, not the updated v2
2. External integrations break: Users who have configured external services (e.g., Telegram bots, third-party webhooks) to call the agent's webhook URL must manually update the URL every time they publish a new agent version
3. No way to preserve URLs: Even removing and re-adding a webhook trigger generates a new URL

Current Behavior

As reported in testing on dev:

1. Build agent v1, set up webhook trigger → webhook URL works ✅
2. Update agent to v2, trigger the same webhook → v1 is called (not v2) ❌
3. Creating a new trigger → generates a new URL
4. Removing original trigger and creating new one → also generates a new URL

Expected Behavior

Users should be able to migrate/preserve webhook trigger URLs when updating their agent to a new version, so that:

• External integrations continue working without reconfiguration
• The same webhook URL can invoke the latest (or a specified) agent version

Proposed Solution

1. Automatic migration (default): When publishing a new agent version, automatically migrate compatible webhook triggers by updating the AgentPreset to reference the new graph version
2. Manual migration: For cases where auto-migration isn't possible or the user has opted out, provide a UI option to manually migrate an existing webhook trigger to a newer agent version

Impact

This is particularly problematic for integrations like Telegram bots and other external services where changing the webhook URL requires reconfiguration on the external platform.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[CodeVishal-17]

Thanks for raising this — the current behavior makes webhook-based integrations (Telegram bots, external services, etc.) quite fragile.

Preserving or migrating webhook trigger URLs across agent versions would significantly improve DX and avoid repeated reconfiguration on every publish.

The proposed auto-migration + optional manual migration approach sounds reasonable. Happy to help test or contribute once the direction is finalized.