Make.com Integration with Airtable - Scheduled Notification Trigger Failing Due to Time Zone Problems

Other Questions Airtable
1

Issue Description:

Hey everyone!

I’m having trouble with a Make.com and Airtable setup for sending notifications 15 minutes before events. Users input time data (IST timezone) into a column named Event_Time.

My Airtable formula calculates the notification time like this:

IF(
  {Event_Time},
  DATETIME_FORMAT(
    DATEADD(
      DATETIME_PARSE({Event_Time} & ' +05:30'),
      -15,
      'minutes'
    ),
    'YYYY-MM-DDTHH:mm:ss\Z'
  )
)

In Make’s “Find Records” module, I’m using:

AND(
  IS_AFTER(DATETIME_PARSE({Notification_Time}), DATEADD(NOW(), -15, 'minutes')),
  IS_BEFORE(DATETIME_PARSE({Notification_Time}), DATEADD(NOW(), 1, 'minutes')),
  NOT({Alert_Sent})
)

The setup seems right - both Notification_Time and Make’s NOW() function use UTC format, and the timing calculations appear correct. However, the search isn’t finding any matching records when it should.

Has anyone dealt with similar timezone issues in Make.com automations? Any suggestions would be great!

2

Had the same issue with Make.com and timezones last year. Your Airtable formula might be adding ‘Z’ but the stored value isn’t actually UTC despite how it looks. Make.com gets picky about datetime strings from Airtable. Drop the ‘\Z’ from your Airtable formula and use Make’s FORMATDATE function in your filter instead - keeps timezone handling consistent. Also check your Airtable base timezone settings. I found mine was set to a different timezone than I expected, which messed up everything. One more thing - verify if Make.com is getting datetime values as strings or datetime objects. Add a text output to log what’s actually being compared. Sometimes there are formatting mismatches you can’t see from just the formula.

3

Had the same issue with Make and Airtable datetime comparisons. Make’s DATETIME_PARSE function was screwing up the timezone conversion for me. Skip parsing the datetime in your filter - just use the raw Airtable value and let Make handle the comparison itself. Also check if your scenario’s actually running every minute. Mine was set to 15 minutes and I was missing records because of the gaps. I’d add buffer time to your search window - maybe 5-10 minutes instead of 1 minute to catch scheduling delays. What really helped was creating a test record with known values and manually checking what Make received vs what I expected.

4

had the same timezone headache. try removing the \Z from your airtable formula - make sometimes gets confused by the literal z. also check that your scenario’s running in the right timezone under settings.