Microsoft PowerPoint 365
Manages PowerPoint presentations in OneDrive and SharePoint via Microsoft Graph API. Supports full presentation lifecycle: create, open, list, copy, delete, upload, download, and export to PDF. Provides template-based content manipulation — batch replace text placeholders across all slides using key-value maps and replace images by placeholder name or alt text (accepts file paths, URLs, or base64 data). Uses an open/save workflow where presentations are parsed in-memory for editing. Supports slide management including duplication, deletion, and adding slides from layouts. Authenticates via Azure AD client credentials (server-to-server) or OAuth2 delegated flow.
| Namespace | Robomotion.PowerPoint365 |
| Version | 1.2.0 |
| Category | Productivity, Business Software |
| Nodes | 12 |
Nodes
| Node | Description |
|---|---|
| Open Presentation | Opens a presentation in Microsoft PowerPoint 365. |
| Close Presentation | Closes a presentation in Microsoft PowerPoint 365. |
| Save Presentation | Save Presentation — see the properties below. |
| List Presentations | Lists presentations in Microsoft PowerPoint 365. |
| Create Presentation | Creates a presentation in Microsoft PowerPoint 365. |
| Delete Presentation | Deletes a presentation in Microsoft PowerPoint 365. |
| Copy Presentation | Copies a presentation in Microsoft PowerPoint 365. |
| Download Presentation | Downloads a presentation in Microsoft PowerPoint 365. |
| Upload Presentation | Uploads a presentation in Microsoft PowerPoint 365. |
| Replace Text | Replace Text — see the properties below. |
| Replace Image | Replace Image — see the properties below. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
AI Agent tools
11 of these nodes are exposed as tools an AI Agent can call directly:
Open Presentation, Close Presentation, Save Presentation, List Presentations, Create Presentation, Delete Presentation, Copy Presentation, Download Presentation, Upload Presentation, Replace Text, Replace Image.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.