Connection lifecycle
- Not connected: no provider authority exists.
- Setup required: intent or credentials may exist, but required provider steps are incomplete.
- Connected: the provider authenticated, but a capability can still require scope or setup.
- Active: required permissions and health checks passed for the stated capability.
- Needs attention: token, permission, account, webhook, location, or provider state requires action.
- Disconnected: provider-backed actions are blocked and affected workflows are evaluated before removal.
What integrations can support
- Google and Outlook calendars for external busy events and appointment synchronization.
- Stripe for subscription billing and connected-business customer payments.
- Telephony and messaging providers for voice, SMS, SIP, call control, recordings, and delivery states.
- WhatsApp, Instagram, Facebook, email, review, accounting, and other supported business systems.
- API and webhook access on eligible plans.
Disconnect protection
Before disconnecting a provider, NevoDesk checks whether an active workflow would lose its last capable provider. If so, the account must repair the workflow, connect an equivalent provider, or explicitly resolve the impact before the disconnect can complete.
This article is part of the same maintained knowledge corpus used by NevoGuide. Live provider evidence and saved workspace configuration remain authoritative for your account’s current operational state.