ZuckerBot › Tool reference › Conversion tracking (CAPI)
zuckerbot_set_capi_config
| Name | Type | Description | |
|---|---|---|---|
business_id | string | optional | Optional business ID override for the authenticated API key |
is_enabled | boolean | optional | Enable or disable CAPI delivery for the business |
currency | string | optional | Business currency used for CAPI event values, such as USD or AUD |
crm_source | string | optional | CRM source label, such as hubspot |
optimise_for | "lead" | "sql" | "customer" | optional | Downstream optimisation target for autonomous evaluation |
action_source | "website" | "app" | "email" | "phone_call" | "chat" | "physical_store" | "system_generated" | "business_messaging" | "other" | optional | Meta Conversions API action_source. Defaults to website for CRM events |
rotate_webhook_secret | boolean | optional | Rotate the webhook secret on update. The new secret is returned exactly once in the response; prefer zuckerbot_rotate_webhook_secret for a dedicated rotation |
event_mapping | object | optional | CRM stage mapping object keyed by source stage. Stage keys are normalised (lower-cased, non-alphanumerics stripped: signup_completed → signupcompleted); inbound webhook source_stage values are normalised identically before matching, and any renamed keys are reported back as normalised_keys in the response |
{
"tool": "zuckerbot_set_capi_config",
"arguments": {}
}
You never invoke this directly — describe what you want in plain English inside Claude, Cursor, ChatGPT or any MCP client with ZuckerBot connected, and the agent selects zuckerbot_set_capi_config and fills the arguments for you.