Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

DuckDB

Run SQL queries on an in-memory DuckDB database.

CategoryDeveloper Tools
AuthenticationNo authentication required
Version0.0.8
Published scopes0 published scopes
Last updatedOctober 6, 2026

Overview

Connect DuckDB with Flows360

Run SQL queries on an in-memory DuckDB database.

Use the DuckDB 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 1 action and no declared triggers.

Available actions

  • Create and Query DB

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: DuckDB
  • Package: @activepieces/piece-duckdb@0.0.8
  • Exact artifact digest: sha256:10714a9ade0dff3b625813463e2538b792a0818c7898fd5dd3319bbd0308eb6d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. 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 and Query DB (createAndQueryDB), Create DB from data and run query Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects1
Supported actions1
TriggersNone published

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Create and Query DB Yes No Create DB from data and run query

Supported actions

Create and Query DB · Read

Create DB from data and run query

create_and_query_db · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** insert dynamic input directly into the query string. Instead, use $1, $2, $3 and add them in args for parameterized queries to prevent **SQL injection.**
  • tables · array · Required, List of tables to create in the database
  • query · string · Required, Please use $1, $2, etc. for parameterized queries to avoid SQL injection.
  • args · array · Optional, Arguments to be used in the query

Setup

Setup

  1. Add the DuckDB 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-duckdb@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 1 action 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required DuckDB 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-duckdb@0.0.8 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