← Back to all posts

Integrations: what you have to bring, and what is already there

Integrations: what you have to bring, and what is already there

"Integrations" is usually a wall of logos that tells you nothing about how much work you are in for. So here is the same list, sorted by what it costs you.

Already there, nothing to connect

Every project gets these the moment it exists. No account, no keys, no setup step.

  • A Postgres database. A real one, per project, not a spreadsheet pretending.
  • User accounts, roles and permissions. Sign-up, sign-in, password reset, and rules about who can see which rows.
  • File storage. Uploads, private folders, the lot.
  • Email notifications. A confirmation to the customer, a heads-up to you.
  • Scheduled automations. Something that runs every morning, or every hour.
  • Webhooks and API keys. So other software can talk to your app, and your app can talk back.
  • A custom domain. Yours, with a certificate, www handled.
  • AI image generation, image editing and stock photos. Make a picture, crop it, or pull a real one.
  • Charts.

If your idea only needs things on this list, you can describe it and have it running without opening another tab.

Sign in once, and the builder can use it

These are accounts you already have. You connect one, tick exactly what it may touch, and from then on the builder can read from it while it works.

  • Google Sheets, Google Drive, Google Calendar and Gmail
  • GitHub, so your project's code can be pushed to your own repository
  • Sentry and PostHog

It only ever uses the specific things you tick. That list is on the screen before you connect, and some of them can change your data, so it is worth reading rather than clicking past.

Paste one value, once

The rest are a single key or URL, copied from the other service into your project settings. One paste, then the builder wires it into whatever it makes.

  • Stripe, a secret key, and your app takes real money
  • Slack, a channel webhook, and a channel hears about every order
  • Sign in with Google, a client id and secret, so your customers use the account they already have
  • Google Analytics, a measurement id
  • Google Maps, an API key
  • Search Console, a verification token
  • Calendly, your booking URL
  • Cloudinary, a cloud name

The credential goes into your project's settings, not into a prompt. That distinction matters more than it sounds: the builder writes files that get published to the internet, so anything it can see is something that could end up in a page. It never handles these values.

Anything else with an API

The list above is what we made a button for, not the limit. If a service has an API, your app can use it: give it a webhook to send to, or an API key to call with, and the app talks to it on its own. No plugin, no waiting for us to add it.

Why this split is the useful one

A logo wall implies every item is the same size of job. It is not. Roughly half of that strip is work that has already been done for you and costs nothing to use, and most of the other half is one paste. Knowing which is which is the difference between "that will take a week" and "that is a sentence and a copy and paste."

If you have been putting something off because it sounded like it needed three services wired together, check the first list. It might already be in there.