Send Recap External
Mail the confirmed write-up to the EXTERNAL attendees — the rep’s explicit choice, never automatic (2026-08-12 decision).
The automatic send on confirm covers the team only; this button is how a customer ever sees the recap. Inline rather than a background task, deliberately: the rep pressed a button that mails their customer, and “sent to 3, one address failed” is the answer they are owed before the dialog closes. The activity self-gates (setting, confirmation, usable analysis, at-most-once external claim), so a double-press or a stale tab re-posting costs nothing.
View access is the same rule as the detail page (N5): no oversight means only meetings the caller may open — and a refusal is the same 404 the detail route answers, because a 403 would confirm the id exists.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
The response is of type Response Send Recap External Meetings Meeting Id Recap Send External Post · object.