# Update Data

This action updates data in a variable or table to a new value.

New data can be empty - this will clear the existing data and set it to an empty value.

#### **Example 1: Mark leads as qualified if their description contains certain keywords** 

Imagine you saved profiles from, for example, LinkedIn to a table called "Linkedin profiles". Now you want to mark all those leads which have keywords "senior", "vp", "director" in their job title as qualified. For this, you can create a column which you can call, for example, "Status" and use this action to update rows with the word "qualified" in the cases where your condition is fulfilled.

This is the workflow set-up:

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FTP49iPjXJLX1CaJ4Kvt1%2FScreenshot%202023-11-21%20at%2015.46.56.png?alt=media&#x26;token=f5de8406-5d8b-4f74-ab71-bbc5779ed5c4" alt=""><figcaption></figcaption></figure>

Loop is set up to iterate over profiles in your table:

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FbHRuRqZrI87fnzgpROBm%2FScreenshot%202023-11-21%20at%2015.47.37.png?alt=media&#x26;token=758e3154-28a0-44b0-b03b-181610d90a7c" alt=""><figcaption></figcaption></figure>

*Start Condition* is pointing to the column "Job position".

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FKAyRNRF8GgK3fephItMI%2FScreenshot%202023-11-21%20at%2015.48.03.png?alt=media&#x26;token=f49760fd-c205-4941-9df8-cf630b53c398" alt=""><figcaption></figcaption></figure>

*Set Condition* is checking for the aforementioned keywords.

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FxqkRG1e1b1ycdE6bDEQy%2FScreenshot%202023-11-21%20at%2015.49.00.png?alt=media&#x26;token=df3ea271-cf03-4eb1-9aa2-ed33af50aa1c" alt=""><figcaption></figcaption></figure>

Now the column "Status" will be set equal to "qualified" as long as the condition above is met.

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FBUrqU1OuFNIcSiBagDKQ%2FScreenshot%202025-01-02%20at%2007.51.36.png?alt=media&#x26;token=f96c4c36-f97e-421e-bbb1-86c4603c2cf5" alt=""><figcaption></figcaption></figure>

Later, when you continue working with this table, you can set up your TaskBot to only send connection requests to those contacts who have the word "qualified" in the column "Status" or you can delete all disqualified leads (see example here: [#example-remove-disqualified-leads-if-lead-qualification-status-does-not-equal-qualified](https://docs.zerowork.io/using-zerowork/delete-data#example-remove-disqualified-leads-if-lead-qualification-status-does-not-equal-qualified "mention")).

#### **Example 2: Mark leads who received an outreach message with "Message sent"**

A similar popular use case is to mark a message status as processed. Imagine your TaskBot will be sending out automated messages to a list of profiles. You can create a column called, for example, "Status message" and let your TaskBot update it with "sent" every time a DM is sent. Then by adding a condition to skip sending DMs on profiles who have a record "sent" in their "Status message" column, you can make sure that you never send repeated DMs to the same leads.

<figure><img src="https://3220183989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9LcR8XM7TGOzOCDGsCS%2Fuploads%2FJbrfM0muTG1nsnqShNVM%2FScreenshot%202025-01-02%20at%2007.52.21.png?alt=media&#x26;token=83c6601c-0965-48f8-a7ee-83c89db734d5" alt=""><figcaption></figcaption></figure>

#### **Example 3: Set profile visit status to "visited" to avoid visiting same profiles**

Here is a an example of a workflow set-up that checks for status of profile being visited: [#avoid-visiting-same-profiles](https://docs.zerowork.io/using-zerowork/save-web-element/enrich-existing-data#avoid-visiting-same-profiles "mention") (link includes a video tutorial).

### FAQ

#### When I use a table reference, no data is updated, although there is data in the table.

This happens when no dynamic loop is set up to pull rows from the table. Please see the solution here: [when-i-use-data-from-table-no-data-is-being-pulled](https://docs.zerowork.io/using-zerowork/common-problems/when-i-use-data-from-table-no-data-is-being-pulled "mention").

### Video Tutorial 1: Qualify Profiles in a Table or Google Sheet

{% embed url="<https://youtu.be/wfN6Oyle8Ic?si=S04AqsnXpaWlcpRW>" %}

### Video Tutorial 2: Use Update Data to Transfer Data from One Table to Another

{% embed url="<https://youtu.be/dQThS6YyHxI?si=WDPvz4gslLUnMtib>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zerowork.io/using-zerowork/using-building-blocks/update-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.