Schedule workflows

Feature Requests
1

Being able to create workflows that are time-based. Eg to set up just like workflows fixed on time. Such as that a certain time of the day or a day of the week, etc. should run a workflow with certain actions. Just like we have today with workflows. Or are there any tips on how to build today? For example trigger via zapier to noloco to run a workflow?

1 Like
2

The only way I can think of is e.g.

Have a trigger in zapier that is triggered a certain day (it works) that updates a field in noloco for that record. As well as having a workflow that is set to trigger on changes, thus triggering action in workflow in noloco and for example back to zapier to do some actions


2 Likes
3

That’s a pretty reliable workaround @Phoenix

Scheduled workflows are definitely something we have thought about, but every workflow in Noloco starts with 1 record, so it’s unclear what that would look like for a scheduled workflow

If you could expand on your use-case it would help for sure

4

Scheduled workflows are quite a common request and would definitely be appreciated in Noloco.

Most commonly we find they’re used for daily/weekly/monthly reminders. E.g. a daily summary of tasks you’re working on, or monthly upcoming projects, etc.

1 Like
5

right, I didn’t think that a record is required for that :slight_smile:

But if you could have new type of action button that you can set a time for it to be triggered in a list. e.g. all records in a list are triggered by a timed action which is then linked with a workflow etc? Then you can automate actions on records that is filtered thru a list.

Perhaps this can be done thru make but it would be more effectively within noloco app

Skickat frÄn Outlook för iOS

6

Darragh, I see what you’re saying about the issue with workflows being rooted in a record.

Perhaps these options in a hypothetical scheduled workflow might work?

  • Can choose to root the workflow in 1 record or many records (statically)
  • Can choose to root the workflow in 1 record or many records (dynamically)
  • If the user chooses dynamic, the workflow automatically pulls the records that match a user-defined condition. In other words, when the “Reminder” checkbox is TRUE, that record will be used in the dynamic workflow.
  • If many records are chosen, maybe force a loop as the next action?

Just thinking out loud


7

Picking up on this one.

We often create “daily digest” or “weekly digest” emails for projects.

That’s a clear “scheduled time → find records → send email
” workflow.

2 Likes
8

To add another example:

We have weekly/monthly/quarterly/annual reports we need to generate and distribute to investors and other contacts. We’d like to have a workflow generate new records for these reports at the scheduled interval, so we can track the status, etc.

1 Like
9

This happens over and over again
 +1 for looking at this feature.

This is the use-case for the current client:

A ‘referral’ record has a status - active, won, lost, delayed.

The user wants to delay the referral - they enter a delayed-to date, and the referral is updated to status of delayed.

When the date arrives, the referral needs to return to ‘active’ and a notification needs to be sent to the user.

At the moment we’re having to trigger a webhook when status changes to delayed - push to Zapier.
We store the delayed record in a zapier table of delayed referrals.
Once a day we check the delayed referrals, and any where the date is today we update to active in Noloco, and send the notification. We then delete it from the Zapier table.

If we had a noloco automation that could act based on the value of a date field in a record - today, in the past, etc, we could skip all this.