Integration
Connect Airparser to Wasi
When Document Parsed fires in Airparser, your agent runs Add Contact in Wasi. Describe the whole flow 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 Airparser and Wasi 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 Airparser can start in Wasi
When Document Parsed in Airparser
then Add Contact in Wasi
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 Airparser and Wasi
Triggers and actions 1 trigger · 21 actions
- Document Parsed
Triggers when Airparser finishes parsing a document in the chosen inbox, giving you the extracted data.
- Create an Inbox
Creates a new Airparser inbox that documents can be sent to for parsing.
- Create or Update Extraction Schema
Sets which fields Airparser should pull out of documents sent to an inbox, replacing whatever schema was there before.
- Delete an Inbox
Deletes an Airparser inbox and the documents stored in it.
- Extract Data From a Document
Sends a document to an Airparser inbox, waits for it to be parsed, and returns the extracted data.
- Extract Data From a Document (Async)
Sends a document to an Airparser inbox and returns straight away without waiting for parsing. Use the Document Parsed trigger or Get Document to pick up the result.
- Get a Document
Returns a parsed Airparser document, including the data extracted from it.
- Get an Inbox
Returns one Airparser inbox with its settings, its email address prefix and its current extraction schema.
- List Documents
Lists the documents in an Airparser inbox, with the data extracted from each one.
- List Inboxes
Lists all the Airparser inboxes in the connected account.
- Add Contact
Registers a contact from a client in Wasi, creating the client if they do not already exist, and optionally associates them with a property.
- Add property
Creates a new property listing in Wasi and returns its id.
- Add task
Creates a task (call, meeting, visit, etc.) in a Wasi user's schedule.
- Delete task
Deletes a task from a user's schedule in Wasi, identified by its id and assigned date.
- Get client
Returns a single Wasi client, including contact details, location, client types and tags.
- Get property
Returns a single Wasi property by its id, including its location, prices, images and features.
- Get task
Returns one task from the Wasi schedule, including its type, status, assigned user and linked clients and properties.
- Get user
Returns a Wasi user (employee) by id, including name, email, role and contact details.
- List tasks
Returns the tasks on a user's Wasi schedule between a start and end date, optionally limited to one task type.
- List users
Returns all users (agents and administrators) of your Wasi company, with their email, type and profile details.
- Update property
Updates an existing Wasi property. Only the fields you fill in are changed.
- Update task
Updates an existing task in the Wasi schedule, changing only the fields you fill in.
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 Airparser
Airparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Airparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Airparser to Google SheetsGoogle Sheets
Airparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Airparser to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Airparser to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Wasi
Slack to WasiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Questions
Airparser and Wasi, answered
What can start an automation from Airparser?
Any of Airparser's 1 trigger in the catalog, including Document Parsed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wasi when something happens in Airparser?
Any of Wasi's 12 actions, including Update property, Update task, Add Contact and Add property. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wasi to Airparser?
Wasi has no triggers in the catalog today, so automations start in Airparser. If you need the other direction, ask: your agent reads Wasi's API documentation and adds it.
Do I have to build a connector for Airparser or Wasi?
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.