microsoft/power-platform-skills / plugins/code-apps/skills/add-teams
add-teams
VerifiedAdds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Add Teams
Workflow
- Check Memory Bank → 2. Add Connector → 3. Configure → 4. Build → 5. Update Memory Bank
Step 1: Check Memory Bank
Check for memory-bank.md per shared-instructions.md.
Step 2: Add Connector
Get the connection as described in connector-reference.md.
CLI 1.3.0+ (PA_INLINE_CONNECTIONS=yes): tell the user that adding Teams may create a connection with their account, then run the add without -c and handle the result with the outcome table in connector-reference.md:
pa app add data-source --connector teams --non-interactive
Older CLIs: run /list-connections to find the Teams connection ID (if none exists, create one with pa connection create as described in connector-reference.md), then:
pa app add data-source --connector teams -c <connection-id>
Step 3: Configure
Ask the user what Teams operations they need (send message, post to channel, etc.).
PostMessageToConversation -- sends a chat message via Flow bot:
await TeamsService.PostMessageToConversation({
"Post as": "Flow bot",
"Post in": "Chat with Flow bot",
"Post message request": {
recipient: "<recipient-upn-or-id>", // UPN or Entra object ID
messageBody: "<p>HTML message</p>", // HTML format
isAlert: false,
feedbackLoopEnabled: false
}
});
Use Grep to find specific methods in src/generated/services/TeamsService.ts (generated files can be very large -- see connector-reference.md).
Step 4: Build
npm run build
Fix TypeScript errors before proceeding. Do NOT deploy yet.
Step 5: Update Memory Bank
Update memory-bank.md with: connector added, configured operations, build status.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |