Launch integration evidence review
Provider proof required before promotion. Connection evidence reviewed before customer use across provider, credential, consent, delivery, removal, and support-owner scope.
Launch-Scoped Connections
Email Provider Evidence
Review outbound email provider proof before launch promotion.
- Provider evidence reviewed before promotion
- Connection evidence reviewed before customer use
- Compliance metadata and unsubscribe checks required for campaigns
- Launch availability depends on the email evidence packet
Messaging Provider Evidence
Review SMS and messaging consent proof before customer promotion.
- Workspace-level sender proof reviewed before enablement
- Connection evidence reviewed before customer use
- Consent and A2P evidence required before broad use
Developer Surfaces
Webhook Evidence
Review signed delivery proof before event delivery is promoted.
- Event-delivery scope reviewed for approved CRM changes
- HMAC signing and retry behavior must be proven before launch
- Delivery evidence is tracked in the launch packet
API Scope Evidence
Review server-to-server access scope before customer promotion.
- Workspace access proof reviewed before enablement
- Rate limits and permissions documented per launch scope
- External developer platform claims stay deferred until proven
Assisted Launch Workflows
File Imports
Assisted imports for controlled onboarding projects.
- CSV import validation for scoped objects
- Dry-run and rollback evidence required for migrations
- Customer cutover remains assisted until proven end to end
Credential and Removal Review
Each retained connection must pass launch evidence review.
- Credential handling and removal proof documented
- Data flow and support owner identified before promotion
- Unproven vendor connectors stay on the roadmap
Provider Roadmap
New provider connections are promoted only after credential, sync, disconnect, support, and privacy evidence is complete.
Planned connection families:
- →CRM event export for downstream systems
- →Approved email-provider delivery proof
- →Accounting and finance connector review
- →Calendar and meeting capture review
Trigger Evidence Review
- CRM record-change export proof
- Revenue milestone evidence packet
- Contact lifecycle evidence
- Activity timeline audit sample
- Pipeline state-change proof
Action Evidence Review
- Downstream record write proof
- Field mapping review
- Notification delivery evidence
- Activity creation evidence
- Sequencing scope review
API Scope Review
Scope what needs proof
API Keys
- Scoped API evidence for approved server integrations
- Webhook delivery proof before launch promotion
- Rate limits documented per launch plan
- Developer surface notes limited to proven scope
Webhooks
Event delivery remains proof-gated until signing, retry, support ownership, and customer data-flow evidence are reviewed.
Webhook proof packet
{
"eventScope": "approved-crm-change",
"deliveryEvidence": "required-before-promotion"
}Enterprise Custom Integrations
Enterprise integration work is scoped through sales and promoted only after implementation and launch evidence are complete.
Contact SalesFrequently Asked Questions
Don't See What You Need?
Tell us which workflow needs evidence review before launch promotion.
Request IntegrationConfirm Your Launch Integration Scope
Talk with us about the connections you need and which ones are available, beta-scoped, or planned.