Integration
Connect Every.org to District of Columbia Open Data
When something happens in Every.org, 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 Every.org 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 Every.org and District of Columbia Open Data
Triggers and actions 1 trigger ยท 9 actions
Trigger
New DonationTriggered instantly when someone donates through your Every.org account or one of its fundraisers. Paste the URL this trigger mints into the Webhook URL field in your Every.org developer dashboard.
Action
Add fundraiserCreates a fundraiser on Every.org for a nonprofit, with an optional goal, dates and cover image. Returns the new fundraiser.
Action
Find nonprofits by keywordReturns the nonprofits on Every.org that match a keyword, optionally limited to particular causes.
Action
Get fundraiserReturns the details of a fundraiser on Every.org, such as its title, description, goal and dates.
Action
Get fundraiser total raisedReturns how much a fundraiser has raised so far, along with its supporter count and goal.
Action
Get nonprofitReturns the details of a nonprofit on Every.org, including its description, location, website and causes.
Action
List nonprofits by causeReturns the nonprofits on Every.org that work on a given cause.
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