Skip to main content

Update collected records action

Update every record in a list you collected earlier, for example mark all paid invoices of a month as archived, in one step instead of one loop run per record.

Written by Leo

Update collected is an action that changes fields on all records in a list of collected records. In the action list, its description reads Update all collected records. It's meant to help you change many records at once after an earlier action collected them, without building a loop.

You can use this action for many things, including:

  • Archiving all paid invoices of a month when the month is closed.

  • Cancelling all open tasks of a project when the project is stopped.

The action Update all collected records in Expenses below Search for records, with Add field

Note:

  • Collect first. Update collected works on records that an earlier action collected, for example Search for records, Get view, or Get related. Without a collection, Select collected records shows No results.

  • Each collecting action returns up to 1,000 records. Every updated record counts as one action, and a run can use up to 1,000 actions, so update large lists in batches.

  • It changes every collected record. With Set value or Set option, each field you add replaces the current value on every collected record.

Who can use the Update collected action?

  • Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • To add or change this action, you need to be a workspace admin of the workspace the database app is in. You also need full access to every database the automation uses.

Add the Update collected action

To update collected records from an automation:

  1. Open the database app and click the automations icon in the top bar (tooltip Create and view automations). The icon is only there for workspace admins, and not on mobile.

  2. Open an automation, or select New automation and choose a trigger.

  3. Add an action that collects records, for example Add action → Search for records.

  4. Select Add action → Update collected. The step appears as Update all collected records.

  5. Next to in, select the collection you want to update. Tape preselects the nearest collection above this action. Without a collection, it reads Select collected records.

  6. Select Add field. Tape adds a row with the first field of the database. Select the field name and choose the field you want to change.

  7. Enter the new value. The menu next to the field depends on the field type, for example Set value or Set option. It also has Calculation and an option to clear the field.

  8. Add more fields if needed, then select Create automation for a new automation, or Save changes for an existing one.

Adding Search for records and then Update collected in an Expenses automation: selecting Update collected, which reads Update all collected records in Expenses, selecting Add field, changing the field Expense to Approval note, and typing Checked by finance

Update collected settings

  • Select collected records: the collection to update. The list shows the collections created by actions above this one. Lists are named after the database app, for example Invoices. Actions that collect from the same database share one list.

  • Add field: adds a row with the first field of the collected database. Select the field name to choose another field. Add one row per field you want to change.

  • A value for each field: enter text or numbers, choose an option, date, person, or record, or insert record values by typing @. The placeholder in the text box is Value. Fields with several values also offer adding or removing values, for example Add options and Remove options. To give each record its own value, insert fields under Collected / <record name>. Tape fills them with the values of each record in turn.

Under the action's menu, Settings has these options:

  • Author: who the change is attributed to. If you don't choose one, the change is attributed to the automation itself. Open •••, then select a person under Author. You can choose the automation (the default), a member of the workspace, or a person value such as Created by.

  • Silent: makes the update without sending notifications. It's off when you add the action.

  • Trigger automations: lets the updates start other automations. It's off when you add the action.

  • Trigger webhooks: lets the updates send outbound webhooks. It's off when you add the action.

The menu also has Continue on error, Deactivate, Turn into, Duplicate, and Remove. Learn more about action settings →

Let's look at an example

Let's say your finance team closes every month and wants all paid invoices of that month archived. Here's how:

  1. Set the trigger to When a record is updated in a "Month end" database app and select the field Status.

  2. Add the filter Where Status Has changed to "Closed".

  3. Select Add action → Search for records, select the database Invoices, and add a filter so only invoices with the status "Paid" are collected.

  4. Select Add action → Update collected and select the collection from step 3.

  5. Select Add field, choose Note in the new row, and enter "Archived at month end".

  6. Select Create automation.

When a month is set to "Closed", every paid invoice gets the note "Archived at month end".

Update collected errors

  • If the step fails, the run shows the step and its message in the automation's runs. Open the automation and click ▷ (View all runs) at the top, or use cmd/ctrl + 1. Each run shows its status, for example Success; select a run to see every step. For all automations, open Runs in the Automation Center and filter by App, Automation, or Status.

  • If Select collected records shows No results, add a collecting action above this one.

  • If a collection is empty at run time, the step finishes without changing anything.

Test, pause, or edit the Update collected action

  • Manual run runs the automation once. Under Run on, select the records, then select Start run, or Save and start run if you have unsaved changes. The collected records are changed for real.

  • New automations you create in the editor are Active right away. The status, Active or Paused, sits right below the automation's name in the editor. To pause one, select Active, then select Save changes. The status switches to Paused.

  • To change the action, open the automation, select the Update all collected records step, make your changes, then select Save changes.

Learn more

FAQs

What's the difference between Update collected and Update record?

Update record changes one record, usually the one that started the automation. Update collected changes every record in a collection. Learn more about Update record →

Do I need a loop to update many records?

No. Update collected updates all collected records in one step. Use a loop only when each record needs extra steps. To give each record its own values, insert fields under Collected / <record name>. Learn more about loops →

How many records can I update at once?

A collecting action returns up to 1,000 records, and every updated record counts as one action. If you need to update more, work in batches. Learn more about updating many records in batches →

Can I update only some of the collected records?

Yes! Use Filter collected before Update collected to keep only the records that match a condition. Learn more about filtering collected records →

Will the updates start other automations?

Only if Trigger automations is on in the action's Settings.

Are there other actions I can use?

Yes! Actions can create and update records, add comments, send emails, create PDFs, call other services, and more. See every action in Automation actions →

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: collected_records_update in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?