Integration
Connect Better Proposals to District of Columbia Open Data
When something happens in Better Proposals, 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 Better Proposals 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 Better Proposals and District of Columbia Open Data
Triggers and actions 3 triggers ยท 4 actions
Trigger
Proposal OpenedTriggers when a proposal is opened.
- Proposal Paid
Triggers when a proposal is paid.
- Proposal Signed
Triggers when a proposal is signed.
- Create a Proposal
Creates a new proposal.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
- Find records
Query a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
- Get dataset
Get 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.