WorqHat
Database

Update Data

Category
Database
Node Type
Update Node

Overview

The Update Data Node allows you to modify existing records in a database table. It is ideal for workflows where data needs to be updated automatically — for example, changing a user’s details, updating a timestamp, or modifying status information after another node’s execution.

This node works within your selected environment (like production) and uses query fields to locate the target record, then data parameters to apply the updates.

Description

Modify existing records in your database.

Use this node to update data in your connected database. You can define which record(s) should be updated by setting query fields (such as id, name, or email) and then specify what values to update using data parameters.

Production Environment

Update data in your live production tables. Use this for real user data.

Development Environment

Update data in development tables for testing and validation without affecting live data.

For example, if you want to change a user’s name and email based on their ID, you can use this node to perform that action automatically — no SQL required.

Input Parameters

The Update Data node accepts the target collection name, query fields to find records, and data fields to update.

collectionNamestringRequired
The name of the target table or collection. Must be in the format 'environment:tableName'.
Example
"production:users" or "development:orders"
Query FieldsobjectRequired
Key-value pairs used to find the specific record(s) to update. Acts like a 'WHERE' clause.
Example
{"id": "12345"}
Data ParametersobjectRequired
Key-value pairs representing the new values to set for the matched record(s).
Example
{"status": "active", "last_login": "2023-10-27"}
Instructions

Dynamic Values: You can use variables from previous nodes in both Query and Data fields:

Query: { "email": "{{form.email}}" }
Data: { "status": "verified" }

Output Parameters

The node returns a structured JSON object containing the results of the update operation.

tableNamestringOptional
The full name of the database table that was updated.
Example
"production:users"
queryIdstringOptional
A unique identifier assigned to the query run.
Example
"1d6330c7-e3c8..."
updatedCountnumberOptional
The number of records successfully updated.
Example
1
messagestringOptional
A summary message describing the result of the operation.
Example
"Successfully updated 1 record(s)"
statusstringOptional
Indicates whether the update was successful or failed.
Example
"success"
Accessing Data

Access output values in your workflow using:

{{update-data.output.updatedCount}}
{{update-data.output.status}}

Output Type

Output Type: JSON

The node produces a JSON object as output, summarizing the operation’s success and update results. This output can be used by subsequent nodes for conditional actions or logging.

Example Usage

Example 1: Update User Profile

Update a user's name and email based on their ID.

{  "collectionName": "production:users",  "Query Fields": {    "id": "10"  },  "Data Parameters": {    "name": "John Doe",    "email": "jd@gmail.com",    "updated_at": "2025-12-01T12:00:00.000Z"  }}
{  "tableName": "production:users",  "queryId": "1d6330c7-e3c8-4712-a12f-4594242321d1",  "updatedCount": 1,  "message": "Successfully updated 1 record(s)",  "status": "success"}

Example 2: Update Order Status

Change an order status to "shipped".

{  "collectionName": "production:orders",  "Query Fields": {    "order_id": "ORD-5521"  },  "Data Parameters": {    "status": "shipped",    "shipped_at": "2025-10-27T10:00:00Z"  }}
{  "tableName": "production:orders",  "queryId": "99a88b77-...",  "updatedCount": 1,  "message": "Successfully updated 1 record(s)",  "status": "success"}

How to Use in a No-Code Workflow

1

Add the Node

Add the Update Data Node from the Database category in your workflow.

2

Select Table

In Table Name, select the database table you want to modify (e.g., production:users).

3

Define Query

Add Query Fields to define which records to find. For example: id = {{input.id}}.

4

Define Updates

Add Data Parameters to specify what will be updated. For example: status = "active".

5

Run Workflow

Save your configuration and run the workflow. Review the output message to confirm the update.

Best Practices

  • Always use a unique identifier like id in your query fields to ensure only the correct record is updated.
  • Double-check that you’re updating the correct environment (e.g., production vs staging).
  • Use the output message and status for error checking or logging.

Do / Don’t

Do
  • ✔️ Format timestamps correctly (ISO format) before updating.
  • ✔️ Test updates on development tables first.
  • ✔️ Use dynamic variables to make your updates flexible.
Don’t
  • ❌ Don’t use broad query fields (like just status="pending") unless you intend to update MANY records at once.
  • ❌ Don’t overwrite critical data without a backup or log.
  • ❌ Don’t ignore the updatedCount — if it's 0, nothing happened.

Common Errors

Successfully updated 0 record(s)WarningOptional
No matching record was found. Check your Query Fields values.
Table not foundErrorOptional
The specified table name or environment is incorrect. Verify the selection.
Missing required fieldErrorOptional
A required input value was not provided. Check your connections.
Connection timeoutErrorOptional
The node couldn’t reach the database. Retry or check connection settings.

Example Workflow Integration

Use Case 1: User Profile Update

Update user details after a form submission.

  1. Form Submission: User submits new details.
  2. Data Validation: Checks if email is valid.
  3. Update Data Node: Updates the record in production:users where id matches.
  4. Email Node: Sends confirmation.

Workflow Data Flow:

{{form.user_id}}      →  {{updateData.query.id}}
{{form.new_email}}    →  {{updateData.data.email}}

Use Case 2: Order Fulfillment

Automatically mark an order as paid after payment.

  1. Stripe Trigger: Payment successful event.
  2. Update Data Node: Find order by transaction_id and set status to "paid".
  3. Slack Node: Notify sales team.

Workflow Data Flow:

{{stripe.transaction_id}} →  {{updateData.query.transaction_id}}
"paid"                    →  {{updateData.data.status}}