post_inbox_apps_conversations_participants
Add a participant to an inbox app conversation using a Person, User, or Relationship ID, or contact details like name, email, or phone. Enables including new participants in existing conversations.
Instructions
Adds a participant to an Inbox App conversation. (POST /inboxApps/{inboxAppId}/conversations/{extConversationId}/participants)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"inboxAppId": "<inboxAppId>",
"extConversationId": "<extConversationId>"
},
"name": "post_inbox_apps_conversations_participants"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The participant's name if you do not know the participant's Person or User ID. | |
| No | The participant's email address if you do not know the participant's Person or User ID. | ||
| phone | No | The participant's phone number if you do not know the participant's Person or User ID. | |
| userId | No | A FUB User ID. Mutually exclusive to other fields. | |
| personId | No | A FUB Person ID. Mutually exclusive to other fields. | |
| extraBody | No | Extra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is. | |
| extraQuery | No | Extra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is. | |
| inboxAppId | Yes | ||
| isAutomation | No | Whether the participant is an automated system. Defaults to false. | |
| relationshipId | No | A FUB Relationship ID. Mutually exclusive to the other ID fields. | |
| extConversationId | Yes |