Data Operations

Actions for reading, writing, updating, and deleting data in databases

Data operation actions allow you to interact with databases in your workflows. These actions support SQL databases (PostgreSQL, MySQL, SQLite) and MongoDB through configured integrations.

Before using data operations, ensure you have a database integration configured. See Configuration Reference for setup details.

---

fetch

Retrieves data from a database table using filters.

Database Integration

The SQL or MongoDB integration to read from.

YAML Key	integration
Type	integration
Required	Yes

Table

The database table or collection name to query.

YAML Key	table
Type	string
Required	Yes

Filters

Query filters to narrow down results. See Filter Syntax for available operators.

YAML Key	filters
Type	array
Required	No

Single

Return a single result object instead of an array.

YAML Key	single
Type	boolean
Required	No
Default	false

Fail If Empty

Treat no results as a failure, routing to the fail step. Note the default is true: unless you set this to false, a query that matches nothing fails the step.

YAML Key	failIfEmpty
Type	boolean
Required	No
Default	true

Datasource Options

Additional datasource-specific options.

YAML Key	datasourceOptions
Type	map
Required	No

Output

{{ .step_id }} holds the rows the query matched, with the table’s own column names — one row when single is set, otherwise a list.

Example

actions:
  get_user:
    type: fetch
    config:
      integration: my_database
      table: users
      filters:
        - field: email
          operator: eq
          value: "{{ param \"email\" }}"
      single: true
      failIfEmpty: true

---

save

Inserts a new record, or updates existing records, in a database table.

save is one action for both operations. When filters are provided, it updates every record they match. When filters are absent, it inserts a new record.

Database Integration

The SQL or MongoDB integration to write to.

YAML Key	integration
Type	integration
Required	Yes

Table

The database table or collection name to write to.

YAML Key	table
Type	string
Required	Yes

Fields

The data to write, as key-value pairs.

YAML Key	fields
Type	map
Required	Yes

Filters

Filters identifying which records to update. Omit them to insert instead. See Filter Syntax for available operators.

YAML Key	filters
Type	map
Required	No

Datasource Options

Additional datasource-specific options.

YAML Key	datasourceOptions
Type	map
Required	No

Output

{{ .step_id }} is an object with one field:

Path	Type	Description
id	string	The id of the saved record

Insert Example

With no filters, save inserts:

actions:
  create_user:
    type: save
    config:
      integration: my_database
      table: users
      fields:
        email: "{{ param \"email\" }}"
        name: "{{ param \"name\" }}"
        password: "{{ .hash_password }}"
        created_at: "{{ now }}"

If no id field is provided, a UUID is generated automatically. Read it back with {{ .create_user.id }}.

Update Example

With filters, save updates the records they match:

actions:
  update_user:
    type: save
    config:
      integration: my_database
      table: users
      filters:
        - field: id
          operator: eq
          value: "{{ param \"user_id\" }}"
      fields:
        name: "{{ param \"name\" }}"
        updated_at: "{{ now }}"

---

delete

Deletes records from a database table.

Database Integration

The SQL or MongoDB integration to delete from.

YAML Key	integration
Type	integration
Required	Yes

Table

The database table or collection name to delete from.

YAML Key	table
Type	string
Required	Yes

Filters

Filters to identify which records to delete. See Filter Syntax for available operators.

YAML Key	filters
Type	array
Required	Yes

Datasource Options

Additional datasource-specific options.

YAML Key	datasourceOptions
Type	map
Required	No

Example

actions:
  delete_user:
    type: delete
    config:
      integration: my_database
      table: users
      filters:
        - field: id
          operator: eq
          value: "{{ param \"user_id\" }}"

---

mongoquery

Executes native MongoDB queries with filter and projection support.

MongoDB Integration

The MongoDB integration to query.

YAML Key	integration
Type	integration
Required	Yes

Collection

The MongoDB collection name to query.

YAML Key	collection
Type	string
Required	Yes

Filter Query

MongoDB filter query in JSON format.

YAML Key	filterQuery
Type	string
Required	Yes

Projection

MongoDB projection query in JSON format to select specific fields.

YAML Key	projection
Type	string
Required	No

Fail If Empty

Treat no results as a failure, routing to the fail step.

YAML Key	failIfEmpty
Type	boolean
Required	No
Default	true

Example

actions:
  query_users:
    type: mongoquery
    config:
      integration: my_mongodb
      collection: users
      filterQuery: '{"status": "active", "age": {"$gte": 18}}'
      projection: '{"name": 1, "email": 1, "_id": 0}'
      failIfEmpty: false

Dynamic filter example:

actions:
  search_users:
    type: mongoquery
    config:
      integration: my_mongodb
      collection: users
      filterQuery: '{"email": "{{ param "email" | stringescape }}"}'

Use the stringescape template function when inserting user input into JSON queries to prevent injection attacks.

---

firestore

Stores documents in Google Cloud Firestore. Unlike the other data actions, it does not use an integration — it is configured with a service account directly.

Project ID

The Google Cloud project that owns the Firestore database.

YAML Key	projectID
Type	string
Required	Yes

Collection ID

The Firestore collection to write the document into.

YAML Key	collectionID
Type	string
Required	Yes

Document Template

The document to write, as JSON. Use template syntax to fill in values.

YAML Key	documentTemplate
Type	string
Required	Yes

Service Account

The Google service account credentials JSON. Use a secret rather than inlining it.

YAML Key	serviceAccount
Type	string
Required	Yes

Output

{{ .step_id }} holds the document that was written, as the JSON text it was sent as.

Example

actions:
  record_event:
    type: firestore
    config:
      projectID: my-gcp-project
      collectionID: events
      serviceAccount: "{{ secret \"gcp_service_account\" }}"
      documentTemplate: |
        {
          "user_id": "{{ param \"user_id\" }}",
          "event": "{{ param \"event\" }}",
          "recorded_at": "{{ now }}"
        }

---

Filter Syntax

The fetch, update, and delete actions use a common filter syntax:

filters:
  - field: field_name
    operator: eq
    value: "comparison_value"

Available Operators

Operator	Description
eq	Equal to
ne	Not equal to
gt	Greater than
gte	Greater than or equal
lt	Less than
lte	Less than or equal
in	Value in array
nin	Value not in array

Multiple Filters Example

filters:
  - field: status
    operator: eq
    value: active
  - field: age
    operator: gte
    value: "18"
  - field: role
    operator: in
    value:
      - admin
      - moderator

---

Next Steps

Actions Overview

Learn about action structure and chaining.

Vector Operations

Store and query vector embeddings.

Authentication

Secure your APIs with JWT and authentication.

Secrets Management

Securely store database credentials.