Skip to main content

Automation & the API

Anything you can do in the Cobblr UI, you can do without it. The web app is one client of a REST API, and everything under it goes through that same API. This section is the reference for driving a workspace from a script, another service, or an agent.

There are a few ways in, and they layer:

  • REST API reads and writes records, runs actions, and installs bundles. Every other surface here is built on it.
  • Wires run inside the workspace: when an event fires, do an action. No outside caller needed once a wire is set up.
  • Events and webhooks connect a workspace to systems outside it, in both directions: fire an event out to a URL you own, or take an inbound ping from another system.
  • API tokens are how a script or agent authenticates. A token can be unrestricted or clamped to a narrow set of routes.

For working on a workspace conversationally, Cobblr also ships an MCP server that wraps the same API for your own Claude, including an opt-in mode where it drives your open browser tab. That has its own page: Connecting Claude.

Which one to reach for​

Reading or changing data on a schedule of your own, or from an existing service, is a REST job with a token. Reacting to something that happens inside the workspace (an order arrives, stock drops) is a wire, and it needs no code. Getting those same happenings out to Slack, Discord, or a service you run is a webhook. The three compose: a wire can react to an inbound webhook, and an outbound webhook can carry the result somewhere else.