Workflows in apps and connection sync
Connect repeatable processing to app data, app parameters, and source refreshes.
Workflows power both standalone automation and app-specific processing. Connection sync is also a workflow, so refreshes can use the same run history and monitoring model.
Use workflow output in an app
An app can bind a workflow data source to the records that process publishes. Configure the workflow's input and destination, run it, then inspect the app's Data view to confirm the expected source is available.
Keep source identity and output schema stable when components depend on them. Renaming a display label is different from replacing the underlying source. A workflow change that removes fields can require a corresponding app update.
Some apps manage their own processing recipes. Their workflows can appear in Workflows but protect structural edits. Change supported app parameters or use the app's reviewed upgrade flow rather than bypassing those protections.
Inherit app settings
A model-backed job can declare that its model comes from App Parameters. That choice is resolved when the run starts. Stored fallback model values do not override the app's current parameter selection.
Check inherited models, extraction profiles, and source settings when an app's behavior differs from a standalone test. The same graph can produce different results with different supported parameter bindings.
Refresh a connection
From a connection's workflow view, open or create its sync workflow and trigger it. Monitor the run instead of assuming a button click means synchronization completed. Then inspect the connection's resulting records or files.
A sync workflow can be manual, scheduled, or combined with further processing depending on the supported source. Use the workflow list's connection scope to find other processes affected by changing that connection.
Keep human decisions separate
A generation workflow can finish before human review begins. An app can use committed decisions to trigger a declared follow-up process, but that does not let the generation workflow approve its own proposals.
See apps, connections, data sources, and publishing workflows.