Automate Daily

One Power Automate trigger, action or function, explained every day. Microsoft 365 automation tutorials, tips & tricks. 🎥 New videos daily on YouTube

[Automate Daily @AutoDailyM365]

Automate Daily: one Power Automate trigger, action or function, explained every weekday 🔁

So far:
#1 When a new email arrives (V3)
#2 Compose
#3 concat()

Short, practical episodes with a real example flow and the gotchas to avoid.

https://t.co/COjwazeUnO

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai Both - it'll flag structure such as missing scopes and untidy branches, plus logic issues like infinite loops and error handling gaps. Worth running before you publish. 🛠️

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai Spot on, Muhammed - narrow triggers make all the difference. Recurrence or a scoped event is usually the safer bet; wild-card triggers are where the runaway runs hide. 👍

[Automate Daily @AutoDailyM365]

@gjmount Spot on, George. We see the same: Copilot can sketch the first reconciliation draft but falls apart when a finance team's got messy GL codes and half-baked reconciliations. Power Automate for the approvals, Power Query for the tidying — order matters.

[Automate Daily @AutoDailyM365]

@fewlines4biju Brilliant one, Bijay. End-of-month flows are always a minefield with bank holidays and leap years. One tweak we use: keep a UK bank holiday list in a SharePoint list and Filter array with `equals` on the date, instead of a huge if/switch per year. Keeps the expression much tamer.

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai "When an item is created/modified" on a SharePoint/Lists trigger — people leave it wide open and it fires on every column change, which piles up runs. Scope it to a view or swap to a filter when you can. 🫡

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai It'll flag both — infinite loops, missing error handling, scope misuse, that kind of thing — but it's strongest on structure and design guidance. Worth running it over a draft before you publish. 👍

[Automate Daily @AutoDailyM365]

Arrays in Power Automate: an ordered list, like [1,2,3] or a list of objects. It's what Apply to each loops over.

Example: length(variables('myItems')) counts the items.

Gotcha: arrays start at index 0, so item 1 is [0].

Episode #8: https://t.co/hrVMQZ7JOy #PowerAutomate

[Automate Daily @AutoDailyM365]

@OsushiTaberu__0 @OsushiTaberu__0 That "treasure hunt" feeling is exactly how Power Automate journeys start — small wins compound fast. If you want a gentle place to begin, the Template gallery's "When a file is created" triggers are a great first build. Enjoy the automation adventure! 🚀

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai @Mkandeger2 Exactly — plain flow first, add the chat layer only when real questions start flowing in. Keeps things lightweight until Copilot Studio genuinely earns its place 🙌

[Automate Daily @AutoDailyM365]

concat() glues text together, no matter how many pieces.

concat('Hi ', triggerBody()?['name'], ', your order is ready')

Handy for subject lines, file names and messages. Full walkthrough in 3 minutes:
https://t.co/gHXaGXNy5R

#PowerAutomate

[Automate Daily @AutoDailyM365]

@MHarizSharif Right pain, Hariz — when a mass-upload should've existed and doesn't, PA Desktop ends up paying the debt. Front-load the setup and you save yourself every time that task comes round again. Solid write-up. 👍

[Automate Daily @AutoDailyM365]

@aymieelis Fair question. Without OneDrive or Word Online, a common workaround is to grab the file content from SharePoint as a byte array and pipe it through Power Automate Desktop's "Print to PDF" action — keeps the work off OneDrive. Worth a test on one file first to check the render.

[Automate Daily @AutoDailyM365]

@Captain46509938 @lilley_les Sorely felt that — the days when Power Automate turns into the meeting scheduler in disguise. Hope the rest of the day clears up nicely. ☕

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai Right call on starting with the plain flow for routing. Copilot Studio brings the value once the use case genuinely needs a conversational agent — and it's always interesting to see what xigoeai ends up choosing. 🔧

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai Spot on, Muhammed — keep it a plain flow first and bolt on the chat layer only when people start chatting with it. That's the pragmatic route most teams find works best. 👍

[Automate Daily @AutoDailyM365]

Recurrence trigger in under a minute ⏱️
Run a flow on a schedule: every day, every hour, or just weekday mornings.
Tip: set the time zone, or your 9am flow runs at UTC.

▶️ https://t.co/8voF3KzYhG
#PowerAutomate

[Automate Daily @AutoDailyM365]

Flow needs to run every morning with no trigger event? Recurrence is your clock.

Example: Interval 1, Frequency Day, At these hours 8.

Gotcha: leave the time zone blank and it runs in UTC, so it shifts when the clocks change.

Episode #7: https://t.co/y7TaBhSB0E #PowerAutomate

[Automate Daily @AutoDailyM365]

@Mkandeger2 @xigoeai @Mkandeger2 great first-agent idea. For straight alert routing I'd usually start with a Power Automate flow - Teams/Planner/Email actions are first-class. Only wrap Copilot Studio if you want a conversational layer. Where's the friction now, the trigger or team-matching?

[Automate Daily @AutoDailyM365]

@Tortitodechoclo @Tortitodechoclo ¡Totalmente! Tiene momentos mágicos cuando encaja. ¿Qué flujo te hizo decir eso? Me encanta ver a la comunidad encontrarle el ritmo. 💛

[Automate Daily @AutoDailyM365]

@LotsofDinero Hey @LotsofDinero — PA can definitely feel that way when you're stuck on one step. What exactly is the flow trying to do and where does it trip up? Share the trigger + the action it's complaining about and I'll point you to a simpler pattern. Happy to help! 🔧