Zintara integration capability matrix: supported paths and explicit gaps

Define the decision

This matrix describes the reviewed local implementation on September 16, 2026. It is a contract-reading aid, not a promise that a particular deployed account has every option configured or enabled.

Work through the procedure

1. Choose the surface that matches the required action.
2. Confirm account configuration and permissions.
3. Test the actual payload or export with synthetic data.
4. Document any missing field, event or recovery guarantee before production use.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

API keys: workspace-bound lead, campaign and analytics scope families
General webhooks: reply.received and bounce.detected; best-effort
Slack: reply, bounce, unsubscribe, campaign_paused, import_completed alerts
CSV export: eight descriptive lead columns
Not promised: complete event replay, native CRM two-way sync or arbitrary mailbox-folder import

Read the result

These surfaces overlap in purpose but are not interchangeable. A Slack unsubscribe alert does not create a general webhook event, and a CSV export does not provide a live synchronization guarantee.

Check before moving on

1. Check route-specific request and response shapes.
2. Keep a dated capability record for the integration owner.

Limits and next action

Review the actual deployed version before relying on this matrix. Missing functionality should remain a visible requirement rather than being filled with guessed endpoints or fields.

Source: Zintara implementation and product context