N8N: On a Schedule Trigger
Starts a workflow at fixed times or intervals, like Unix cron. Missed runs are skipped, not backfilled.
Here I share the best practices I use for the Power Platform tools, drawn from my own experience and plenty of learning from other people's mistakes so I don't repeat them. None of this is set in stone, so adjust it to fit how you work. Consistency matters, especially when several people share a platform. I see it constantly: SharePoint sites with mismatched naming, lists with convoluted names, and flows nobody can follow. When you agree on rules, everyone always knows what something means, and onboarding a new person becomes far easier. Even if you never adopt my conventions, at least write your own down. And even if you work alone, building your own reference makes you think, and you will often spot places where things could be better. That reflection is half the value.
Starts a workflow at fixed times or intervals, like Unix cron. Missed runs are skipped, not backfilled.
Converts a timestamp from a source time zone to UTC using Windows time zone names.
Bundle hundreds of SharePoint writes into a single $batch request to stop hitting throttling limits.
Adds numbers, cells, or ranges into a single total. A single error in the range takes over the result.
Converts text to uppercase, leaving numbers and punctuation untouched. The result is always text.
Checks if a string is an integer.
Add columns to library files so you can filter, sort, group, and find them by metadata instead of folders.
Counts the cells in a range that contain numbers. Ignores text, blanks, and errors.
Starts a workflow when a new email arrives in Gmail. Polls on a schedule; filter by label, sender, or search.
Extracts a substring by position. Supports negative indices; endIndex is exclusive.
Explains why SharePoint's email field is spelled EMail and why the casing breaks your filters
Why I keep ads, affiliate links, guest posts, tracking, and polarizing topics off the site.