Circuitry Logo
Circuitry
Open Circuitry

Deploying

While you're building, a workflow runs only when you press Run. To make it run on its own — when a webhook arrives or a schedule fires — you deploy it. Deploying publishes the current version and turns the trigger on.

What deploying does

  • Webhook workflow → its URL goes live: real requests now start runs.
  • Scheduled workflow → the timer starts: it begins running on its schedule automatically.

Until you deploy, a webhook URL returns nothing and a schedule never fires.

Choose where it runs: circuitry.dev or your own server

Before deploying, pick a Hosted on target in the Start node's configuration:

  • circuitry.dev (default) — runs in Circuitry's cloud. Nothing to install; it just works.
  • Your EServer — Direct — runs on your own Circuitry Server at its own public URL. Fully self-hosted; your data and execution stay on your machine.
  • Your EServer — Proxied via circuitry.dev — circuitry.dev receives the request and forwards it to your EServer. Useful when your server isn't publicly reachable.

For schedules, the cloud option enforces a 5-minute minimum interval; an EServer has no minimum.

Deploy a webhook

  1. Set the Start node to Webhook and (optionally) a custom path.
  2. Copy the Execution URL shown in the panel. It looks like:
https://circuitry.dev/api/webhook/<your-name>/<your-project>/<path>
  1. Click Deploy webhook. The status pill changes to ● Live.
  2. Give the URL to the service that should call it.

The status pill tells you where things stand:

  • ○ Not deployed — the URL isn't live yet.
  • ● Live — deployed and reachable.
  • ◐ Undeployed changes — you've edited the workflow since the last deploy; click Redeploy to push the changes.

Want to see a real request's data before going live? Use Listen for request to capture the next incoming payload without running the workflow — see the Webhooks guide.

Deploy a schedule

  1. Set the Start node to Schedule and build your timer (see Triggers & Scheduling).
  2. Choose your Hosted on target.
  3. Deploy. The schedule starts on its next matching time and runs automatically from then on.

To pause it, undeploy (or switch the Start node back to Manual and redeploy).

Updating a deployed workflow

Edits don't go live automatically — that's deliberate, so you can work safely. When you're happy, Redeploy to publish the new version. The trigger keeps the same URL / schedule.

Next steps