Guide · Integrations

Connect accounts without passing tokens around.

Ekvaar supports direct adapters for core services and organisation-scoped connections through Composio. The exact connection method depends on the provider.

Choose the connection path

OAuth is preferred for user-facing services because the provider shows the account and permissions being granted. API keys are appropriate for infrastructure or model providers when the organisation owns the key. Workflow endpoints are used when n8n receives a controlled trigger from Ekvaar.

Connect an OAuth app

Open Integrations

Choose the service and select Connect. The page should identify the organisation making the connection.

Verify provider setup

If the workspace uses Composio, add the organisation’s Composio API key in Settings and verify the provider’s auth configuration exists.

Complete provider consent

Review the account name and requested scopes on the provider screen. Finish the consent flow only for the intended account.

Verify the connected identity

Return to Ekvaar and confirm the connection shows Live with the correct account or page name. Do not infer identity from a generic “connected” state.

Connect a provider key

Go to Settings → AI Providers → Add new key. Select the provider, add the key, save and test it. Ekvaar should display only the models returned by connected providers when configuring a route.

Keys stay server-side

The UI should never read the stored secret back. Status endpoints expose connection state, not the secret value.

Connect n8n

Use the internal n8n service URL for server-to-server health checks and a production webhook URL for controlled triggers. The workflow must return JSON, include a stable run identifier and write important outputs back to the Ekvaar task or approval record.

Avoid HTML-as-JSON failures

If a trigger reports “Unexpected token <”, the request reached an HTML page rather than the JSON webhook endpoint. Verify the production webhook URL, activation state, authentication and response node.