For the complete documentation index, see llms.txt. This page is also available as Markdown.
Connect an integration
Connect a third-party service to your workspace from Integrations.
Connect your workspace to third-party services from Integrations.
This guide covers finding an integration, adding a connection, and confirming it is ready. Connected integrations are reusable across apps and agents.
Prerequisites
You need access to a Qore workspace and Integrations.
You also need service credentials. These may be an API key, OAuth login, or core-banking credentials.
Connect methods
Each integration uses one of three connect methods:
Connect BYOK (Bring Your Own Key) — you supply your own API key or OAuth credentials. Best for services you already have an account with (e.g., OpenAI, Salesforce, Stripe).
Connect via UDG (Uptiq Data Gateway) — you authenticate through Uptiq's managed gateway. Best for partner-managed services.
MCP Sandbox Account — connects to core banking / accountancy systems through the Kinective network (cards marked Powered by K).
Steps
1
Open Integrations
Select Integrations in the left navigation. The catalog lists 200+ integrations. Use the search box, the category chips (All, Storage, Authentication, LLM, Payments, CRM, Accountancy, Banking, Messaging, …), or the status filter to find a service.
The Integrations catalog, with search, category chips, and integration cards
2
Select the integration
On the integration's card, click + Connect (visible directly on the card). This opens the integration's detail page, showing its status (e.g., Not Connected), an Overview, and an All Connections table.
The integration detail page, showing status, Overview, and the All Connections table
3
Add a connection
Click + Add Connection. In the Manage {Service} dialog, enter a Connection Name and the service-specific details:
LLMs (e.g., OpenAI): choose a Model (and provide your API key where prompted).
OAuth services: click to authorize through the provider's consent screen.
Token / token + webhook services: paste your API key (and webhook secret).
Then click Save.
The Manage {Service} dialog, with Connection Name, service fields, and Save
Credentials are encrypted at rest and masked as ****** on read. For OAuth, tokens are refreshed automatically.
Verify
The connection appears in the integration's All Connections table with a connected status.
The integration is now available to your apps and agents.
Common issues
Not sure which method to use. Core-banking cards show Powered by K (MCP Sandbox / Kinective); most SaaS use BYOK or UDG.
OAuth won't complete. Re-run the connect step and finish the provider consent screen; ensure pop-ups aren't blocked.
The service I need isn't in the catalog. For any REST API without a pre-built connector, use the API Call Skill.
