Start with the event contract
Name the event, the source record, and the destination action. Decide which fields are required, how an event is identified, and which person owns the resulting change. Avoid passing an entire contact record when the destination needs only a small subset.
Scope access to the task
Keep credentials outside browser code and separate integration ownership from campaign access. Request only the permissions a connection needs, rotate credentials securely, and provide a clear path for revocation.
Plan for delivery and retries
Webhook consumers need a way to recognize repeated events and recover from temporary failure. Agree on retry behavior, ordering assumptions, and the point at which a person must review the exception. The marketing demo-request API is not a public outreach integration API.
Define assistant permissions
Define explicit capabilities, access boundaries, and review points for MCP and conversational integrations. Keep external actions accountable to an owner. Use Get Demo to discuss your integration requirements and implementation details.