What does this PR do?

This PR contains two sets of changes:

1. Original Changes (Delegation Credential Error Webhook Fixes)

• Fixes the delegation credential error webhook system to properly resolve organizations from delegation credentials
• Changes webhook trigger parameter fromorgId todelegationCredentialId for more accurate organization resolution
• Adds newWebhookRepository.findByOrgIdAndTrigger() method for fetching webhooks by organization and trigger event
• Enriches webhook payload withdelegationCredentialId andorganizationId fields
• Fixes GoogleCalendar to includedelegatedToId check before triggering webhooks

2. Refactoring Changes (Code DRY Improvements)

• Extracts repeated delegation credential error webhook triggering logic into helper methods
• AddstriggerDelegationCredentialError() private method inOffice365CalendarService class
• AddstriggerDelegationCredentialError() helper function inTeamsVideoApiAdapter
• Replaces 4 instances of repeated code in each file with calls to the helper methods

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code
• N/A - No documentation changes required (internal refactoring and bug fix)
• I confirm automated tests are in place that prove my fix is effective or that my feature works

How should this be tested?

Testing the webhook fixes:

1. Set up a delegation credential for Office365 or Google Calendar
2. Configure a webhook subscriber forDELEGATION_CREDENTIAL_ERROR trigger at the organization level
3. Trigger a delegation credential error (e.g., invalid tenant ID, missing client credentials, or non-existent Azure user)
4. Verify the webhook is fired with the correct payload includingdelegationCredentialId andorganizationId

Testing the refactoring:

1. Run existing tests for Office365Calendar and Office365Video integrations
2. Verify delegation credential error scenarios still trigger webhooks correctly
3. Check that all 4 error scenarios in each file still work as expected

Human Review Checklist

Critical items to review:

1. Webhook Logic Change: Verify the change from passingorgId directly to looking up the delegation credential first is correct. Does this properly handle all edge cases?

2. New Repository Method: ReviewWebhookRepository.findByOrgIdAndTrigger() - is the query correct? Does it properly filter by organization and trigger event?

3. Payload Changes: The webhook payload now includesdelegationCredentialId andorganizationId. Is this a breaking change for existing webhook consumers? Should this be documented?

4. GoogleCalendar Fix: Verify the addition ofcredential.delegatedToId check in GoogleCalendar is correct and consistent with other integrations.

5. Refactoring Correctness: Verify the extracted helper methods maintain exactly the same behavior as the original repeated code. Check that:

   • All conditional checks are preserved
   • The webhook payload structure is identical
   • Error handling remains the same

6. Edge Cases: What happens ifdelegationCredential is not found in the database? The code returns early, but is this the correct behavior?

Session Info:

• Requested by:morgan@cal.com (@ThyMinimalDev)
• Devin session:https://app.devin.ai/sessions/445bdf27097648ab8eaf91d7cac2af57