Integration
Connect Paperless to DistrictAPI
When something happens in Paperless, your agent does the next thing in DistrictAPI. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Paperless and DistrictAPI to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Paperless can start in DistrictAPI
When Document updated in Paperless
then Batch lookup districts in DistrictAPI
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Paperless and DistrictAPI
Triggers and actions 2 triggers · 14 actions
- Document updated
Fires when a document is updated (e.g. name changed). Backed by the document.updated webhook event.
- New document created
Fires when a new document is created. Backed by the document.created webhook event.
- Create Document (From Template)
Creates a new Paperless document from an existing template, optionally filling in recipients, form-field defaults and variables, and optionally sending it right away.
- Delete Document
Permanently delete a document by ID.
- Get Document
Retrieves a single Paperless document by its id.
- Get Template
Retrieves a single Paperless template by its id.
- List Templates
List all templates the API key's integration has access to, used to pick a template_id before creating a document.
- Update Document
Updates an existing Paperless document: rename it, set its recipients, form field defaults and variables, or send it by setting its state to dispatched.
- Batch lookup districts
Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one.
- Find districts by name, state or county
Returns the school districts matching the name, state or county you supply.
- Get district
Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary.
- Get school
Returns the full profile of one school, including its address, grades served, enrollment and parent district.
- Get school's district
Returns the full profile of the school district a given school belongs to.
- List districts
Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID.
- List schools
Returns the schools near a street address or a pair of coordinates, within the radius you choose.
- List schools by district
Returns the open schools inside a given school district, optionally limited to one school type or to charter schools.
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
What our customers say
More from Paperless
Paperless to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Paperless to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Paperless to StripeStripe is a payment processing platform for online businesses.
Paperless to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Paperless to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Paperless to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into DistrictAPI
Arxiv to DistrictAPIOpen-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...
HubSpot to DistrictAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to DistrictAPIGoogle Sheets
Gmail to DistrictAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Paperless and DistrictAPI, answered
What can start an automation from Paperless?
Any of Paperless's 2 triggers in the catalog, including Document updated and New document created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in DistrictAPI when something happens in Paperless?
Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DistrictAPI to Paperless?
DistrictAPI has no triggers in the catalog today, so automations start in Paperless. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it.
Do I have to build a connector for Paperless or DistrictAPI?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.