Integration
Connect Twilio to District of Columbia Open Data
When something happens in Twilio, 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 Twilio 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 Twilio and District of Columbia Open Data
Triggers and actions 2 triggers ยท 9 actions
Trigger
New CallPolls for voice calls on your Twilio account.
Trigger
New Message ReceivedPolls for inbound SMS/MMS messages received by your Twilio account.
Action
Get CallRetrieves details of a single voice call by its Call SID.
Action
Get MessageRetrieves a single SMS/MMS message by its Message SID.
Action
List CallsLists voice calls on the account, optionally filtered by To, From, or status.
Action
List MessagesLists SMS/MMS messages on the account, optionally filtered by To, From, or date sent.
Action
List Phone NumbersLists the Twilio phone numbers (incoming phone numbers) owned by your account.
Action
Lookup Phone NumberLooks up details (carrier, line type, caller name) for a phone number via the Twilio Lookup v2 API.
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.
Each app on its own
Reviews