Import 1–100 comments into a comment thread, appended in array order.

Note: This API requires additional fund configuration to be enabled. Please contact us if you would like to try it out.

Posting is addressed by fund + thread together: obtain a threadId from ListCommentThreads (existing conversations) or CreateOrGetCommentThread (the order's general thread, created on demand), and pass it with the fund it belongs to — a threadId outside the fund is a 404. The comments are authored by the service account; onBehalfOf is display attribution only.

Mentions. body is plain text with mention tokens: @[[email protected]] mentions a fund member by email, @[team:TEAM-ID] mentions a GP team (expanded to its members). Any @[…] in the body is treated as a mention token, so if you need the literal characters @[ in your text, escape them as @\[. A token that does not resolve to a thread-visible member (unknown email, a non-member, a user outside the thread's visibility tier, an unknown team) is kept as literal text — the request is never rejected for an unresolvable mention, and no mention or notification is recorded for it.

Notifications. notifyMode (default none) controls whether an import notifies the thread's audience. none is fully silent — no in-app notifications and no emails — recommended for historical migrations so a bulk backfill never storms members. inApp records the in-app unread rows (the thread lights for its thread-visible members) but sends no email digest. all sends both in-app and email. Mentions in the body are always parsed and stored, but a mentioned member is notified only when notifyMode is inApp or all.

Retries. Comment ids are system-generated: the response's commentIds (in input order) are the only handle on what was stored. Import is not idempotent — re-sending a request (or an already-imported comment) appends new comments rather than overwriting, so a blind retry after an ambiguous failure can duplicate. Before retrying, read the thread back (ListThreadComments) or correlate via your own externalRefs to remove the comments that already landed.

Imported metadata. The request has no createdAt field — an imported comment's createdAt is server-assigned at import time (in array order) and read back in (createdAt, commentId) order. Imported comments carry an importedMetadata object on export. It echoes onBehalfOf and externalRef verbatim when they were supplied; each field is absent otherwise. The presence of importedMetadata is what marks a comment as imported. externalRef is an optional correlation tag for your own systems — not a de-duplication key; it is echoed back on export but never affects storage.

Limits. 1–100 comments per request; each comment at most 10,000 characters in stored form; at most 200 comments per thread. The service account needs permission to post comments at the thread's visibility tier (403 otherwise); an unknown or foreign threadId is 404.