Integration
Connect Cakemail to District of Columbia Open Data
When something happens in Cakemail, 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 Cakemail 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 Cakemail and District of Columbia Open Data
Triggers and actions 8 triggers ยท 5 actions
Trigger
New ContactTriggers when a new Contact is added.
Trigger
New Email BounceTriggers when an email bounces.
Trigger
New Email ClickTriggers when a new Email Click is tracked.
Trigger
New Email OpenTriggers when a new Email Open is tracked.
Trigger
New ListTriggers when a List is created.
Trigger
New Suppressed EmailTriggers when a new Suppressed Email is added.
Trigger
Unsubscribed ContactTriggers when a Contact is unsubscribed.
Trigger
Updated ContactTriggers when a Contact is updated.
Action
Add Suppressed EmailAdds an email address to the Cakemail suppression list so no further mail is sent to it.
Action
Find Contact by EmailReturns the contacts on a Cakemail list whose email address matches the one you supply.
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