> 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/platform-resources/logic-and-external-api-integration.md).

# Logic & External API Integration

For complex, multi-system automation, Uptiq moves beyond basic API calls. This section documents the officially supported connectors that enable your Agents to seamlessly integrate with external services, databases, and enterprise control points (Management Control Points, or MCPs).

These connectors are crucial for both Workflow I (App-First) and Workflow II (Agent-First) scenarios where data persistence and system interaction are required.

## Supported External Integrations

Uptiq leverages structured protocols to enable intelligent interaction with external tools, allowing Agents to use real-world context and data from your connected systems.

| **Connector**                        | **Purpose**                   | **Uptiq Workflow Use Case**                                                                                                                                                                |
| ------------------------------------ | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Supabase                             | Serverless Backend & Database | Connects the App Builder output to a scalable, dedicated PostgreSQL database and backend. Used for permanent data persistence and external authentication.                                 |
| GitHub                               | Source Control & DevOps       | Provides secure Code Access & Git Integration. Allows Agents to read documentation (context) and perform actions like committing generated code or updating ticket statuses (Workflow II). |
| MCP Servers (Model Context Protocol) | Agentic Control Point         | Enables Multi-Agent Orchestration and deep collaboration across complex enterprise systems. Used for connecting to private APIs, internal CRMs, and custom data sources.                   |

## Mechanism: API Call Skill vs. Connectors

The core API Call Skill provides generic HTTP communication, requiring manual setup of endpoint URLs, headers, and authentication.

In contrast, Enterprise Connectors (like the three listed above) utilize a dedicated, pre-configured framework. This framework manages authentication schemas (OAuth, Bearer Token) and endpoint protocols, ensuring secure, compliant, and reliable integration tailored for enterprise use.

{% hint style="info" %}
**Key Advantage**: Using connectors ensures that the Agent can not only execute an API call (like the generic Skill) but can also read and write structured data within external tools (like updating a GitHub issue or pulling data from Supabase), ensuring the automation remains grounded in real-time context.
{% endhint %}

<br>


---

# 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/platform-resources/logic-and-external-api-integration.md?ask=<question>&goal=<endgoal>
```

`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.