[Feature New API] Manage Web-hook Notifications from Inactive Accounts

[Arbaz-Dispo]

🌟 Describe the Feature

Currently, apps continue to receive web-hook notifications from inactive locations where the app is installed but not actively used. This consumes unnecessary server resources. We need a way to unsubscribe from inactive accounts’ web-hooks or to filter webhook notifications at the source level.

🚀 Justification

• Apps may remain installed in many accounts that no longer actively use them.
• Continuing to receive webhook notifications from these inactive accounts wastes processing power and storage.
• Filtering or unsubscribing at the source would improve efficiency and reduce infrastructure costs.

📝 Suggestions

No response

Product Area

marketplace

📋 Use Case

• Reduce unnecessary webhook traffic from accounts that are not actively using the app
• Save server resources currently consumed by processing irrelevant data
• Maintain clean and efficient integrations at scale

🚨 Why Should This Be Prioritized?

1. Reduces wasted compute and storage caused by webhook spam from inactive accounts
2. Improves scalability for apps integrated with hundreds or thousands of accounts
3. Without this, apps face unnecessary costs and performance degradation when handling inactive accounts traffic

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.