Skip to main content
Connectors link outside services to your projects. Once a service is connected, the AI uses it every time it builds or edits a project: contact forms email you, pages count their visitors, a chat bubble lets visitors message you, and buy buttons take payments. Pollinations is the exception: the AI only uses it when you ask for generated images or AI features. Web3Forms, Umami, Plausible, tawk.to and Square only ask for something that is safe to put in a web page: a public key, tracking code or a link. AppBlips never needs a password or a secret key for any of them. Pollinations works differently: you sign in to it, and AppBlips keeps that sign-in to itself (see Pollinations).
AppBlips has no partnership, sponsorship or affiliate arrangement with any of these services or the companies and developers behind them. They are offered because they work without a server or a secret key. Each one is a separate service with its own terms, prices and privacy policy, and questions about your account with it go to that service. Their names and logos belong to their owners.

​
Set up a connector

1

Open Connectors

Click Settings, then the Connectors tab. You see a card for each service.
2

Pick a service

Click its card. Click How it works at the top if you’d like an explanation of the service before you start.
3

Turn it on

Click the switch next to Enable and the service name, for example Enable Square.
4

Paste what the service gives you

Paste the key, code or link into the box. The sections below say where to find it for each service. A green Connected. message appears when it looks right.
Changes save as you type, so there is no Save button. Click Connectors at the top to go back to the cards. Each card shows Connected, Needs key or Not connected.

​
Use a connector in a project

You don’t have to mention a connected service in your requests. If Web3Forms is connected and you ask for “a contact form”, the AI sets it up to email you. If Square is connected and you ask for “a buy button”, it opens your Square checkout. Projects you built before you connected a service don’t change on their own. To add the service to one:
  1. Open the project.
  2. Click Settings, then Connectors, then the service’s card.
  3. Under Prompts to try, click Copy next to the request you want.
  4. Close Settings and paste the request into the builder chat.
  5. Send it.
If you change your key or link later, use a prompt the same way to update a project you already built. The Browser Game studio only uses the connectors that count visitors. Forms, chat and payments are for the Responsive Website and Mobile & Web App studios.

​
Web3Forms

Web3Forms sends the entries from your forms to your email, so a contact form works without you building or paying for a server. It is a separate service with its own free plan.
  1. Go to web3forms.com and enter the email address you want entries sent to.
  2. Web3Forms emails you an access key: a 36-character code like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
  3. In AppBlips, turn on Web3Forms and paste the key into the Access key box.
The AI then uses it for every form that sends a message to you, such as contact, signup and booking forms. The form shows a message on the page when the entry is sent, or what went wrong. Forms send real emails from the preview too, so a test entry there lands in your inbox.
The access key is made to sit in a website’s code. It can only send email to your own inbox, so it is safe in the pages and any HTML you export.

​
Umami

Umami counts the visitors to your websites, apps and games and shows them on a dashboard: how many people came, which pages they viewed, and where they came from. It doesn’t use cookies, so the AI doesn’t add a cookie banner for it. Umami has a free plan, and you can also run it on your own server: see Umami on GitHub.
  1. Sign up at umami.is and add your website.
  2. Open the website’s settings in Umami and copy its tracking code.
  3. In AppBlips, turn on Umami and paste the code into the Tracking code or website ID box. On Umami Cloud you can paste just the 36-character website ID instead.
The AI then adds the tracking code to every page, in every studio. Visits from the AppBlips preview, including the AI’s own testing, aren’t counted. Your stats start once you put the exported project online.
AppBlips only keeps the parts of the tracking code it needs (the script address and your website ID). Anyone who sees the code can only add visits to your stats, not read them.

​
Plausible

Plausible counts the visitors to your websites, apps and games and shows them on a dashboard: how many people came, which pages they viewed, and where they came from. It doesn’t use cookies, so the AI doesn’t add a cookie banner for it. Plausible is paid, with a free trial, and you can also run it on your own server: see the Plausible Community Edition on GitHub.
  1. Sign up at plausible.io and add your site, using the web address it will have once it is online.
  2. Open the site’s settings in Plausible and copy everything in the Site installation section.
  3. In AppBlips, turn on Plausible and paste it into the Tracking code box.
