Create or update a contact
upsert_contactCreate a contact by email or update an existing record, merging supplied fields so you can change one property without knowing the rest. This does not subscribe or send messages.
Instructions
Purpose: create a contact, or update the one with that address. Properties are merged, so you can set one field without knowing the rest. NOT for: subscribing anyone to anything, or sending. Adding a contact sends nothing. Returns: the contact as it now stands, including consent if it was given.
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": {
"email": "<email>"
},
"name": "upsert_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The contact's address; the identity of the record. | ||
| consent | No | Optional consent provenance for this address. Stored, shown and exported; never a reason this call is refused. | |
| properties | No | Fields to merge in, e.g. { "first_name": "Ada" }. Each value is a string, number, boolean, ISO date or list of strings; a property keeps the type it was first written with. | |
| audience_id | No | Add the contact to this audience. The id is a segment on this account. A value that is not an audience id saves the contact and adds nothing. | |
| idempotency_key | No | Your own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Identifier. | |
| No | |||
| error | No | Present instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds. |