chat.add_participantsAdd eligible accounts or email recipients to this group under the applicable reviewed approval contract. Requires all current participant IDs as expected_participant_ids. Accounts gain history access; email recipients receive future messages.
- Operation
- write
- OAuth scopes
- mcp
Availability depends on your assigned tools. Scopes do not grant record access. Read the tool description and current resource before changing it; follow the required revision and idempotency fields below.
Client portal inputs
| Name and description | Required |
|---|---|
conversation_idConversation slug returned in the id field by chat.list. Copy it exactly; do not use the group name or a database ID. | Yes |
expected_participant_idsSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
organization_slugSee the input schema for constraints. | Yes |
participant_emailsSee the input schema for constraints. | Yes |
provider_slugSee the input schema for constraints. | Yes |
user_confirmedSee the input schema for constraints. | Yes |
View exact input schema
Provider portal inputs
| Name and description | Required |
|---|---|
conversation_idConversation slug returned in the id field by chat.list. Copy it exactly; do not use the group name or a database ID. | Yes |
expected_participant_idsSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
participant_emailsSee the input schema for constraints. | Yes |
provider_slugCopy the provider slug from providers.list or your client workspace. | Yes |
user_confirmedSee the input schema for constraints. | Yes |
View exact input schema
Result
Check the structured result for success or an error before continuing. Read the affected record to confirm your change.
View exact output schema
For this workflow’s steps and prerequisites, read the Chat and messages guide.
