No logo available for Formstack to DuckDB connector icon

Load Formstack data to DuckDB

Build a Formstack to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Formstack API base URL, auth, endpoints, and incremental loading.

SourceFormstackOverviewDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

Formstack provides a REST API for programmatically managing forms, submissions, and other account-level data resources. Everything needed to build a working Formstack → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.


Build your Formstack to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

Prompt
Run uvx dlthub-init@latest to build a pipeline from Formstack to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Formstack API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.


Formstack API at a glance

Base URLhttps://www.formstack.com/api/v2025
Example endpointGET form/{formId}/submission
Records found atsubmissions
Authenticationrequests require a Bearer token in the Authorization header — sent in the Authorization header, prefixed Bearer
PaginationPage-number
Incremental fieldpage
Record idid
API referencehttps://developers.formstack.com/reference/api-overview

These values come from the Formstack API reference — the authoritative source if anything here looks out of date.


How do I authenticate with the Formstack API?

All API requests require an Authorization header with the format 'Bearer '. Personal Access Tokens are prefixed with 'fs_pat_'.

1. Get your credentials

To obtain credentials, log in to your Formstack account as an Admin. Click on your profile name in the dropdown menu and select 'API' to navigate to the API management dashboard. From here, you can either click 'Create new application' to generate a Client ID and Client Secret (for OAuth2 flows) or follow the 'Access Tokens' menu if you need a Personal Access Token (PAT) for direct authentication. Note that PAT generation may require explicit enablement by an Organization Admin.

2. Add them to .dlt/secrets.toml

[sources.formstack_source] api_key = "fs_pat_<your_personal_access_token>"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.


What Formstack data can I load into DuckDB?

These are the Formstack endpoints dlt can load into DuckDB:

ResourceEndpointMethodData selectorDescription
formsformGETGet all forms in your account
form_detailsform/{formId}GETGet the details of the specified form
form_fieldsform/{formId}/fieldGETGet all fields for the specified form
form_submissionsform/{formId}/submissionGETGet all submissions for the specified form
notificationsform/{formId}/notificationGETGet all notification emails for the specified form
webhooksform/{formId}/webhookGETGet all webhooks for the specified form

How do I load only new Formstack records?

Formstack exposes page on form/{formId}/submission, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

{"name": "form_submissions", "endpoint": { "path": "form/{formId}/submission", "data_selector": "submissions", "incremental": {"cursor_path": "page", "initial_value": "2024-01-01T00:00:00Z"}, }}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.


What does the generated Formstack pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /form and /submission from the Formstack API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def formstack_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.formstack.com/api/v2025", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "form_submissions", "endpoint": {"path": "form/{formId}/submission", "data_selector": "submissions"}}, {"name": "forms", "endpoint": {"path": "form", "data_selector": "forms"}} ], } yield from rest_api_resources(config) def load_formstack_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="formstack_pipeline", destination="duckdb", dataset_name="formstack_data", ) load_info = pipeline.run(formstack_source()) print(load_info) if __name__ == "__main__": load_formstack_to_duckdb()

Run it with python formstack_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.


How do I query Formstack data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("formstack_pipeline").dataset() df = data.form_submissions.df() print(df.head())

SQL:

SELECT * FROM formstack_data.form_submissions LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.


How do I deploy the Formstack to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

  • Deploy & schedule — run the pipeline as a managed job with automatic retries.
  • Monitor — observable job queues, alerting, and load metrics for every run.
  • Transform — promote raw Formstack loads into governed, documented models.
  • Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →


What other destinations can I load Formstack data to?

dlt loads into any of these — only the destination argument changes:

DestinationExample value
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.


Next steps

Was this page helpful?

Community Hub

Need more dlt context for Formstack to DuckDB?

Request dlt skills, commands, AGENT.md files, and AI-native context.