Skip to main content

How to update and add a row in Tables

Manage individual extractions directly from your Table with quick actions. Update parameters, retry failed tasks, and add new rows for on-demand extraction without leaving your Table view.

M
Written by Melissa Shires
Updated this week

Quick actions in Tables

In Tables you can trigger the following actions:

  • Update Row: re-run an extraction with the same parameters.

  • Add Row: create a new extraction task.

πŸ’‘ You can only update or add a row in the Main tab of any trained robot.

Update Row: Re-run a task

The Update Row action lets you re-run any extraction without changing parameters. This is perfect for:

  • Retrying failed extractions

  • Refreshing your data for a specific URLs or input parameter

How to update a row

  1. Find the extraction task in your Table.

  2. Locate the Update Row button in the actions column.

  3. Click to re-run this task.

  4. Your robot will automatically run to extract the trained dataset.

Add Row: Trigger new extractions

You can also add a new data extraction task directly from Tables. This is perfect for if you want your robot to extract data from:

  • Another URL, ex: scrape details from a new product page

  • Different input parameters, ex: extract search results from a different search term.

How to add a row

  1. Click Add Row above your Table

  2. Enter required parameters:

    • Origin URL

    • Input parameter

  3. Click Start extracting data

  4. Task queues to start running immediately.

Common uses

Ad-hoc additions

  • Add missed URLs

  • Include new pages

  • Fill gaps in data

Different parameters

  • Try various search terms

  • Experiment with limits

Using quick actions effectively

For failed extractions

  1. Filter by Status = Failed

  2. Review error types in History

  3. Update Row on temporary failures

For data updates

  • Update Row for specific products or new items

  • Refresh time-sensitive data

  • Check for changes manually

  • Test additional URLs or input parameters before bulk runs

Did this answer your question?