Hey community!
Today we are officially launching several brand new automation features to help you build more robust workflows.
- Automation trigger: at a scheduled time
- Automation action: find records
- Rendering records as a list
One of the best applications for these new features is making an email digest, where you can schedule a time to send a list of records that match the conditions you set. To see how all of these features come together to build an email digest, see this support article.
Below you’ll find a shorter summary of each new feature.
At a scheduled time trigger
The “At a scheduled time” trigger allows you to trigger (or run) an automation at a pre-designated date and time. You can choose to run at regular intervals (in hours or minutes) or at set time on specific days of the week.
Find records action
This action will look for records matching conditions that you can specify within the action settings. If a record that matches the conditions is found, you can add a following action that uses the record data to perform some other action.
Render records as a list
This new feature lets you use the records found in the “find records” trigger and render them as a list within an email. You can select which fields to include, and render them as a list of records in the email.
Share your feedback
Our developers would love to hear your feedback around this feature, so feel free to comment in this topic with any questions or ideas on how we can improve.
Thank you for the new automations. excited to see what i can do with them.
Just a quick question. why is it the only dynamic data we can use to find records with are record ids and dates? the options we need for the others are all there but you cant actually use them? specifically i need something that says ‘When a record matches conditions, find records in the X table where Y field = Z field, update the original record with the values from the matching records’ ideally it would then delete the records it merged from but i know that isnt a thing. (sort of an automatic dedupe)
Same sort of question with some sort of monthly or yearly interval trigger. the intervals provided dont seem particularly useful to me but it may just be my use case. way more often do i need something that says on the 15th of every month create this record.
Yay!!! Very exciting additions!! :smiling_face_with_sunglasses: :partying_face: 
Thank you for the new automations. excited to see what i can do with them.
Just a quick question. why is it the only dynamic data we can use to find records with are record ids and dates? the options we need for the others are all there but you cant actually use them? specifically i need something that says ‘When a record matches conditions, find records in the X table where Y field = Z field, update the original record with the values from the matching records’ ideally it would then delete the records it merged from but i know that isnt a thing. (sort of an automatic dedupe)
Same sort of question with some sort of monthly or yearly interval trigger. the intervals provided dont seem particularly useful to me but it may just be my use case. way more often do i need something that says on the 15th of every month create this record.
Hi Rebecca – do you mind sharing more details about when the find records dynamic input didn’t work? Specifically, in “find records in the X table where Y field = Z field” what are Y and Z?
I would like the ability to format the “List of records” in the email action as a grid, the same way as you can do with the “Send records as email” right-click option
I would like the ability to format the “List of records” in the email action as a grid, the same way as you can do with the “Send records as email” right-click option
I second this motion! 
Great idea @Heather_Cameron! I’ve shared that with the team that built this feature :thumbs_up:
Hi Rebecca – do you mind sharing more details about when the find records dynamic input didn’t work? Specifically, in “find records in the X table where Y field = Z field” what are Y and Z?
When you web clip you create a new record and then dedupe it to the old record. i use a Job ID to match. they look like this. 
i need a way to copy the values from the web clipped record into the master record without having to dedupe. theres far too many to dedupe everything. problem is as it stands i cant just say find records that match in the job id field.
the insert option is never made available these things are just greyed out or lead you down a click hole that leads to nowhere.
When you web clip you create a new record and then dedupe it to the old record. i use a Job ID to match. they look like this. i need a way to copy the values from the web clipped record into the master record without having to dedupe. theres far too many to dedupe everything. problem is as it stands i cant just say find records that match in the job id field.
the insert option is never made available these things are just greyed out or lead you down a click hole that leads to nowhere.
@Rebecca_Elam - I believe the issue you are highlighting here is that the values of formula fields cannot be selected from a record list to enter into an email automation action, only the length of the values in the formula field, which is… less than useful.
@Rebecca_Elam - I believe the issue you are highlighting here is that the values of formula fields cannot be selected from a record list to enter into an email automation action, only the length of the values in the formula field, which is… less than useful.
in a roundabout way yes that is the underlying problem. i guess thinking about it now all the fields that this is happening with are just formula fields with a pretty cover. lookups rollups and linked records
Ah I see, thanks for the details. The reason you can’t insert “JOBS” into the filter for the second Find Records is that it’s coming from the output of the previous Find Records action, which outputs a list of records. So if the Find Records action outputs 3 records, you will end up with a list of the JOBS cell value taken from each record and combined into a list, e.g. .'job1', 'job2', 'job3']. The filter in the second Find Records expects a single string, so it’s not allowing you to insert the list. We have plans to make it easier to convert from a list to a string, but in this case I’m not sure that will help either. It sounds like what you actually want is to find all records where SUBMITTED is OWNER ADDRESS CORRECTION and then loop over each record, then for each record find records in another table and take an action on those. This is not currently supported in automations because automations don’t support loops, but you can do it with a scripting action.
That’s a great step in the proper direction, as previous methods of creating digests with Zapier were hacky and unreliable.
Is sorting in the roadmap? The current order appears to be record creation which really makes no sense for task-keeping use cases.
A nice feature would be to inherit filters & sorting from specified views.
Ah I see, thanks for the details. The reason you can’t insert “JOBS” into the filter for the second Find Records is that it’s coming from the output of the previous Find Records action, which outputs a list of records. So if the Find Records action outputs 3 records, you will end up with a list of the JOBS cell value taken from each record and combined into a list, e.g. .'job1', 'job2', 'job3']. The filter in the second Find Records expects a single string, so it’s not allowing you to insert the list. We have plans to make it easier to convert from a list to a string, but in this case I’m not sure that will help either. It sounds like what you actually want is to find all records where SUBMITTED is OWNER ADDRESS CORRECTION and then loop over each record, then for each record find records in another table and take an action on those. This is not currently supported in automations because automations don’t support loops, but you can do it with a scripting action.
Hey @Shrey_Banga
But the filter from Find Records doesn´t work also with a “single string” I tried using a formula and a rollup (with concatenate); those fields aren´t a list (array), but it doesn´t give me the option to include them as a filter.
(https://cdn.zappy.app/2f03bf1ceb0dd1886d657079eb18f580.gif)
g2f03bf1ceb0dd1886d657079eb18f580.gif (782×516) (zappy.app)]
This is amazing! Will there be different time intervals coming available soon? (Namely being able to send something once or twice a month rather than on a weekly basis).
Also, have you considered adding the option to send all records in a view rather than needing to use the find records function to send a list of records? Having that available as an action would let me transfer my current digest system over from Zapier, which would be awesome.
I would like the ability to format the “List of records” in the email action as a grid, the same way as you can do with the “Send records as email” right-click option
Also would be great if we could use bullets to sum up the records in the digest, with sub bullets for their details.
This is amazing! Will there be different time intervals coming available soon? (Namely being able to send something once or twice a month rather than on a weekly basis).
Also, have you considered adding the option to send all records in a view rather than needing to use the find records function to send a list of records? Having that available as an action would let me transfer my current digest system over from Zapier, which would be awesome.
Hey @Alyssa_Buchthal! I can’t speak to new time intervals coming soon, but we’ll definitely update the community if we do release them in the future.
As for a way to send records in a view, are you more interested in sending records that are more formatted like the grid view? That’s something we’re actively looking into so I wanted to see if that would fit what you had in mind.
Hey @Alyssa_Buchthal! I can’t speak to new time intervals coming soon, but we’ll definitely update the community if we do release them in the future.
As for a way to send records in a view, are you more interested in sending records that are more formatted like the grid view? That’s something we’re actively looking into so I wanted to see if that would fit what you had in mind.
Yeah! Currently I have an email digest that I’m using Zapier to send. There’s a list of people it might be sent to and with Zapier I filter by each person so their relevant records are in one single view, and then send a digest of that view on a set time basis. I could also use the people’s names as a field and then use logic paths to direct records to one digest or another based off of that field as a filter. It would be great if, rather than setting up 3 automations in AT, I could use logic paths within a single automation, or use a time trigger to send a digest of each view on a set basis.
Yeah! Currently I have an email digest that I’m using Zapier to send. There’s a list of people it might be sent to and with Zapier I filter by each person so their relevant records are in one single view, and then send a digest of that view on a set time basis. I could also use the people’s names as a field and then use logic paths to direct records to one digest or another based off of that field as a filter. It would be great if, rather than setting up 3 automations in AT, I could use logic paths within a single automation, or use a time trigger to send a digest of each view on a set basis.
Ah that makes sense @Alyssa_Buchthal. What we’re working towads wouldn’t exactly fit the need you described, but would allow you to create a digest with more of a grid view (as opposed to the current vertical “list” view).
Hi everyone,
We just released an update to the “send record” functionality - you can now send records as an HTML grid in addition to the previous “list” format.
Here’s an example of what that could look like within an email:
This new addition has just started rolling out across all of our customers, so it should be available to you soon. You may need to refresh your webpage to see it.
You can learn more about the new functionality in this support article.
This is BIG! Thank you!
Edit:
Just tested this new functionality and my formula fields (formatted as number) come in without decimal values?
This is BIG! Thank you!
Edit:
Just tested this new functionality and my formula fields (formatted as number) come in without decimal values?
Hi @Mariusz_S,
I’ll check with our engineers about this and let you know when I learn more.
This is an amazing addition!
I have a question though, is there a way to add multiple grids and filter the content of the grids by one of the columns?
There is a way to do this! Start by adding a second “Find records” action to your automation flow. For each individual “Find records” action you can set different filter criteria (just like for a view) to only find records that match your filter conditions.
Then, you can insert records as a grid using each of these separately. Here’s how that might look when using the “Send email” action. Notice that each HTML grid is using a different “Find records” action step from above.
Then, run a test to make sure the right records are being displayed. Here’s an example of two grids in a received email.
Hope that helps Sara!
There is a way to do this! Start by adding a second “Find records” action to your automation flow. For each individual “Find records” action you can set different filter criteria (just like for a view) to only find records that match your filter conditions.
Then, you can insert records as a grid using each of these separately. Here’s how that might look when using the “Send email” action. Notice that each HTML grid is using a different “Find records” action step from above.
Then, run a test to make sure the right records are being displayed. Here’s an example of two grids in a received email.
Hope that helps Sara!
That is perfect, thank you so much!
One follow up, is it possible to sort the grid by a specific column variable?
That is perfect, thank you so much!
One follow up, is it possible to sort the grid by a specific column variable?
You’re welcome! Right now there isn’t a way to set a custom sorting criteria, but that is something our team is considering for future enhancement.
