add invitation accepted, revoked events

[stacurry]

Description

Adds support for invitation.accepted and invitation.revoked events

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

[linear]

AUTH-5069 Support new invitation events in Node SDK

[greptile-apps]

Greptile Summary

This PR adds support for two new invitation-related webhook events: invitation.accepted and invitation.revoked. The changes extend the existing event handling system in the WorkOS Node.js SDK to properly handle the complete invitation lifecycle.

The implementation follows the established patterns in the codebase:

1. Interface definitions: New TypeScript interfaces are added to event.interface.ts for both events, including both regular Event and EventResponse variants (InvitationAcceptedEvent, InvitationRevokedEvent, InvitationAcceptedEventResponse, InvitationRevokedEventResponse)

2. Event serialization: The event serializer is updated to handle these new event types by extending the existing switch case that already handles invitation.created events

3. Type safety: The new interfaces are properly added to the Event and EventResponse union types, ensuring TypeScript can correctly discriminate between different event types

Both new events reuse the existing deserializeInvitationEvent function since they share the same data structure as the invitation.created event. This makes sense because all invitation events contain the same invitation object with fields like state, acceptedAt, and revokedAt - the event type indicates what triggered the webhook, while the invitation's state field reflects the current status.

This change enables applications using the WorkOS SDK to listen for and respond to all stages of the invitation process, not just creation. The implementation maintains consistency with other event types in the SDK and follows the established webhook event patterns.

Confidence score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects simple, well-structured changes following established patterns with proper type safety
• No files require special attention

_{2 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}