Connectors

A connector links your Buildliy account to another service, such as Resend for email, Twilio for text messages or Airtable for spreadsheets. You connect a service once. After that you can ask the AI to use it in any of your apps, and those apps call the service from their own server, so your key never reaches your visitors' browsers.

There are more than 100 connectors, grouped by category. If the service you need isn't listed, you can add it yourself. See Connect any API.

What a connection unlocks

Open a connector and look under What this unlocks. Depending on the service, a connection gives you one or both of these:

• Your app can use it. The apps you build can call the service from their server code, for example to send an email, look up a product or post a message.
• The AI can read it while building. The AI can look at your real data in that service (read only) so the pages it builds match your actual fields and content. See The AI reads your real data below.

Where to manage connectors

On the Connectors page you can search, pick a category (All, Connected, Popular and one entry per category), or use the brand filters, such as Google or AWS, above the cards. A card shows Connected once a service is set up.

Connect a service

1. 1

   Open the service

   Click Connectors in the left sidebar, then click the service's card. The window that opens explains what the service does and what connecting it unlocks.

2. 2

   Enter your key

   Paste the key from that service's website. Some services need more than one value, such as a region or an account ID. Where do I find this? opens the service's own page that shows you where to get it.

3. 3

   Click Connect

   Buildliy checks the key with the service before it saves anything. The button shows Checking…, then you see a message such as "Resend connected — key checked." If the service rejects the key, nothing is saved and you see why. If the service couldn't be reached right then, the key is still saved and you're told it couldn't be checked yet.

Two cards work differently. Stripe is set up on the Payments page instead (Set up in Payments), see Take payments. Supabase is chosen per app in Manage → Backend, see Use your own backend.

When the AI needs a service

When a request needs a service from the catalog that isn't connected yet, the AI can show a Connect card in the chat for that service. The card says why it needs the service and that the connection is saved to your account, so your other apps can use it too.

When someone books a class, email them a confirmation with the date and time. Use Resend.

• Connect with the service's name (for example Connect Resend) opens the same connect window as the Connectors page. Once the service is connected, the AI picks the build back up and uses it.
• Continue with the service's name appears instead when you've already connected it but it isn't on for this app yet. Clicking it switches the connection on for this app and carries on.
• Skip for now closes the card without connecting anything. The AI replies that you can connect the service any time from the Connectors page, and waits for your next message.

If the service isn't in the catalog, the AI asks for its key with a secure key card instead. See Connect any API.

If your app is shared with teammates, the card also asks you to tick a box confirming that everyone who can build there could use your connection, before it's turned on for that app. In a teammate's view, the card asks them to get the project owner to connect the service, because apps always use the owner's connections.

The AI reads your real data

For many services, the AI can read your actual data while it builds: for example the tables in your Airtable base or the products in your Shopify store. That way the page it builds uses your real field names and content instead of made-up examples. It only reads from connections that are on for the app you're building. It can also read a Google Sheet that's shared by link ("Anyone with the link" can view).

Build a page that lists the products from my Shopify store, with a search box and a category filter.

The AI only reads. It never adds, changes or deletes anything in the service. It reads a limited amount per build, values that look like secret keys are hidden, and email addresses and phone numbers come back partly hidden.

Tools the AI can use while building

Further down the Connectors page, Tools the AI can use while building lets you connect work tools so the AI can look things up while it builds: your real issues, docs, designs or error reports. Only you can use these, and only while you build: teammates' builds can't use them, and your published app never sees them. Sign-ins and tokens for them are stored encrypted.

Ready-made options include Linear, Notion, Sentry, Jira & Confluence, Canva, Miro, Amplitude, PostHog, n8n, Polar, Sanity, Hex, HeyGen, Granola, Context7, Webflow and Zapier. Click one and follow its steps: most ask you to sign in with that service, a few (such as n8n and Zapier) ask you to paste a server address or token from that service, and Context7 needs no account. You can also use Browse directory to search a public directory of these tools, or Add your own to connect one by its web address. Tools in the directory are run by their makers, not Buildliy, so only add ones you trust. These tools are sometimes called MCP servers.

Each connected tool has a card with Test, an on/off switch and Disconnect. If its sign-in stops working, the card shows Sign in (or Reconnect) instead of Test. Open its list of tools to choose what the AI may do without asking. The setting at the top applies to every tool you haven't set on its own:

Each tool in the list can also be set to Always allow, Ask each time or Never on its own. When a tool needs your OK, you get a card in the chat (Skip, Allow once or Always allow) before the AI uses it.

Look at the open bugs in my Linear "Website" project and fix the ones that affect the checkout page.

Choose which apps use a connection

A new connection is on for every app you own, except apps shared with your team (see below). To change that, open the connector on the Connectors page and look under Where it's used:

• Use on all my projects sets the default. On, every app can use the connection unless you switch it off for that app. Off, only the apps you switch on can use it.
• The list below it has a switch for each app (your 50 most recently updated apps), so you can turn the connection on or off for just that one.

You can do the same from inside an app: open the Manage tab and choose Connectors. Each row shows whether the connection is on for this app and why, plus the names of the settings it gives your app (for example RESEND_API_KEY). Click Browse connectors to add more.

• Changes reach the app's preview within about a minute (after any build that's running finishes), and the live app the next time you publish.
• Only the project's owner can switch connectors on or off. Apps always use the owner's connected accounts.
• In an app shared with your team, connections stay off until you switch them on there. Buildliy asks you to confirm first, because everyone who can build in that app could use your key and ask the AI to read data from it.
• If an app has its own secret with the same name in Manage → Secrets, the app uses that value instead of the connection's. See Secrets and API keys.

Check, fix or disconnect

Open a connected service to see its masked key, when it was last checked, and these buttons:

• Check again tests the saved key with the service right now.
• Disconnect removes the connection from your account after you confirm. Your apps' previews and new builds stop using it. An app you've already published can keep using the key it was published with until you publish it again.

If Check again finds that the service no longer accepts your key, the card shows Needs attention and the connection is left out of your builds until you paste a new key and click Reconnect.

How your keys are kept safe

• Every key is checked with the service before it's saved (if the service can't be reached, it's saved and marked as not checked yet), then stored encrypted (AES-256).
• After saving, Buildliy only ever shows a masked preview of the key, never the full value.
• Secret keys are only used in your apps' server code. They never appear in your app's browser code.
• A few values are public by design, such as an analytics project key or a maps key that has to load in the browser. The connect window tells you which values those are, and for a maps key it suggests restricting the key to your app's website in that service's settings.

Available connectors

These are the connectors you can use today, by category. The Connectors page always has the current list.

Related

• Connect any API
• Take payments
• Secrets and API keys
• The Manage tab