Integrate in one sentence

You do not have to ask for each feature one at a time. You do not even have to describe what you are building. Just say "Integrate this with WEEGLOO", and the connected AI agent looks at the screens you built, works out what is needed on its own, and sets up the features you need all at once. The data, members, and permissions the agent puts in place sit on top of a content management system (CMS) that can handle even large-scale services. Even as your service grows, there is no big job of moving your data.

If you have not connected an agent yet, see Connect an agent first.

This page is about handing over "the whole thing at once." When you instead want to pick out a single feature such as data, search, or members, see the individual how-tos under What to do next below.

Tell your AI like this

Integrate this with WEEGLOO.

This one line is enough. Even without describing what you are building or who uses it, the agent looks at the screens you built and picks the pieces it needs on its own.

What the AI then does

The agent takes this and moves through the following steps.

  1. Looks at your screens to work out what you are building. From the screens you built, it reads what data they handle, who reads and writes (visitors, members, operators), and whether it is read-only or also writes.
  2. Decides the overall structure. Based on what it worked out, it first designs whether to add member login, what structure to give the data, and who can access how far.
  3. Sets up the pieces it needs, in turn. For a guestbook screen, it sets up the data structure that holds the posts (a Content Type), Google login (ServiceLogin), the "own posts only" permission, and public delivery that anyone can read, all in one continuous flow. (It adds search, files, external integration (Webhook), and deployment (Web Hosting) the same way when they are needed.)

Setting up each piece is the same as asking for it one at a time in the individual how-tos below. "Integrate in one sentence" simply has the agent bundle that work and handle it all at once.

The agent decides on its own and carries the work through to the end; it does not ask you mid-way what to build. It does, however, ask at that point for values you have to decide or hand over. That is the case for the address to deploy to and for an external service's API key (the secret key that service uses to confirm "you really are who you say").

Handing over the whole thing versus asking one at a time

  • Integrate in one sentence (this page): use it when setting up all the features you need at once from the start. You do not even have to describe what you are building.
  • Individual how-tos (links below): use them when adding one feature to a service you already built, or touching up a specific part. You pick out only what you want, such as data, search, or members.

The two are the same work asked for at different sizes, so you can mix them. Setting up the whole thing once and then refining it with the individual how-tos is a common flow.

The same one sentence works for mobile apps too

Even if you are building a mobile app (Android or iOS), the approach is the same. Connect an agent and say "Integrate this with WEEGLOO", and it sets up what is needed behind your screens (data structures, members, permissions, and so on) exactly as it does for the web. Pulling in published content through external delivery is the same as well.

Two things, though, are different from the web.

  • Deployment: for a web service you can put what you finished on the internet with Web Hosting (Put your site on the internet), but getting a finished mobile app into people's hands (registering it on an app market) happens outside WEEGLOO. What WEEGLOO takes on is the data, members, and permissions behind the app's screens.
  • Member login: the login feature itself attaches the same way. However, the connection that returns the result to the app after login completes is different from the web, so there is a separate technical step you need. This step is covered in Auth API.

For a finished example that follows this whole flow from start to finish, see the Running Tracker Service.

Check that it worked

  • Ask the agent "Pull together what you've built so far and show me," and it reads back the data structures, login, and permissions it set up.
  • If you can read the guestbook on the page without logging in, and once logged in you can leave a post and delete only your own, then it is done.

What to do next