-
Notifications
You must be signed in to change notification settings - Fork 603
feat(webhook): add endUserEmail #5085
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| # 6. Re-authorize an existing connection | ||
|
|
||
| There are cases where you need to re-authorize a connection, e.g. credentials have expired or the scopes/permissions have changed. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Documentation]
Fix grammar: 'all it's associated data' should be 'all its associated data'.
Context for Agents
[**Documentation**]
Fix grammar: 'all it's associated data' should be 'all its associated data'.
File: docs/implementation-guides/api-auth/implement-api-auth.mdx
Line: 219| } | ||
| } | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Documentation]
Fix grammar: 'referred as' should be 'referred to as'.
Context for Agents
[**Documentation**]
Fix grammar: 'referred as' should be 'referred to as'.
File: docs/implementation-guides/platform/webhooks-from-nango.mdx
Line: 233|
|
||
| In some cases, a connection belongs to an organization rather than a user. In such cases, fill in the relevant organization information and use a place holder for the required `end_user.id` (or use the information of the user who initiated the authorization flow). | ||
| </Info> | ||
| In some cases, a connection belongs to an organization rather than a user. In such cases, fill in the relevant organization information and use a place holder for the required `end_user.id` (or use the information of the user who initiated the authorization flow). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Documentation]
Fix spelling: 'place holder' should be 'placeholder'.
Context for Agents
[**Documentation**]
Fix spelling: 'place holder' should be 'placeholder'.
File: docs/getting-started/quickstart/embed-in-your-app.mdx
Line: 88
Expose
endUserEmailin auth webhook payloadsThis PR expands auth webhook payloads to include the optional
endUserEmail, wiring the value throughsendAuthand updating the sharedNangoAuthWebhookBodyBasetype definition. Documentation across webhook, API auth, and quickstart guides now calls out the email field so integrators know to persist it alongsideendUserId.Key Changes
• Populate
endUserEmailin theendUserobject built bysendAuthinpackages/webhooks/lib/auth.ts• Extend
NangoAuthWebhookBodyBaseinpackages/types/lib/webhooks/api.tsto type the optionalendUserEmailfield• Refresh webhook/API auth/quickstart documentation to show the new
endUserEmailproperty and tidy markdown spacingAffected Areas
•
packages/webhooks/lib/auth.ts•
packages/types/lib/webhooks/api.ts•
docs/implementation-guides/platform/webhooks-from-nango.mdx•
docs/implementation-guides/api-auth/implement-api-auth.mdx•
docs/getting-started/quickstart/embed-in-your-app.mdxThis summary was automatically generated by @propel-code-bot