> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/integrations/integrations-hub/connect-methods.md). # Connect Methods Use this page with [Integrations Hub](/integrations/integrations-hub.md). Browse categories: * [AI and Utilities](/integrations/integrations-hub/ai-and-utilities.md) * [Banking and Finance](/integrations/integrations-hub/banking-and-finance.md) * [Compliance and Analytics](/integrations/integrations-hub/compliance-and-analytics.md) * [CRM and Marketing](/integrations/integrations-hub/crm-and-marketing.md) * [Productivity and Collaboration](/integrations/integrations-hub/productivity-and-collaboration.md) ### Connect BYOK (Bring Your Own Key) **Used by:** Platform-native integrations (Anthropic, OpenAI, Salesforce, HubSpot, Stripe, Google Workspace, Microsoft 365, AWS S3, and others) Bring Your Own Key means you supply your own credentials directly — an API key, OAuth client ID/secret, or webhook signing secret. The platform stores your credentials encrypted and uses them at runtime. #### When to use Use Connect BYOK when you have a direct account with the service provider and want full control over the credentials and API access. #### How it works 1. Navigate to the Integration Hub in your workspace. 2. Find the integration in the catalog and select it. 3. Enter your credentials: * **Token-based integrations** (e.g., Anthropic, OpenAI): Paste your API key. * **OAuth integrations** (e.g., Salesforce, Google Workspace): Click "Connect" to start the OAuth authorization flow. The platform redirects you to the provider's consent screen, then stores the access and refresh tokens. * **Token + Webhook integrations** (e.g., Stripe): Enter your API key and webhook signing secret. 4. The platform validates and encrypts your credentials. 5. The integration is now available to Agents, Skills, and Apps in your workspace. #### Credential security * Credentials are encrypted before storage. Fields marked as credential fields are never stored in plaintext. * When you view a configured integration, credential values display as `******`. * You can update or revoke credentials at any time. * For OAuth integrations, the platform automatically handles token refresh. #### Per-user credentials Some BYOK integrations support per-user credential configuration. This allows individual workspace members to use their own API keys or OAuth connections instead of (or in addition to) shared workspace-level credentials. *** ### Connect via UDG (Uptiq Data Gateway) **Used by:** Partner-managed integrations across CRM, commerce, customer support, compliance, analytics, and more (ActiveCampaign, Pipedrive, Shopify, DocuSign, ServiceNow, Zendesk, and others) The Uptiq Data Gateway is a managed integration layer that brokers connections to partner services. UDG handles the connection infrastructure, so you authenticate through UDG rather than directly with the provider. #### When to use Use Connect via UDG when the integration is delivered through Uptiq's partner network. These integrations are pre-configured for compatibility with the Uptiq platform. #### How it works 1. Navigate to the Integration Hub in your workspace. 2. Find the UDG-powered integration in the catalog. 3. Follow the UDG connection flow to authenticate with the provider through the managed gateway. 4. Once connected, the integration is available to Agents, Skills, and Apps. #### What UDG manages * Connection infrastructure and authentication brokering * API compatibility and version management * Provider-specific configuration and defaults *** ### MCP Sandbox Account **Used by:** Banking core system integrations powered by Kinective (Fiserv DNA, Fiserv Premier, FIS Horizon, Jack Henry Symitar, and 13 other core banking platforms), plus accountancy integrations (QuickBooks, Xero, FreshBooks, FreeAgent, Wave) MCP Sandbox Account integrations connect through the Kinective partner network to core banking systems and financial platforms. These integrations use the Model Context Protocol (MCP) to expose banking operations as agent-callable tools. #### When to use Use MCP Sandbox Account when connecting to a core banking system or supported financial platform. These integrations are designed for financial institutions that need to connect their AI agents to their core banking infrastructure. #### How it works 1. Navigate to the Integration in your workspace. 2. Find the banking core or accountancy integration in the catalog. 3. Configure the MCP sandbox connection with your institution's core banking credentials. 4. The integration exposes banking operations (account lookup, transaction history, loan processing, etc.) as MCP tools that agents can call during conversations. #### Supported core banking systems The following core banking platforms are available through MCP Sandbox Account: * **Fiserv:** DNA, Portico, Precision, Premier, Signature, Spectrum, XP2 * **FIS:** Bankway, Horizon, IBS, Miser * **Jack Henry:** CIF 20/20, Core Director, Silverlake, Symitar, Symitar EASE * **Other:** COCC (DNA) - Insight, Corelation - Keystone, CSI - NuPoint, Finastra - Phoenix *** ### Choosing the Right Connect Method | Factor | Connect BYOK | Connect via UDG | MCP Sandbox Account | | ---------------------------------- | ------------------------- | ------------------------ | -------------------- | | **You control credentials** | Yes | Through UDG | Through Kinective | | **Direct provider account needed** | Yes | No | Varies | | **Best for** | Services you already use | Partner-managed services | Core banking systems | | **Available integrations** | \~30 | \~100 | \~20 | | **OAuth support** | Yes (managed by platform) | Yes (managed by UDG) | N/A | | **MCP tool exposure** | Some | Some | All | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.uptiq.ai/integrations/integrations-hub/connect-methods.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.