Campaign Operations Through MCP
In this edition
Campaign Operations Through MCP
- Connected AI clients can log outreach touchpoints with campaign_interaction_create, enroll contacts, companies or accounts with campaign_member_create, and update member stages, next actions and recheck dates with campaign_member_update.
- These operations write directly with contacts:write permission. Enrollment protects against duplicates, checks target eligibility and derives member status from the campaign stage when no status is supplied.
- Read chronological campaign touchpoints with campaign_interaction_list, using pagination to continue through results. Reading requires product_context:read.
- Invalid inputs, missing records, permission failures and conflicts return distinct errors. Temporary service failures are marked retryable.
- The database contracts were verified on staging. The app database contracts must be deployed before the corresponding MCP server update; end-to-end production availability has not been verified.
Link Action Icons
- Link and associate actions in Campaign, Story and source details use chain icons, distinguishing them from actions that create a new item.