Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

SlideSpeak

SlideSpeak integration for Flows360 workflows.

CategoryContent And Files
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect SlideSpeak with Flows360

SlideSpeak integration for Flows360 workflows.

Use the SlideSpeak connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 1 trigger.

Available actions

  • Create Presentation
  • Edit Presentation
  • Get Task Status
  • Upload Document
  • Custom API Call

Available triggers

  • New Presentation

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: SlideSpeak
  • Package: @activepieces/piece-slidespeak@0.2.0
  • Exact artifact digest: sha256:bf5a7d1f895fb11cac3d8e7205841c3ad73ecd62ec4b2207c8640b575c083c27
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Presentation (create-presentation), Creates a new presentation. Classification: read.
  • Edit Presentation (edit-presentation), Edits an existing presentation. Classification: read.
  • Get Task Status (get-task-status), Gets status of task by id. Classification: read.
  • Upload Document (upload-docuemnt), Uploads a document file to SlideSpeak. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Presentation, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Presentation Yes No Creates a new presentation.
Edit Presentation Yes No Edits an existing presentation.
Get Task Status Yes No Gets status of task by id.
Upload Document Yes No Uploads a document file to SlideSpeak.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Presentation Yes No webhook trigger declared by the pinned package.

Supported actions

Create Presentation · Read

Creates a new presentation.

create_presentation · Risk: low · Retry: safe

Inputs

  • plain_text · string · Required, Topic of presentation.
  • length · number · Optional
  • document_uuids · array · Optional, Uploaded docuemts to use in presentation.
  • template · string · Optional
  • language · string · Optional
  • custom_user_instructions · string · Optional
  • fetch_images · boolean · Optional, Whether to include stock images.
  • tone · string · Optional, The tone to use for the text.
  • verbosity · string · Optional, How verbose, or long, the text should be.
  • include_cover · boolean · Optional
  • include_table_of_contents · boolean · Optional
  • response_format · string · Optional
Edit Presentation · Read

Edits an existing presentation.

edit_presentation · Risk: low · Retry: safe

Inputs

  • pptx_file · object · Required
  • config · object · Required
Get Task Status · Read

Gets status of task by id.

get_task_status · Risk: low · Retry: safe

Inputs

  • taskId · string · Required
Upload Document · Read

Uploads a document file to SlideSpeak.

upload_docuemnt · Risk: low · Retry: safe

Inputs

  • file · object · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Presentation · Webhook

Triggers when a new presentation is created.

Setup

Setup

  1. Add the SlideSpeak connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-slidespeak@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required SlideSpeak connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-slidespeak@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com