Update workflow

Changed on

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Updates a workflow. Send only the fields you want to change. Pass change_summary to label what changed.

Anything you leave out keeps its stored value. Sending a definition that differs from the current one saves it as a new immutable version, and the workflow runs that version from then on. Earlier versions stay readable through List workflow versions.

Updating does not change whether the workflow is running.

This is only allowed from the app's main branch.

<Warning>The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time. Send only the fields documented here. Other request fields are not supported and their behavior can change.</Warning>

put/api/apps/{app_id}/workflows/{workflow_id}

Request

  • Base URL: https://app.base44.com
  • URL: https://app.base44.com/api/apps/{app_id}/workflows/{workflow_id}
  • Auth: HTTP bearer

Path parameters

app_idstring required

ID of the app whose workflows you want to work with.

workflow_idstring required

ID of the workflow, as returned in id by List workflows.

Request body

namestring nullable

New name. Leave it out to keep the current one. Must be unique among the app's workflows that are not archived, so renaming to one another live workflow already uses is rejected.

descriptionstring nullable

New description. Leave it out to keep the current one.

definitionobject nullable

New definition. Leave it out to keep the current one. One that differs from the current definition is saved as a new immutable version, and the workflow runs it from then on. An invalid definition is rejected with the validation errors, and nothing is saved.

triggerobject nullable

New trigger. Leave it out to keep the current one. See Triggers for its shape.

change_summarystring nullable

Note describing this change, kept in the version history. This is only recorded when definition actually changes, since that's what creates the version it's attached to.

Example request

{
  "name": "Email me new signups",
  "description": "Sends an email whenever a User record is created.",
  "definition": {
    "do": [],
    "document": {
      "dsl": "1.0.0",
      "name": "notify",
      "version": "1.0.0"
    }
  },
  "trigger": {
    "config": {
      "cron_expression": "0 9 * * *",
      "timezone": "UTC",
      "trigger_type": "scheduled"
    }
  },
  "change_summary": "Send to the ops alias instead"
}

Response

The updated workflow.

run_accounting_availableboolean

Whether definition-level run counters and last-run fields are available. False for hooks: numeric counters are placeholders (0), last-run fields are null; use run history instead.

idstring required

ID of the workflow.

app_idstring required

ID of the app the workflow belongs to.

file_keystring nullable

Name of the workflow's file in the app's code. This is null on workflows saved before files were kept.

namestring required

Name of the workflow.

descriptionstring nullable

What the workflow is for.

statusstring required

Whether the workflow runs: active, inactive, or archived. See Workflow status for what each means and how it changes.

status_reasonstring nullable

Why Base44 changed the workflow's status on its own, as one of consecutive_failures, end_condition_reached, migration_activation_failed, workflows_not_available, app_blocked, or connector_disconnected. This is null when you changed the status yourself. See Workflow status for what each code means.

current_version_idstring nullable

Version the workflow runs today, as the SHA-256 hash of that definition. This is null until a definition is saved.

triggerobject

What starts the workflow. The trigger sits under config, keyed by trigger_type.

app_type_contextobject nullable

Caller-specific context captured when the workflow was created, such as the conversation that authored it. This API never sets it, so a workflow you create through it starts with null. Updating a workflow through this API doesn't clear an existing value either, so a workflow originally authored through the Base44 app editor or a superagent keeps its context here even after an API update.

last_run_atstring date-time nullable

When the workflow last started running, as an ISO 8601 UTC timestamp. This is null before its first run or for hooks; use run history for hooks.

last_run_statusstring nullable

How the workflow's most recent run ended: success, failed, or cancelled. This is null before the first run or for hooks; use run history for hooks. See Workflow status for how this compares to a run's own status.

consecutive_failuresinteger

Runs that have failed in a row. Resets on the next success. Unavailable when run_accounting_available is false; the placeholder is 0.

total_runsinteger

Runs the workflow has started, ever. Unavailable when run_accounting_available is false; the placeholder is 0.

successful_runsinteger

Runs that finished successfully, ever. Unavailable when run_accounting_available is false; the placeholder is 0.

failed_runsinteger

Runs that ended in an error, ever. Unavailable when run_accounting_available is false; the placeholder is 0.

created_datestring date-time nullable

When the workflow was created, as an ISO 8601 UTC timestamp.

updated_datestring date-time nullable

When the workflow was last changed, as an ISO 8601 UTC timestamp.

created_bystring nullable

Email of whoever created the workflow.

definitionobject nullable

The steps the workflow runs, as a CNCF Serverless Workflow v1.0 document. This is null when no version has been saved yet. Only this endpoint returns it. List workflows leaves it out.

Example response

{
  "social_post": {
    "platform": "linkedin",
    "title": "Meet our new app",
    "body": "Our new app is ready to try.",
    "hashtags": [
      "launch"
    ]
  },
  "id": "68b1c0d4e7b91d003c45a1f2",
  "app_id": "6820f3a4e7b91d003c45a1f2",
  "file_key": "email-me-new-signups",
  "name": "Email me new signups",
  "description": "Sends an email whenever a User record is created.",
  "status": "active",
  "status_reason": "consecutive_failures",
  "current_version_id": "9f2c1a7b3e5d84f60c1b2a9e7d4f8c3b6a5e2d1f0c9b8a7e6d5c4b3a2f1e0d9c",
  "trigger": {
    "config": {
      "cron_expression": "0 9 * * *",
      "timezone": "UTC",
      "trigger_type": "scheduled"
    }
  },
  "app_type_context": {
    "anchor_message_id": "68b1c0d4e7b91d003c45a1f2",
    "conversation_id": "0195f2a1-4c3e-7b21-9f0d-2a5c8e1b4d77"
  },
  "last_run_at": "2026-08-25T09:12:44Z",
  "last_run_status": "success",
  "total_runs": 48,
  "successful_runs": 44,
  "failed_runs": 3,
  "created_date": "2026-07-02T11:04:00Z",
  "updated_date": "2026-08-20T16:31:00Z",
  "created_by": "you@example.com",
  "definition": {
    "do": [],
    "document": {
      "dsl": "1.0.0",
      "name": "notify",
      "version": "1.0.0"
    }
  }
}

Changes