Loop templates
Loops: a LoopDefinition (the loop builder's flow), its revisions (who changed it: a person, the Agent in a chat, an MCP agent or an API key) and the Agent chat that holds its history, shared with everyone who can see the loop.
List loop templates
The app's template library, most wanted first: each template's card copy and the definition a loop starts as when a person picks it, named after the template. To start from one, create a loop with its definition (POST /loops), changed as needed. Guests don't see loops (403).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
Pluto-Workspace | string (uuid) | Optional | The workspace to act in, for credentials that can reach several (sessions, agent tokens). API keys belong to one workspace; another value is a 403. |
Response
items- In the library's order.
items[].definition- The LoopDefinition
{ version: 1, name, platform, trigger, nodes, edges }(the loop builder's contract, docs/architecture.md "Loops").platformis the ad platform the loop runs on, fromGET /platforms(absent:meta): every block works on it, and it can't change once the loop has a block (duplicate the loop to another platform instead; Run loop starts loops on other platforms). Drafts may be unfinished; malformed ones are a 422 listing every problem by path (definition/nodes/2/block). Numbers and money inconfigare decimal strings. An Agent or Write reply step'sskillspins up to 5 skills by name fromGET /loop-skills(shared with the workspace or Pluto's); another name is a 422. items[].description- What it does, in a sentence.
items[].family- The card it's one version of, the same on every platform (
pause-losing-adsfor its LinkedIn version): one card per family. items[].featured- Shown first on the Loops page.
items[].group- Its section in the library.One of
optimize,monitor,engage items[].id- Stable template ID.
items[].platform- The ad platform it's for, from
GET /platforms. Listed only where its definition passes the check saving runs there for this workspace (the platform is on for its organization and runs every step). items[].platforms- Every platform its card is listed on here (its family's listed versions), in
GET /platforms' order: the platform marks the card shows. items[].title- Its name in the library.
items[].when- When it runs, e.g.
Every morning.
curl "$PLUTO_API/loop-templates" \
-H "Authorization: Bearer $PLUTO_KEY"