Team priorities that re-rank themselves every two hours

The scenario gathers new signals, meeting decisions, urgent emails and blockers, rebuilds the task order and tells the team only when it actually changed.

  • The task order always reflects what happened in the last few hours
  • Three scoring passes: impact, urgency, final rank
  • You're only pinged when something actually changed — no noise
  • Every re-rank is kept in history
Set it upScriptera

How it works

To connect AWS DynamoDB and Microsoft Teams, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Rerank Trigger
  2. Then: Read Settings
  3. Check: Check Demo Mode
  4. If yes: Get Open Priorities
  5. Then: Sort Priorities
  6. Then: Limit Top 20
  7. Then: Normalize Priorities
  8. Check: Merge Context
  9. Then: Build Priority Matrix
  10. Then: Remove Duplicates
  11. Then: AI Pass 1 - Impact
  12. Then: Parse Impact
  13. Then: Set Impact Scores
  14. Then: AI Pass 2 - Urgency
  15. Then: Parse Urgency
  16. Then: Set Urgency Scores
  17. Then: AI Pass 3 - Final Rank
  18. Then: Parse Ranking
  19. Then: Compare Rankings
  20. Check: Any Changes
  21. If yes: Build Change Summary
  22. Then: Format Slack Update
  23. Then: Post Ranking Change
  24. Then: Create Audit Log
  25. If yes: Prepare Update Batch
  26. Check: Batch Updates
  27. Then: Update Notion Priority
  28. If no: Slack No Changes
  29. If yes: Get Recent Signals
  30. Check: Filter High Signals
  31. Then: Normalize Signals
  32. If yes: Get Meeting Decisions
  33. Then: Normalize Meetings
  34. If yes: Get Urgent Emails
  35. Check: Filter Urgent Emails
  36. Then: Normalize Emails
  37. If yes: Get Blocked Actions
  38. Check: Filter Overdue Actions
  39. Then: Normalize Blockers

You can launch this AWS DynamoDB + Microsoft Teams integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios