Skip to main content
Feedback

Using Flow service component data actions with Flow

Updated 23 July 2026

This type of Flow Service Operation integrates with the database steps in Flow to handle Create, Read, Update, and Delete (CRUD) operations for a particular variety of record, using a single type in a Flow.

Database load steps, Database save steps, and Database delete steps allow Flow to integrate with your Flow Service Data Actions and their associated processes.

Data actions are useful if you intend to send/retrieve the same kinds of records through multiple processes. Using a Message Action instead automatically creates a Request and Response type in the Flow for each associated process. Using database steps also allows you to display data from a service directly in a Flow page, using certain page components, such as a Combobox, Radio, or Table component.

For a worked example of how you can use Data Actions with Flow, refer to A worked example of using Data Actions with Flow.

Flow Service Data Actions map to Flow as follows:

Flow Service Data Actions

  • The Flow Service uses the JSON Profile you assign to the Data Action to automatically create a corresponding type in Flow. Step 1

  • A Database Load step in Flow initiates either the Get Process or the Query Process, depending on the filter options specified in the step Data Action (refer to the details below). Step 2

  • A Database Save step in Flow initiates the Save Process. Step 3

  • A Database Delete step in Flow initiates the Delete Process. Step 4

Using Get Process or Query Process

A Database Load step Data Action can initiate either a Get Process or a Query Process, depending on the filter options specified.

  • If you specify a filter based on a unique identifier for the Data Action in the Database Load step, the Get Process initiates. It returns only a single record, and you must use a unique identifier.

    Get Process

  • If you specify no filter, or filter by ‘where’, for the Data Action in the Database Load step, the Query Process initiates. A Query can return multiple records, typically by populating a List value with the query results. You can then surface these results by loading this data directly from the service into a table component.

    Query Process

Data action profiles and Flow types

A Data Action profile always creates a single type in Flow; this type handles both Objects and Lists through the same single level JSON profile Object.

Data Action Profile and type

  • This is different to Flow Service Message Actions that do not always create a type in Flow, and also creates types that are specific to the Request or Response of a single particular process. Refer to Integration Profiles and Flow Types.

  • Profiles should typically be configured as a ‘flat’ JSON Object profile.

On this Page