The AI then adds the tracking code to every page, in every studio. Visits from the AppBlips preview, including the AI’s own testing, aren’t counted. Your stats start once you put the exported project online at the address you gave Plausible.
AppBlips only keeps the parts of the tracking code it needs (the script address and your site ID). Anyone who sees the code can only add visits to your stats, not read them.

​
tawk.to

tawk.to adds a live chat bubble to the corner of your websites and apps. Visitors click it to message you, and you reply from the tawk.to dashboard or its phone app. It is free, with optional paid extras.
  1. Sign up at tawk.to and create a property for your website.
  2. In tawk.to, open Administration, then Chat Widget.
  3. Copy everything in the Widget Code box, from <!--Start of Tawk.to Script--> to <!--End of Tawk.to Script-->.
  4. In AppBlips, turn on tawk.to and paste it into the Widget code box.
The AI then adds the chat bubble to every page and keeps the bottom-right corner free for it. The chat works in the preview too, so a message you send there reaches your tawk.to dashboard. tawk.to uses cookies to remember chats, so where the law requires it, your site may need a cookie notice.

​
Square

Square takes payments for you. You create a payment link in Square for each thing you sell: a web address that opens Square’s checkout page for it. The buy, order, pay and donate buttons in your websites and apps open that link, people pay by card, Apple Pay or Google Pay, and the money goes to your Square account. Square charges a fee on each payment.
  1. Sign up at squareup.com, or sign in to the Square Dashboard if you already use Square.
  2. Open Payment links. If you can’t see it, type “payment links” in the Dashboard’s search box.
  3. Create a link. Square asks what it is for (a payment, an item, a donation or an event), its name and its price.
  4. Click Copy link. The link starts with https://square.link/u/.
  5. In AppBlips, turn on Square and paste the link into the Payment links box.
To sell several things, put each link on its own line with the name of what it sells in front:
The AI uses the names to match each link to the right button. Square’s button code works too: paste it and AppBlips keeps only the link. Prices are set in Square, so to change one, edit the payment link in Square; your website doesn’t need to change. Payments are real, including from the preview. In the desktop app, the checkout opens in your normal web browser.
Only paste payment links. AppBlips never needs your Square access token or any other secret, and refuses one if you paste it. If you have shared a token anywhere, replace it in the Square Developer Console.

​
Pollinations

Pollinations is an open-source service for AI images and text. With it connected, you can ask the AI for custom images instead of stock photos, and for AI features such as a chatbot, a writing helper or an image generator. Pollinations uses its own credits, called Pollen. It is a separate service with its own terms and prices. Using Pollinations through AppBlips costs 25% more than using it directly. The extra supports AppBlips. This applies to your own images and, if you choose Visitors use their own Pollen, to your visitors’ AI use too. The Connect Pollinations button in your sites tells visitors: “Includes a small fee that supports AppBlips.”

​
Sign in

1

Open Pollinations

Click Settings, then the Connectors tab, then the Pollinations card.
2

Start the sign-in

Click Sign in with Pollinations. A Pollinations page opens in your web browser. If it doesn’t, click open it here in AppBlips.
3

Approve AppBlips

On the Pollinations page, sign in and approve AppBlips. If it asks for a code, type the one AppBlips shows. Here you also choose the most Pollen AppBlips may spend and how many days the sign-in lasts.
4

Go back to AppBlips

AppBlips shows Signed in as and your account name, with the Pollen it has left.
5

Turn it on

Click the switch next to Enable Pollinations. Until you’re signed in, it stays off and shows “Sign in with Pollinations first, then turn this on.”
The sign-in ends after the number of days you chose, or once it has spent its Pollen limit. Pollinations then turns off. Click Sign in with Pollinations again and turn the switch back on. To cancel it sooner, click Sign out, or delete it on the Keys page at enter.pollinations.ai.
Your sign-in stays inside AppBlips. It is never written into your projects, and it is only used to make the images you ask for.

​
Generated images

