Integration
Connect FacturaDirecta to District of Columbia Open Data
When something happens in FacturaDirecta, 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 FacturaDirecta 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 FacturaDirecta and District of Columbia Open Data
Triggers and actions 1 trigger ยท 5 actions
Trigger
New ContactFires instantly when a contact is added in FacturaDirecta. Manual-registration webhook: in FacturaDirecta go to Settings then API and integrations then Webhooks, add a webhook endpoint subscribed specifically to the contact.created event, and paste this triggers minted URL as the endpoint. FacturaDirecta delivers only the events the endpoint is subscribed to, so the payload binds as {{ trigger.body.* }} (contact fields live under data.object, the event kind is in the type field such as contact.created).
Action
Create ClientCreates a client.
Action
Create Sales InvoiceCreates a sales invoice (with line-item support).
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.