Check In Presentation
Check in a checked-out PowerPoint DriveItem and make its version available according to the SharePoint/document-library configuration. Microsoft Graph documents no atomic If-Match/eTag option for this operation.
Create, find, inspect, fill, edit, format, share, preview, version, copy, upload, download, organize, and delete Microsoft PowerPoint files through Microsoft Graph and OneDrive, including slide, shape, chart, comment, and geometry workflows.
Check in a checked-out PowerPoint DriveItem and make its version available according to the SharePoint/document-library configuration. Microsoft Graph documents no atomic If-Match/eTag option for this operation.
Check out a PowerPoint DriveItem where its SharePoint/document-library configuration supports checkout, preventing others from editing and hiding changes until check-in. Microsoft Graph documents no atomic If-Match/eTag option for this operation.
Start an asynchronous Microsoft Graph copy of a PowerPoint presentation. A successful result means only that Graph accepted the submission; it does not mean the copy completed or ultimately succeeded. The action never returns the bearer-equivalent Location monitor URL. Discover the result by destination and filename with FIND_PRESENTATIONS. conflict_behavior is unsupported on OneDrive Personal. To preserve all versions, omit name and rename the copy after discovery.
Submit a PowerPoint presentation copy with a required unique filename, then boundedly search the resolved destination folder for an exact-name candidate. Search results cannot be correlated to the copy request, so a discovered candidate is returned as discovered_unverified and may belong to another writer. The bearer-equivalent Graph monitor URL is never returned or read. An exact-name search result is returned only as an uncorrelated candidate, never as confirmed completion, because Graph's secret monitor URL is not exposed or consumed. A timeout or indeterminate result is not proof of failure: verify the destination before retrying. All-version-history copies require the asynchronous COPY_PRESENTATION workflow because Graph does not safely combine that option with a discovery name.
Create a folder for PowerPoint files in the current or an explicitly selected accessible drive.
Create a bounded macro-free PPTX from one to 50 structured slides containing titles, plain text, nested bullets, rectangular tables, uploaded PNG images, and optional speaker notes. The generated Open XML package, relationships, and semantic readback are validated locally before exactly one Microsoft Graph upload. Limits include 500 content blocks, 500,000 text characters, 10,000 line breaks, 2,000 table cells, and 20 PNGs (10 MiB each, 25 MiB compressed and decoded in aggregate); the final package is limited to 50 MiB.
Create or return a view or edit sharing link for a PowerPoint presentation in the current or an explicitly selected drive.
Move a folder to the Microsoft Graph recycle bin after a metadata preflight proves the DriveItem has a folder facet. Recycling a nonempty folder removes the entire descendant tree from its current location. Files are rejected. The preflight eTag is used for a concurrency-safe delete when available.
Move a PowerPoint presentation to the Microsoft Graph recycle bin. This action does not permanently erase the file. It can require a matching eTag or cTag and can send Microsoft's documented shared-lock or checkout bypass preferences.
Download a PowerPoint file in its original format or export it as PDF or JPG. Export conversion is not presentation editing and accepts source files up to 2 MB.
Verify that the selected DriveItem is a PPTX, then download one retained previous version as a bounded PPTX file. Non-PPTX items are rejected before content download. Use LIST_PRESENTATION_VERSIONS to obtain a version ID, but do not use its first newest/current entry: Microsoft Graph refuses current-version content here. Use DOWNLOAD_PRESENTATION for the current version.
Create one presentation from an existing designed PPTX template by replacing unique literal {{tokens}} simultaneously across reachable slides and speaker notes. The template is downloaded and its eTag is rechecked before one create upload; no intermediate provider copy is created. Every requested token must match.
List a folder or search a drive and return only PowerPoint files. Omit search_text to browse folder_id; provide it to search the full drive. A page can contain no matching files while has_more remains true.
Return the signed-in user's default OneDrive ID and basic owner, type, and quota details. Use the drive ID to target other accessible-drive actions explicitly.
Return metadata for one PowerPoint file by item ID, including its current eTag for concurrency-safe updates.
Read bounded, text-first semantic content from a current macro-free PPTX, including slides, shapes, text, safe hyperlinks, alt text, image metadata, tables, and speaker notes. Default budgets are 100 slides, 200 shapes per slide, 100 paragraphs per shape, 100 runs per paragraph, 20,000 characters per shape, 100,000 total characters, 5,000 structural elements, and 100 comments per slide. Maxima are respectively 500, 1,000, 500, 500, 100,000, 500,000, 20,000, and 200. For ordinary reads, use slide_numbers for only the needed slides and lower budgets instead of reading a whole large deck. Formatting, geometry, supported chart data, and modern comments are opt-ins. Uses eTag consistency and never returns layouts, package bytes, raw XML, unsafe external targets, or preauthenticated URLs.
Download and validate the current macro-free PPTX, then return its complete bounded slide-layout catalog. Each layout has a unique opaque selector accepted by UPDATE_PRESENTATION_CONTENT add_slide, plus exact human-facing name and matchingName values and safe type/placeholder summaries for duplicate-name disambiguation. Never returns package paths, raw OOXML, package bytes, or download URLs.
Deprecated: return short-lived, human-embeddable UI preview material for a SharePoint or OneDrive presentation, including personal OneDrive. It does not return agent-readable slide content. Agents should use GET_PRESENTATION_CONTENT to inspect content, or DOWNLOAD_PRESENTATION with PDF/JPG output for a rendered artifact. The returned URL is caller-only and bearer-equivalent: never share, log, cache, or persist it.
List generated thumbnail metadata for a PowerPoint presentation. Microsoft Graph represents only the first slide and can return an empty set; it does not provide per-slide thumbnails. Returned URLs are short-lived bearer-equivalent capabilities for the caller only and must not be shared, logged, cached, or persisted.
Retrieve compact metadata for one retained or current version of a PowerPoint file. Use List Presentation Versions to discover retained version IDs.
Grant named people read or write access to a PowerPoint presentation. By default, send_invitation=true also causes Microsoft to send external invitation emails; set it false to grant permission without notifications. A 207 response preserves recipient-level errors and is never reported as complete success.
List retained versions of a PowerPoint file in Microsoft Graph's newest-first order, one provider page at a time. Continue while has_more is true before treating the final version as the oldest retained version. The first entry is current: its metadata is readable, but Graph refuses its content through DOWNLOAD_PRESENTATION_VERSION. Choose a later entry for version download/restore, or use DOWNLOAD_PRESENTATION for current content. Version retention depends on the drive's configuration.
Replace the bytes of an existing PowerPoint DriveItem with a valid, non-macro-enabled PPTX package no larger than 250 MiB, optionally requiring a matching eTag.
Restore a retained previous version of a PowerPoint presentation as a new current version while preserving its version history.
Transform text, slide order, or embedded core document properties inside a macro-free PPTX, then conditionally replace the same file. Supports literal, run-normalized text and {{placeholder}} replacement within DrawingML paragraphs, complete slide reordering, and core document-property updates. Provide at least one non-empty text_replacements, slide_order, or core_properties transformation. Rules run sequentially; a find string crosses a line break only when it includes a newline. Use UPDATE_PRESENTATION_METADATA instead to rename or move the DriveItem or change its filesystem metadata. It does not add or delete slides or edit layouts, themes, animations, charts, tables, or images.
Atomically update one macro-free PPTX under an exact eTag and one conditional upload. Supports slide lifecycle, shape and run edits, comments, native bar/line/pie charts, text boxes, PNG images, speaker notes, and tables. The delete_slide mode permanently removes a slide and eligible private dependencies; delete_shape permanently removes a top-level shape and unreferenced relationships; delete_comment permanently removes a root comment and its replies. Because this compatibility action exposes destructive modes, every call carries the static irreversible-update hint and requires irreversible-update approval, even when its submitted operations do not delete content; inspect targets before approval. Validates the package graph and semantic result. Limits include 50 MiB packages, 100 operations, 500,000 text characters, 20 uploaded PNGs, and 10,000 generated line breaks. Unsupported, shared, external, macro, combo, pivot, grouped, field, or ambiguous mutation targets are rejected before upload.
Atomically update one macro-free PPTX with at least one irreversible delete operation, under an exact eTag and one conditional upload. delete_slide permanently removes a slide and eligible private dependencies; delete_shape permanently removes a top-level shape and unreferenced relationships; delete_comment permanently removes a root comment and its replies. Supporting non-delete operations may be included in the same transaction, but every call must contain delete_slide, delete_shape, or delete_comment and requires irreversible-update approval. Validates the package graph and semantic result. Limits include 50 MiB packages, 100 operations, 500,000 text characters, 20 uploaded PNGs, and 10,000 generated line breaks.
Atomically update one macro-free PPTX without delete operations, under an exact eTag and one conditional upload. Allowed operations are add_text_box, add_image, replace_image, set_existing_speaker_notes, add_table, add_slide, duplicate_slide, set_slide_hidden, set_shape_text, format_text_run, set_shape_bounds, set_shape_alt_text, set_shape_hyperlink, set_text_run_hyperlink, add_comment, reply_comment, add_chart, and replace_chart_data. delete_slide, delete_shape, and delete_comment are rejected during request validation before any network request. Validates the package graph and semantic result. Limits include 50 MiB packages, 100 operations, 500,000 text characters, 20 uploaded PNGs, and 10,000 generated line breaks.
Update Microsoft Graph DriveItem metadata or path only: rename a PowerPoint presentation, move it within its current drive, or set supported filesystem metadata. This action does not edit slide text, slide order, document properties inside the PPTX package, or other presentation content. Optionally require a matching eTag. Provide at least one of name, parent_folder_id, description, created_datetime, or last_modified_datetime. OneDrive may accept a description without persisting it; the response reports that limitation.
Create a new PPTX in a Microsoft Graph drive folder, with configurable filename-conflict behavior. The file must be a valid, non-macro-enabled PPTX package no larger than 250 MiB.
The Microsoft PowerPoint integration connects your Dench AI CRM directly to Microsoft PowerPoint, so agents can read and act on your Microsoft PowerPoint data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
30 actions are available for agents to invoke on your behalf. Every call runs through Microsoft PowerPoint's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Microsoft PowerPoint and click Connect — you'll authorize access through Microsoft PowerPoint's own sign-in flow. No API keys or code required.
Ask an agent to use Microsoft PowerPoint in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Microsoft PowerPoint integration connects your AI CRM to Microsoft PowerPoint, so AI agents can work with your Microsoft PowerPoint data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Microsoft PowerPoint integration currently exposes 30 actions, including Check In Presentation, Check Out Presentation, Copy Presentation, Copy Presentation and Wait, Create Folder, and Create Presentation. Agents invoke them on your behalf from chat or from automations.
No. You connect Microsoft PowerPoint from your Dench workspace using Microsoft PowerPoint's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Microsoft PowerPoint's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Microsoft PowerPoint connection from your workspace settings at any time.