Skip to content
Proud to collaborate with Microsoft for Startups

appdata.publish-as-app ​

Publish an organization-side record into an app-owned appdata table, visible to every end-user of the app

Publish one organization-side record into an app-owned table.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-appdata
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—Authenticated organization UUID
identity_app_uuiduuidYes—Identity app to publish into; must be owned by the authenticated organization
database_slugstringYes—Virtual database slug
table_slugstringYes—Virtual table slug; the table must declare ownership kind 'app'
payloaddictNo—Declared field payload to publish (single record). Mutually exclusive with 'payloads'
payloadslistNo—Declared field payloads to publish as one atomic batch (max 500). Mutually exclusive with 'payload'. All rows commit together or none does
sourcestringNo—Free-text provenance label recorded on the audit row (e.g. 'car.reconcile-window')
request_idstringNo—Caller request id for audit correlation
actorstringNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes——
identity_app_uuiduuidYes——
database_slugstringYes——
table_slugstringYes——
record_uuiduuidNo—Published record UUID (single-payload calls; the first row of a batch)
record_uuidslistNo—Every published record UUID, in input order — keep these; they are what retract-as-app takes
published_countintegerNo—Number of records inserted by this call
publishedbooleanNo—True when a record was inserted
published_atstringNo—ISO-8601 publication timestamp
published_by_workflow_uuidstringNo—Workflow run that published the record — the provenance stamp
sourcestringNo——
failure_reasonstringNo—Engine-stamped failure reason
failed_at_statestringNo—State when the workflow failed
failed_stepstringNo—Failed DAG step name
failed_layerintegerNo—Failed DAG layer index
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—completePublish record
completedNoYesYes—Published
failedNoYesNo—Publish failed

State Diagram ​

Transitions ​

FromActionToDescription
pendingcompletecompleted—
pendingfailfailed—

Outcomes ​

OutcomeTypeDescriptionState Data Keys
publishedSUCCESSPublish an organization-side record into an app-owned appdata table, visible to every end-user of the apprecord_uuid
failedFAILUREAppdata workflow failedfailure_reason

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "appdata.publish-as-app",
  "initial_data": {
    "organization_uuid": "value",
    "identity_app_uuid": "value",
    "database_slug": "value",
    "table_slug": "value"
  }
}