Publish data for other apps

Define stable read-only outputs that other apps can consume.

A published output is a named data contract from one app to another. The producing app chooses the workflow-backed records it exposes; consuming apps bind to that output instead of directly reaching into its internal workflow configuration.

Define the contract

An output has a unique id, optional description, and a non-empty set of record types. Its origin is either one of the app's workflow-record data sources or a workflow. It has exactly one origin.

Use the builder's definition editing tools to declare outputs. The current Data section displays the result under Published outputs; it is an inspection view rather than an output-creation form.

Choose ids that describe the stable purpose of the records. Output ids use the builder identifier grammar and must not collide with component or data-source ids. When an output derives from a narrowed data source, its published record types must remain inside that source's declared types.

An output cannot simply republish another app's app-output source. Publish records from your own workflow-backed origin so the contract has an accountable producer.

Consume the output

In another app's builder, open Data and choose Use app output. Select the producer and output, then bind components to the resulting source. Leave the consumer's narrowing empty to read all currently published types, or select a subset within the producer's envelope.

Consumers read records; they cannot trigger the producer's workflow through the output. The producer's published scope remains the ceiling even if a consumer requests broader record types.

Change or withdraw carefully

Review Apps consuming before changing an output id, removing the output, shrinking its published types, or deleting the app. Consumers depend on that address and contract. Strive can refuse destructive changes while dependencies remain; rebind or remove the consuming sources first.

A source showing Resolves confirms the address exists. It does not prove that records are present or current. Check the producer's workflow activity for freshness.

See App-output sources and Dependencies.