Connect other services to your website

Payments, Slack alerts, mailing lists, automation tools: how the assistant connects your website to a service you already use, how it asks for the key, and where the key lives afterwards.

Your website can talk to services you already use: take payments through your Stripe account, post every new booking to Slack, add signups to your Mailchimp list, hand form entries to Zapier or Make. Each of these needs one thing from you: a key or a link from that service's own dashboard. This page explains how that hand-off works. The service-specific guides tell you exactly where to click.

How it goes

  1. You ask for the connection in plain words. "Post every new booking to our Slack channel", "add newsletter signups to Mailchimp". The assistant asks which service you use if it is not obvious, and what should happen when it fires. "Just email me" is always an option, and needs no key at all.
  2. A card appears in the chat. It lists the values the assistant needs, one field each, with a short note on where each one comes from. The How do I get this? link on the card opens the matching guide right inside the builder.
  3. You paste each value into the card and save. The values go straight into your website's settings. They never appear in the conversation; the assistant is told which ones were saved, not what they contain.
  4. The assistant tests the connection and tells you the result. A real test: a test message to Slack, a check of the key against Stripe, a first read of a calendar link. You get a plain answer such as "Slack accepted the test message" or "the key was refused". Nothing is called connected until that test passes.
  5. The feature is built and you try it once yourself. Send a form, make a test booking, and watch it arrive on the other side.

Never paste a key in the chat

A key is a password to your account on that service. The chat box refuses text that looks like one and reopens the card instead. If a card was closed or timed out, just ask again ("let's connect Slack") and the assistant shows a fresh card.

Where the values live

Every value is stored under Website settings, Environment variables: click the project name at the top left of the builder to get there. You can change a value there at any time, for example when you rotate a key, without touching the site. The same values are used by the published site, so a connection that works in the preview works live too.

When you publish or move the site

Publishing carries the values across, nothing to redo. If you ever export your code and host it elsewhere, the README lists the variable names to set on the new host. No connection depends on Looops staying online: the code in your site talks to the service directly.

Guides

For a service that has no guide yet, the assistant writes the three steps in the chat before showing the card: where to log in, which page, what to copy.

Common questions

Can the assistant log into the service for me? No. You copy the key yourself, once. That keeps your account in your hands.

Is the key safe on Looops? It is stored encrypted with your website's settings, shown to nobody, and only ever read by your own site's code when it runs.

A service only offers "Sign in with..." and no key. Then the assistant says so and offers the email route instead. Some services add a key option under "developer" or "API" settings; the guides point to it when one exists.