Integration Hub

Manage credentials and connection status for all external services — Gmail, Slack, databases, and more.

Overview

Integration Hub is the central credential store for TotalApp. Every external service that a workflow node connects to (email providers, Slack workspaces, databases, cloud storage, third-party APIs) has its credentials stored here. Nodes reference a named integration rather than embedding credentials directly in the workflow — this means rotating an API key requires only one update in the Hub, not hunting through every workflow.

Coming Soon

Integration Hub is currently in development. The UI is visible in the Automation mode sidebar but integration management is not yet active.

Planned Features

Integration cards — each connected service shows as a card with its logo, connection status (connected / disconnected / error), and the date credentials were last verified.
OAuth2 integrations — for services that support OAuth (Gmail, Slack, Google Sheets), TotalApp handles the OAuth flow. You authorise once; the Hub stores and refreshes the token automatically.
API key integrations — for services that use API keys (OpenAI, Stripe, Shopify), paste the key once. The Hub encrypts it at rest.
Connection test — a one-click test that makes a lightweight API call to verify the stored credentials are still valid.
Usage tracking — see which workflows reference each integration so you know the blast radius before rotating a credential.
Shared vs. personal — integrations can be marked as shared (available to all users) or personal (only visible to the user who added them).

Frequently Asked Questions

Is Integration Hub available to use right now?

Not yet. Integration Hub is visible in the Automation mode sidebar, but credential management is still in development. Workflow nodes that need external service credentials (email, Slack, databases) currently store connection details on the node itself; the Hub will centralize this in a future release.

How will credentials be secured once Integration Hub ships?

API key integrations will be encrypted at rest, and OAuth2 integrations (Gmail, Slack, Google Sheets) will store only the refresh token issued by the provider, never a plaintext password. Credentials will never be exposed in workflow JSON exports or shared publicly between tenants.

What is the difference between a shared and a personal integration?

A shared integration is available to every user in the tenant — useful for a company-wide Slack workspace or shared database. A personal integration is visible only to the user who connected it, which is appropriate for individual Gmail accounts or personal API keys that should not be reused by teammates.

Will rotating an API key break my existing workflows?

No — that is the core purpose of Integration Hub. Because workflow nodes reference a named integration instead of embedding the credential directly, updating the key once in the Hub propagates to every workflow that uses it. The planned Usage Tracking feature will also show you exactly which workflows depend on an integration before you rotate its credentials.