Hey @Marcin11!

There are two different aspects to your question:
1. Trigger
2. Script

Regarding the Trigger. What do you exactly mean by "specific time trigger automation "?
Do remember that you can select the Trigger "At a scheduled time..", and you can furthermore select the corresponding time/frequency. See image below.

If you go this route, you'll probably want to have an action block after the Trigger which finds records which meet certain criteria, then loops through each record found, and runs the script below for each record found.

Alternatively, you can make the automation Trigger "when a record matches conditions".. By using certain date/time formulas, you can set a condition that will be met when a specific date/time is met (e.g. 2 days after record Creation Date or whatever). As the immediate next action, you'll run the script below on your automation.

Regarding the Script, you'll want to use the following script. Furthermore, on the left margin of your scripting block, you'll want to have "recordID" as key for your variable, and the value of the RecordID of the record which triggered the automation as the value.

 
Please let me know if this somehow helps, or else feel free to reach out via Private Message or provide further context here!

Mike, Consultant @ Automatic Nation

@Marcin11 

If you're new to Make’s advanced automations & integrations, I’ve assembled a bunch of Make training resources in this thread.

For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Use a 'Find records' action followed by a 'Repeating group' action that uses the results of the 'Find record' as a list:  

This'll let you use each found record's ID inside the script, so you'll be triggering the webhook once per found record

Link to base

Method 1:
Change your Make automation to SEARCH for Airtable records instead of the Webhook+ Get a record Combo.

Method 2: Schedule an automation > Find suitable records > Run a script (command fetch + Make webhook URL)

Method 3: Trigger automation when record matches condition > Run a script (command fetch + Make webhook URL)

For your use case as described, I'd suggest Method 1, but I prefer Method 3 personally.

Hi. Thank you for the solution. It does work somewhat as intended. It triggers a webhook but only once for a random record so it won't generate all the agreements that are meant to come from the AirTable but perhaps I can figure out how to loop through the integration in Make as it only runs once for a radnomly chosen record from the table.

Hi. Thank you for your time. I wanted to create the agreement at a specific time so needed to run an automation at a specific time that would then trigger the webhook in Make which then would generate all the agreements. 

A solution provided below seems somewhat to what you are suggesting and it works in the way of triggering the webhook but it does it only once so only one agreement is generated for a randomly chosen record in the AirTable.

Would you be able to share the date/time formulas approach in greater detail as this might be a solution if I staggered the records in couple of increments of each other so the Make webhook integration could be run until we loop through all the records.

Hmm sounds like your 'Find record' step isn't returning the results you want.  Could you provide a screenshot of the 'Find records' automation step set up, as well as a screenshot of the records you'd want it to find?  That way I can help you figure out what the conditions should be for 'Find record' step

Hi Adam. Thank you for offering to troubleshoot this some more and I'm sorry for a late reply.

Here are screenshots that I think show everything that's needed. The base will have Printed Name and Email there in each record from the go. Rest will be filled once the agreement is filled (I know I've got some more steps to do in another workflow in Make but this should not be a problem).

Hmm, you've set up your automation to look for all records with an 'Email' value and then trigger the webhook once for each record.  You mentioned that it only works only once on a random record, and that sounds like you're not actually running the automation, but testing it instead

Could you confirm that you turned on the automation and triggered it, and when it ran it only ran for one record despite the 'Find record' step finding multiple records?  To trigger the automation manually, try using a checkbox field or something

Hi. I've added a field with a checkbox, and ticked all the fields. The automation was on and when the time of the automation came, only one record got triggered.
I'm not sure if I'm tiggering the automation the way you would like me to do.

Hi again. I think it might be something to do with Make. Once I set up Make webhook to run every minute, the agreements were generated every minute so maybe this is the approach I'd have to use. 

People from Make suggest to use "Watch Records" module but I don't seem to be able to narrow down what I'm doing wrong there too.

Ah, yeah, from your screenshot 'step5', your trigger is still "At scheduled time" and is errored out, which means you aren't triggering the automation?  Could you check the automation history to see if the automation's actually ran before?  And if it has, check the 'Find record' action's results and see whether the repeating group fired for each of the results

It sounds like you've got it working though, and if that's the case you could just leave it heh

Hi Adam. I've checked the history and the automation appears to have run for each record.  And the approach with one minute would not be the cleaniest but it actually did they job.

I was actually do it with the "Watch Record" module in Make once I realise at what step I was going wrong about the workflow. Your approach helped me to learn some more so I really appreciate the time you took to walk me through your approach and I might use in the future in another project!