> For the complete documentation index, see [llms.txt](https://docs.emobiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emobiq.com/emobiq-ai/readme/supabase/integrating-emobiq-ai-with-supabase.md).

# Integrating eMOBIQ AI with Supabase

## The Integration Flow: Seamless, Smart, and Safe

eMOBIQ AI doesn't just connect to Supabase, it **orchestrates** your entire backend workflow with built-in safeguards

{% stepper %}
{% step %}

#### Linking Supabase

To use Supabase with your eMOBIQ project, simply click `Configure` under the `Advanced Tab`

<figure><img src="/files/KzgcaGPynj3xqOAKqnC6" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Connect to Supabase

Click on `Connect to Supabase`

<figure><img src="/files/Xt0m97A5fdbw3NZvFgze" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Authorise eMOBIQ AI

* Log in to your Supabase account. If you don't have one, simply register for an account to get started
* Select the **Organization** you want to grant API access to
* Authorize eMOBIQ by confirming the permissions

<figure><img src="/files/LNbGmFOFV4oaAjBBmpY9" alt="" width="325"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Select or Create a Project

Select the project you would like eMOBIQ AI to create the database on

If you haven't created a project yet, you can click `Create New Project` directly from the eMOBIQ AI platform

<figure><img src="/files/X1ZoL6N5cPJlYsEGEACz" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/DnPOIVSexWeu4a9kSUi7" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## Pro Tips for Success

#### Let eMOBIQ AI know which backend to use

In your app ideation phase, be sure to let eMOBIQ AI know you want to use Supabase as the backend database. This is to help ensure that the backend is confirmed and eMOBIQ AI is clear on what backend you want to use.

<figure><img src="/files/PAehYXp6RBCcLHOjp9re" alt=""><figcaption></figcaption></figure>

#### Selecting Manual Review (Recommended)

While not compulsory, we **highly recommend** selecting the `Manual Review` option over Autopilot.

<figure><img src="/files/PgQ4Z3QVluKOmoy5OdqX" alt=""><figcaption></figcaption></figure>

**Why?**

* In the Tech Lead stage, you'll receive prompts to review database schemas
* You can approve or reject each schema based on your specific requirements
* Each SQL query will create tables on Supabase based on what you approve or modify
* This gives you full control and ensures the database structure matches your needs

<figure><img src="/files/R5ReXjvtBHF8bfMVt8DK" alt=""><figcaption></figcaption></figure>

***

### Summary

By following these steps and best practices, you'll have a fully integrated Supabase backend that's tailored to your application's needs — with the safety and control of manual review every step of the way.


---

# 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.emobiq.com/emobiq-ai/readme/supabase/integrating-emobiq-ai-with-supabase.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.