Enabling Integrations

Here you’ll find setup guides for enabling integrations and operating Nected in your own infrastructure.

If you're using Nected Cloud (SaaS), you can connect integrations in the Nected UI without these steps. See the main Integrations documentation for cloud setup.

These guides assume you already have Nected deployed via Helm and have access to nected-values.yaml and your Kubernetes cluster (kubectl, Helm).

---

Integrations

The following guides explain how to enable and configure third-party integrations in your on-premise Nected instance. Each integration typically involves:

• Creating and configuring an app in the provider’s developer console (OAuth, API keys, scopes)

• Updating CREDENTIAL_CONFIG_MAP and SYNC_PLUGINS in nected-values.yaml

• Running Helm upgrade and, when needed, restarting or syncing Nalanda

Common Configuration Keys

When adding or changing integrations, you’ll often use these in nected-values.yaml:

• CREDENTIAL_CONFIG_MAP — OAuth client IDs, secrets, and provider-specific settings for each integration.

• SYNC_PLUGINS — Comma-separated list of plugin names (e.g. mysql, gsheet, slack). The Nalanda service uses this to expose integrations in the Nected UI.

After editing values, run:

helm repo update
helm upgrade -i nected nected/nected -f nected-values.yaml

If the Nalanda deployment doesn’t pick up new plugins, restart it and optionally sync plugins from inside the pod:

kubectl rollout restart deploy nected-nalanda
# If the integration still doesn’t appear under Integrations:
kubectl exec -it <nalanda-pod-name> -- /bin/bash
./nalanda sync plugin