Skip to main content
Planasonix separates what you are editing from what production runs. You build and save in development. Production (schedules, webhook-driven runs, and other event triggers) executes the promoted version—not every autosave on the canvas.

​
Development vs production

Your organization may also show a staging environment for connection and variable overrides. Promotion to live traffic is still the production pointer.
Multi-environment workflows are available on Professional and higher. Exact environment names and approval rules depend on your organization settings.

​
Save vs promote

Saving and promoting are different actions:
  1. Save writes the canvas definition and creates or updates version history.
  2. Promote to production sets which saved version production uses.
Until a version is promoted, production has nothing (or still points at an older version). Editing the canvas alone does not move the production pointer.

​
Promote to production

1

Save a version you trust

Finish the graph, connections, and node settings. Prefer a deliberate save so the version you promote is intentional (not an accidental restore duplicate).
2

Open Promote to production

From the pipeline, choose Promote to production. Select the version to make live. The picker highlights recent manual versions; restore-origin versions are available when you show all versions.
3

Confirm or wait for approval

Organization admins typically see the version go live immediately (vN is now live in production). Other roles may submit a request that stays pending until an admin approves. Pending requests do not move the production pointer.
4

Verify production

Confirm schedules, webhooks, or a controlled production run use the new version. Check run history after the first live fire.

​
Webhook URLs: minted on save, fired against production

Webhook Source nodes illustrate the lifecycle clearly:
1

Save mints the URL

When you save a pipeline that includes a Webhook Source node, Planasonix provisions an ingest URL (and optional HMAC secret when signature verification is on). The URL appears on the node after save—you do not create it in a separate orchestration screen.
2

Callers can hit the URL immediately

The URL is real as soon as it is minted. Authentication (token path, optional HMAC) is enforced on every request.
3

Production execution needs a promoted version

Event-triggered runs—including webhook source—load the pipeline graph from the production deployment. If the pipeline has never been promoted (or was unpromoted), Planasonix cannot resolve a production version and the run does not execute the canvas you just saved.
4

Promote so live traffic matches the canvas

After you promote the version that contains the webhook node and destination settings, inbound posts run that promoted graph end-to-end.
A common failure mode is saving a webhook pipeline, copying the URL, and posting successfully authenticated payloads that still fail to run the expected graph because production was never promoted. Promote the version, then retest.
For signing headers and verification, see Webhook HMAC signing.

​
Schedules follow the same production pointer

Enabling, editing, or running a production schedule requires the pipeline to be promoted. If the pipeline is unpromoted, schedule actions return a conflict (the schedule stays disabled) until you promote again. Scheduled fires also resolve the production deployment. Unpromoted pipelines skip those fires rather than running the live canvas by accident.

​
Unpromote

Unpromote removes the production deployment pointer and pauses schedules that unpromote itself disabled. Use it when you need to take production offline without deleting the pipeline. Re-promote a version to restore the pointer; schedules that were paused by unpromote can return with that promote. You typically need admin (or equivalent) rights to unpromote. You cannot delete a pipeline that is still promoted—unpromote first (or use the delete approval path your organization enables).

​
Connection and variable overrides

Each environment can bind different variables and connection targets (for example, a sandbox warehouse in development and the live warehouse in production). Promote the graph once; keep environment-specific endpoints in overrides so you do not maintain three separate pipelines. Prefer credential references or managed secrets in production overrides. Do not embed production passwords in plain-text variables.

Webhooks

Webhook Source minting and fire path.

Webhook HMAC

Signing contract for inbound webhooks.

Variables

Values that differ by environment.

Git integration

Optional source control alongside promotion.