Update integration
update_integrationRename, pause or resume (status), or change an integration's settings or credentials (left-out credentials keep the stored ones). eventTriggers (Mixpanel) maps Mixpanel events to TextKit events; exportEvents: false stops sending text events to Mixpanel (on by default); changing only those does not re-test credentials or resync.
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": {
"id": "<id>"
},
"name": "update_integration"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Integration id | |
| name | No | What to call it | |
| apiKey | No | Amplitude API key | |
| secret | No | Mixpanel service account secret | |
| status | No | active, or paused to stop syncing | |
| sourceId | No | Mixpanel or Amplitude cohort id; HubSpot list id; Salesforce campaign id; a Shopify customer search | |
| username | No | Mixpanel service account username | |
| secretKey | No | Amplitude secret key | |
| phoneEvent | No | Mixpanel: an event that carries the number when profiles do not | |
| phoneField | No | The tool's property holding the mobile number | |
| accessToken | No | HubSpot private app token, or Shopify Admin API access token | |
| consentEvent | No | Mixpanel / Amplitude: the opt-in event the cohort is built on | |
| consentField | No | The tool's property that records SMS consent | |
| exportEvents | No | Mixpanel (with a service account): send each text's events onto the person's Mixpanel profile: TextKit Message Sent, Delivered, Failed, Link Clicked, Reply Received and Opted Out, with the message, batch or automation and step ids and names. The person is matched by the batch recipient's external_id, the user id or mixpanel_distinct_id of the event that started the automation, or the contact Mixpanel supplied. On unless false. Needs a service account Mixpanel lets import (Admin or Owner on the project). | |
| eventTriggers | No | Mixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel events that count as it, like { event: "purchase_completed", mixpanel_events: ["Purchase Completed", "Web Trial Successful"] }. Only events from people in the integration's list become events, matched by their Mixpanel id. [] clears them. Changing only these keeps the credentials and the sync schedule as they are (no re-test, no resync). The answer's `warnings` names mapped events that fired 0 times in the last 7 days. | |
| phoneEventProperty | No | Mixpanel: that event's property holding the number (default phone) |