Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Skyvern

Skyvern integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Skyvern with Flows360

Skyvern integration for Flows360 workflows.

Use the Skyvern 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 6 actions and no declared triggers.

Available actions

  • Run Agent Task
  • Run Workflow
  • Cancel Run
  • Get Workflow/Task Run
  • Find Workflow
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

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: Skyvern
  • Package: @activepieces/piece-skyvern@0.2.0
  • Exact artifact digest: sha256:78ec23d137cca93a431c0ea36ccc6c5a0d75c66c07b57fec1b0a5a4388fc1454
  • 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

  • Run Agent Task (run-agent-task), Runs task with specified prompt. Classification: read.
  • Run Workflow (run-workflow), Runs the workflow. Classification: read.
  • Cancel Run (cancel-run), Cancels a workflow or or task run by ID. Classification: read.
  • Get Workflow/Task Run (get-run), Retrieves a workflow or task run by ID. Classification: read.
  • Find Workflow (find-workflow), Finds workflow based on title. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

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 actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Run Agent Task Yes No Runs task with specified prompt.
Run Workflow Yes No Runs the workflow.
Cancel Run Yes No Cancels a workflow or or task run by ID.
Get Workflow/Task Run Yes No Retrieves a workflow or task run by ID.
Find Workflow Yes No Finds workflow based on title.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Run Agent Task · Read

Runs task with specified prompt.

run_agent_task · Risk: low · Retry: safe

Inputs

  • prompt · string · Required, The goal or task description for Skyvern to accomplish.
  • url · string · Optional, The starting URL for the task.
  • engine · string · Optional
  • webhookUrl · string · Optional, URL to send task status updates to after a run is finished.
  • proxyLocation · string · Optional
  • maxSteps · number · Optional, Maximum number of steps the task can take. Task will fail if it exceeds this number.
  • dataExtractionSchema · object · Optional, The schema for data to be extracted from the webpage.
Run Workflow · Read

Runs the workflow.

run_workflow · Risk: low · Retry: safe

Inputs

  • workflowId · string · Required
  • title · string · Optional, The title for this workflow run.
  • proxyLocation · string · Optional
  • webhookUrl · string · Optional
  • parameters · object · Optional
Cancel Run · Read

Cancels a workflow or or task run by ID.

cancel_run · Risk: low · Retry: safe

Inputs

  • runId · string · Required
Get Workflow/Task Run · Read

Retrieves a workflow or task run by ID.

get_run · Risk: low · Retry: safe

Inputs

  • runId · string · Required
Find Workflow · Read

Finds workflow based on title.

find_workflow · Risk: low · Retry: safe

Inputs

  • title · string · 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.

Setup

Setup

  1. Add the Skyvern 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-skyvern@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers 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 Skyvern 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-skyvern@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