Integration
Connect Webflow to District of Columbia Open Data
When something happens in Webflow, your agent does the next thing in District of Columbia Open Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Webflow and District of Columbia Open Data to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Webflow and District of Columbia Open Data
Triggers and actions 2 triggers · 15 actions
Trigger
Form submissionInstant trigger: fires when a Webflow form is submitted (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New Collection Item (polling)Polls a CMS collection for newly created items.
Action
Create Collection ItemCreates a new item in a CMS collection.
Action
Delete Collection ItemDeletes a CMS collection item by ID.
Action
Get CollectionRetrieves details and field schema of a CMS collection.
Action
Get Collection ItemRetrieves a single CMS collection item by ID.
Action
Get SiteRetrieves details of a single site by ID.
Action
List Collection ItemsLists items in a CMS collection (paginated).
Action
List CollectionsLists all CMS collections for a site.
Action
List FormsLists forms for a site.
Action
List SitesLists all sites the authorized user can access.
Action
Publish Collection ItemsPublishes the specified live CMS collection items.
Action
Publish SitePublishes a site to the specified domains.
Action
Update Collection ItemUpdates an existing CMS collection item.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
Action
Find recordsQuery a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
Action
Get datasetGet a dataset's metadata and field/schema definitions by dataset or layer id, so callers know what attributes can be filtered or returned.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.