Ask for them in the builder chat, for example “Add a hero image made with Pollinations”. This works in the Responsive Website and Mobile & Web App studios.
  • AppBlips makes each image with your sign-in after the AI finishes, and pays for it from your Pollen. Most image models cost a small fraction of one Pollen per image.
  • One request makes at most 12 new images.
  • Pollinations stores each image at a public web address that needs no key, and that address goes into your project.
  • When you publish or export, AppBlips copies the images into the site, so they stay online as long as it does. A .zip export keeps them in an images folder, and a single-file export builds them into the page.
  • Pollinations deletes a stored image after 30 days without a view. In a project you haven’t opened for a month, an image can disappear. Ask the AI to make it again if that happens.

​
AI features in your sites

AI features, such as a chatbot or an image generator, run in your visitors’ browsers, so something has to pay each time a visitor uses one. Your sign-in is never used for this. Under AI features in your sites in Settings → Connectors → Pollinations, choose who pays. The AI builds the features to match your choice.
  • Visitors use their own Pollen (safer) is the default. The feature shows a Connect Pollinations button. The visitor approves AppBlips on Pollinations’ website with their own account, and their use comes from their own Pollen. Nothing secret goes into your sites.
  • My key pays (the key goes in my sites’ code) lets visitors use the features without an account. Your site key pays: a separate Pollinations key with a small budget, shared by all your sites. Until you add one, the AI won’t add AI features. If you ask for one, it builds the rest of your request and tells you how to add the key.
To use a feature, ask for it in the builder chat, for example “Add an AI chatbot that answers visitors’ questions, using Pollinations”. If you change your choice, sites you built earlier switch over when you publish or export them again. A site built for the site key that later switches to visitors shows its own Connect Pollinations panel when a visitor first uses a feature.

​
Use your own key

The site key has to be inside your sites so visitors’ browsers can use it. AppBlips scrambles it so it isn’t in plain sight, but this is not foolproof: anyone with a little know-how can find it and spend its Pollen. Only use a key made for this, with a small budget, so the most you can lose is that budget.
To make a safe key:
  1. Go to enter.pollinations.ai/keys and sign in.
  2. Create a new secret key. Name it something like “My AppBlips sites”.
  3. Set a small Pollen budget, for example 2. AppBlips won’t accept a key without one.
  4. Allow only the models your sites need: text for chat features, and image if visitors make pictures.
  5. Set an end date if you can, so a leaked key stops working on its own.
  6. Leave every account permission off.
  7. Copy the key. It starts with sk_.
Then add it to AppBlips:
  1. In Settings → Connectors → Pollinations, under AI features in your sites, choose My key pays (the key goes in my sites’ code).
  2. Paste the key into the Site key box.
  3. Click Check key. AppBlips asks Pollinations about the key and refuses it if it has no budget or can manage your account.
  4. Read the warnings, then tick I understand that anyone can find this key in my sites and spend its Pollen.
From then on, AI features in the preview and in everything you publish or export use this key. If the budget runs out, or you delete the key, the features show “AI features are unavailable right now.” To stop using the key, click Remove key, or delete it on Pollinations’ Keys page. Sites you already published keep the key until you publish them again, so delete it on Pollinations to stop those too. In the Browser Game studio, ask for Pollinations images for things like the title screen, backgrounds or sprites; everything else in a game is still drawn in code. Imported sites don’t use Pollinations.

​
Request a connector

Missing a service?
  1. Click Settings, then Connectors.
  2. Click Request a connector at the end of the cards.
  3. Enter the service and what you’d like it to do.
  4. Add your email only if you’d like a reply.
  5. Click Send request.
Your request goes to the AppBlips team through Web3Forms. Nothing about your projects is sent.

​
Privacy

AppBlips saves your connector settings on your computer. It never contacts these services itself, except Web3Forms when you send a connector request, and Pollinations as described in Pollinations. The pages you build contact them, including in the preview, and anything a connector needs is written into those pages and any HTML you export. Your Pollinations sign-in is the exception: it is kept like your AI key and never written into a page. See What does AppBlips connect to? in the FAQ.