Collected records are a list of records that an action gathers during a run (one action finds the records, and later actions work on all of them). Collecting is meant to help you act on many records at once, without starting a separate run for each one.
You can use collected records for many things, including:
Emailing every tenant whose lease ends this month.
Setting the status of all open tasks in a project to
Donewhen the project closes.
Note:
A collecting action returns at most 1,000 records. If more records match, Tape cuts the list off at 1,000 without a warning. Tape keeps one list per database app, so a second search in the same database adds to the list.
The list exists only during the run. The next run collects again.
Collect records
Collecting is always the first step. These actions put records into a list:
Search for recordsfinds records in a database app. Add filters to narrow them down.Get viewtakes the records of a view in a database app.Get relatedfinds records that are connected to the current record. UseAdd followto continue from the related records to the next database.Get related for collecteddoes the same for every record in a list that you've already collected.
To collect records:
Open the automation and select
Add action.Choose
Search for records,Get view, orGet related.Select the database. For
Get view, also select the view.For
Search for records, selectAdd filterand set the conditions, for exampleStatusisOverdue.Select
Save changes.
To limit the list, open the menu on Search for records or Get view and switch on Limit results. The action then reads and limit results to, followed by a number, which starts at 1.
Use the list
Once a list exists, the actions for collected records can use it. In their first setting, Select collected records, choose the list. If the dropdown shows No results, no action above collects records yet.
Update collectedchanges fields on every record in the list.Comment on collectedadds the same comment to every record.Send email to collectedsends one email per record.Filter collectedremoves records that don't match your conditions.Sort collectedputs the list in order. SelectAdd sortto choose a field and a direction.Rollup collectedcalculates a value across the list, for exampleCount all,Count empty, orSum.Clear collectedempties the list.Call automation on collectedstarts another automation for every record.Loop actionsruns several actions for each record, one after the other.
Use Loop actions when you need several steps for each record. Use an action for collected records, such as Update collected, when one step is enough. Learn more about limits →
In Update collected, Comment on collected, and Send email to collected, insert fields under Collected / <record name>. Tape fills them with the values of each record in turn. After a collecting action, the values of the first record in the list are also available under Collected / <record name>. This is useful when you only expect one record.
You can also insert values from a list into an email or a PDF, for example to build a table. Learn more about building tables →
Let's look at an example
Let's say your solar company wants to remind customers whose installation is overdue. Here's how:
Set the trigger to
On a scheduled time or intervaland run it every Monday at 8:00 AM.Select
Add action→Search for recordsand choose theInstallationsdatabase app.Add the filter
StatusisOverdue.Select
Add action→Sort collectedand sort byDue date.Select
Add action→Send email to collected. Choose the list from step 2 and insert the customer's email inTo.Select
Save changes.
Every Monday, each customer with an overdue installation gets one email.
Collected records errors
The list is shorter than expected. A collecting action stops at 1,000 records. Add filters, or split the work into batches. Learn more about batches →
Select collected recordsshowsNo results. Add a collecting action above the action that needs the list.A run stops after a while. A run ends after three minutes, or after 1,000 actions. Large lists can reach one of these limits. Learn more about limits →
Test, pause, or edit collected records
Use
Manual runon a test record to see which records an action collects. Learn more about testing →To change what is collected, open the automation, select the collecting action, change the database app, view, or filters, then select
Save changes.To use a list for something else, add another action below that uses it.
Learn more
FAQs
How many records can I collect?
How many records can I collect?
Up to 1,000 per collecting action. Tape cuts off anything beyond that, even if you set a higher number in Limit results, and doesn't show a warning.
Can I collect records from more than one database app?
Can I collect records from more than one database app?
Yes. Add one collecting action per database. If two actions collect from the same database, they fill the same list for that database, so later actions get all records. Get related replaces the list instead. You can't name lists. Use Clear collected between them to start over.
Does a list change if records change during the run?
Does a list change if records change during the run?
No. The list holds the records as they were when collected. After Update collected, the list holds the updated records.
Can I update only some of the records in a list?
Can I update only some of the records in a list?
Yes. Add Filter collected before Update collected. It removes the records that don't match, and the next action works on the rest.
Can I collect more than 1,000 records?
Can I collect more than 1,000 records?
Not in a single action. Collect them in batches, for example by filtering on a date range or status, and call another automation for each batch.
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Full reference: Actions in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
