Apps
Manage workspace-scoped platform credentials, capabilities, configuration, and app lifecycle.
Last reviewed July 13, 2026
Apps are workspace-scoped platform connections. A single app can supply source, destination, or other capabilities to more than one integration.
Open Data → Integrations → Apps.
What an App Owns
- the platform type and display name;
- OAuth or credential configuration;
- granted capability permissions;
- provider account metadata where available;
- lifecycle state;
- the source and destination integrations that refer to it.
AI provider configuration is managed separately under Workspace Settings → AI Models.
Add an App
- Select Add App.
- Choose a platform from the current runtime catalog.
- Review the capabilities and permissions in scope.
- Complete OAuth or enter the required credentials.
- Select the provider account when the platform exposes more than one.
- Validate and save the connection.
Saving an app does not automatically create every possible data flow. Configure the required source or destination integration afterward.
Draft and Active State
An incomplete app can remain a draft and return to the add-app flow. An active app appears in the Apps table with its capabilities. Provider validity and integration health must still be checked from the app detail and related jobs; the word Active is not proof that a recent sync succeeded.
Update Credentials
Open the app and use the provided reauthorization or credential-edit path. After any update:
- validate the connection;
- run a narrow source or destination test;
- inspect Activity Logs;
- verify the provider-side result.
Do not assume paused or failed integrations resume solely because credentials were saved.
Delete Safely
Before deleting an app, identify every source, destination, model, automation, and schedule that depends on it. Confirm the intended data-retention behavior for each related source. Delete only after those consumers are removed or migrated.