Development

FloopFloop Integration

Build and deploy live web apps from a prompt — create, refine, update and archive projects, manage per-project secrets and subdomains (writes require approval).

Capabilities

This integration enables workers to:

  • List projects and read build/deploy status + the live URL
  • Create a new app from a prompt (generates & deploys; approval-gated)
  • Refine a deployed app iteratively (approval-gated)
  • Update or archive a project (approval-gated; archive is destructive)
  • Manage per-project secrets/env vars — set & remove (approval-gated)
  • Browse & clone the template library; check/suggest subdomains; read usage

Setup

Follow these steps to connect FloopFloop:

  1. Create a FloopFloop API key (Account → API Keys; a Business plan is required to mint flp_ keys)
  2. Navigate to Integrations and add a FloopFloop connection with your flp_ API key
  3. Assign a worker (e.g. Content Creator, Operations Assistant) to use it

Official links

Tutorial

End to end: connect FloopFloop, hand a worker a brief, and let it build, deploy, and iterate on a real live web app — with your approval on anything that ships.

  1. Connect FloopFloop: in Integrations, open the FloopFloop section, paste your flp_ API key, and click Connect.
  2. Bind a worker: in your connections, assign a worker (e.g. a Content Creator or Operations Assistant) to the FloopFloop connection so it can use these tools.
  3. Give it a brief: create a task like “Build a landing page for my coffee shop with a sign-up form and deploy it to the coffee-corner subdomain.”
  4. It grounds itself first: the worker checks subdomain availability and lists existing projects, then proposes a floop_create_project action.
  5. Review & approve: approve the proposed action — FloopFloop generates the code and deploys the app. Nothing ships without your approval.
  6. Get the live URL: once the build finishes, the worker reports the live URL; asking it to check status re-runs floop_get_project until the deployment is live.
  7. Iterate: follow up with “add a contact form and change the hero color” — the worker proposes floop_refine_project; approve to ship the change. Use floop_set_secret to add environment variables, and floop_clone_library to start from a template.

Prefer code? Drive the same flow programmatically with the TypeScript SDK:

import { CreateWorker } from "@createworker/sdk";

const cw = new CreateWorker({ apiKey: process.env.CREATEWORKER_API_KEY! });

// Hand the FloopFloop-bound worker a brief.
const task = await cw.tasks.create({
  workerId: "wrk_…",
  title: "Build & deploy a landing page for my coffee shop (subdomain: coffee-corner)",
});

// The worker proposes floop_create_project — approve it to generate + deploy.
const done = await cw.tasks.waitForTask(task.id);
if (done.status === "PROPOSED") await cw.approvals.create(task.id, { decision: "APPROVE" });

// The deliverable includes the live URL once the deployment is ready.
const { data } = await cw.tasks.deliverables(task.id);
console.log(data[0]?.content);

Security

  • API keys are encrypted at rest (AES-256-GCM)
  • Create/refine/update/archive and secret changes require human approval
  • Workers can never mint or revoke FloopFloop API keys

Credential Storage

All integration credentials are encrypted at rest using AES-256-GCM encryption. OAuth tokens are automatically refreshed when needed.

Supported Roles

The following roles can use this integration by default:

Related Documentation