Send Reminder Email To Non-Registered QuickBase User 24 Hours Prior To Date

Correct. The caveat is that these users are already captured in our system and have already received triggered notifications for their scheduled appointment. We just want to send a reminder 24 hours before their appointment.

When you say this

The caveat is that these users are ...

But these are not users, then just email addresses, right?

Assuming that is what you meant, then the three choices I see are

1. Make a report of Reminders due to be sent, and make a formula URL button to update a date field to trigger the OPEN Notification and refresh the report with that record gone.  Then the user would receive a morning Subscription email and just mindless click a button on all the records until they are all sent.  So many clicks but pretty mindless and quick.

2. Contract with a QSP like myself to have the same thing done, but by clicking a single button once which would run a script to fire the individual emails by updating a date field on each respective record.  One click.

3. Contract with a QSP like Juiced to install their "Triggers Add On" to run a process automatically each day. No Clicks.

Thanks! Ideally, we won't have any clicks, so I'll have to look into Juiced. If the costs are too high, I'll reach out about the 1-click solution. 

This might be a non-starter if you're sending out appointment information - but do you specifically need to send any detailed information to the end recipient? As in - is it possible to send a generic email to anyone to be reminded that just says hey - appointment tomorrow - call us here if you have an issue - but not include any info specific to their actual appointment? Or do you need it to say 'Hey Kate - appointment tomorrow at 9:00 AM'

If you can send a generic, not targeted email - you could use Automations to run a daily scheduled action - and do a bulk-modify to all the records that are currently a day out to send a notification instead of a reminder. The limitation of that, is Automations will then fire off an Import call - which means it will modify them all at once - and send the multi-record version of a native QB notification - which means you can't include record / field specific data. It has to be as generic as it gets.

Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base