Overview
Connect Descript with Flows360
AI-powered video and podcast editor. Import media, run AI edits with Underlord, and publish.
Use the Descript 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 7 actions and 1 trigger.
Available actions
- Import Media
- Agent Edit (Underlord)
- Publish Project
- Get Job Status
- List Projects
- Get Project
- Custom API Call
Available triggers
- Job Completed
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: Descript
- Package:
@activepieces/piece-descript@0.1.0 - Exact artifact digest:
sha256:d85659bf4431a5ec3c275a35d8d6401042a2d2b8357a305fa34c2fc4fa4604a1 - 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
- Import Media (
import_media), Imports a media file from a URL into a new or existing Descript project and optionally creates a composition. Classification: read. - Agent Edit (Underlord) (
agent_edit), Use Descript's AI agent "Underlord" to edit an existing project or create a new one with a natural language prompt. Classification: read. - Publish Project (
publish_project), Publishes a composition from a project to create a shareable link and a downloadable export file. Classification: read. - Get Job Status (
get_job_status), Retrieves the current status of a Descript background job (import, agent edit, or publish). Use the job_id returned by any job-creation action. Classification: read. - List Projects (
list_projects), Returns projects in your Descript Drive. Supports filtering by name, date, and creator. Classification: read. - Get Project (
get_project), Retrieves details for a Descript project including its compositions and media files. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- Job Completed, polling.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API Token Required · protected credential
Setup
Setup
- Add the Descript connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-descript@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 7 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 Descript 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-descript@0.1.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.