Skip to main content
If your leaders use Microsoft 365, this recipe posts new waiting-list applications to a Teams channel every morning. It uses a Power Automate cloud flow.
The HTTP action is a premium connector. It needs a Power Automate Premium licence, or a Microsoft 365 plan that includes premium connectors. Without it, use n8n or Zapier for the same job.

​
1. Start the flow

1

Create a scheduled flow

In Power Automate, choose Create → Scheduled cloud flow. Call it Scoutworks waiting list. Set it to repeat every 1 day, and set a start time of 07:00. Choose Create.
2

Add the HTTP action

Choose + → Add an action, search for HTTP and choose HTTP. Fill it in:
  • URI: https://api-demo.scoutworks.app/api/v1/waiting-list?status=received&limit=200
  • Method: GET
  • Headers: Authorization → Bearer followed by the key, for example:
3

Keep the key out of the run history

Open the HTTP action’s Settings. Turn on Secure inputs and Secure outputs. The run history then hides the key and the names. Do the same for the Filter array and Post message actions that you add below, because they also handle names.

​
2. Keep only yesterday’s applications

1

Add a Filter array action

Add the Filter array action (under Data Operation).
  • From: choose Expression and enter body('HTTP')?['data']
  • Filter query: choose Edit in advanced mode and enter:
This keeps the applications from yesterday, midnight to midnight (UTC). Each day has fixed edges, so a run that starts late neither misses an application nor posts one twice.

​
3. Post to Teams

1

Add a loop

Add Apply to each. For Select an output from previous steps, choose the Body of Filter array.
2

Post a message

Inside the loop, add Microsoft Teams → Post message in a chat or channel. Post as Flow bot, in your leaders’ channel. For the message, choose Expression and enter:
Choose Save, then Test → Manually. The demo group has applications from many days ago, so the first test may post nothing. To see messages, change addDays(utcNow(), -1) to addDays(utcNow(), -365) for one test, then change it back.

​
4. Switch to your group

In the HTTP action, change api-demo.scoutworks.app to api.scoutworks.app, and replace the sandbox key with your own. Your key needs the waiting-list:read scope.
The key is saved inside the flow. Anyone who can edit the flow can read it. Do not share the flow, and create a key with only the scope it needs. If you must share the flow, keep the key in Azure Key Vault and read it with the Azure Key Vault action instead.

​
Limits

  • One page. The flow reads the first 200 applications at received, the first stage. Once a leader moves an application on, it leaves that list. A group rarely has more than 200 at that stage.
  • Other lists. Change the URI to read another list. The API reference lists every endpoint and field.
  • Errors. If the key stops working, the HTTP action fails, and Power Automate emails the flow’s owner. See Errors for what each code means.