Can n8n generate PowerPoint presentations?

Yes. Use an n8n trigger to collect source data, transform it into a presentation brief or structured payload, call a presentation API with the HTTP Request node, monitor the asynchronous job, and send the finished PPTX to an approved destination.

The n8n presentation workflow

Schedule / Webhook / CRM trigger
  → fetch approved data
  → validate and map fields
  → POST presentation job
  → save task ID
  → wait or receive webhook
  → check status
  → store and deliver PPTX

Configure the HTTP Request node

Create a POST request to the asynchronous generation endpoint. Send JSON and use Bearer authentication through an n8n credential rather than a visible expression or hard-coded header.

POST https://api.presenton.ai/api/v3/presentation/generate/async
Authorization: Bearer [stored credential]
Content-Type: application/json

{
  "content": "Create a monthly customer-success review from the supplied facts.",
  "n_slides": 8,
  "tone": "professional",
  "verbosity": "concise",
  "standard_template": "general",
  "export_as": "pptx"
}

Map dynamic values only after validating them. Keep templates, output format, and maximum slide count controlled by the workflow.

Track the asynchronous task

Save the returned task ID with the business record. Then use one of two patterns:

• Wait and poll: pause, call the task-status endpoint, branch on status, and repeat with a maximum attempt count.
• Webhook completion: subscribe an HTTPS endpoint, verify the event, and resume processing idempotently.

Polling is simpler for an initial workflow. Webhooks reduce repeated requests at scale but require a public endpoint, verification, and duplicate-event handling.

Normalize source data before generation

Do not pass an entire CRM record or spreadsheet row directly into the prompt. Use a Set or Code node to construct a stable contract containing only approved fields: audience, objective, KPIs, evidence, risks, recommendation, and requested action.

This reduces accidental data leakage and keeps output consistent when an upstream app changes its schema.

Handle failures and retries

Deliver the deck safely

Store the result in an approved workspace, object store, or customer record. Verify tenant ownership before sending a link. Avoid posting provider URLs into public channels, and do not email sensitive decks without the organization’s normal access controls.

Useful n8n PowerPoint automations

• weekly KPI and leadership reports;
• one sales deck when an opportunity enters a stage;
• client reports generated from analytics data;
• training slides created from approved lesson content;
• research briefings from a controlled document library;
• personalized decks generated in a rate-limited batch.