Integration
Connect IntakeQ to Wasi
When New Appointment fires in IntakeQ, 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 IntakeQ and Wasi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 IntakeQ can start in Wasi
When New Appointment in IntakeQ
then Add Contact in Wasi
When New Client in IntakeQ
then Get client 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 IntakeQ and Wasi
Triggers and actions 3 triggers · 31 actions
Trigger
New AppointmentTriggers when a new appointment is booked in IntakeQ.
Trigger
New ClientTriggers when a new client is added to IntakeQ.
Trigger
New Submitted IntakeTriggers when a client submits an IntakeQ intake form.
Action
Add Tag to ClientAdds a tag to an IntakeQ client, creating the tag if it does not exist yet.
Action
Cancel AppointmentCancels an IntakeQ appointment, with an optional reason.
Action
Create AppointmentBooks an IntakeQ appointment for a client with a practitioner, service and location at a given time.
Action
Create or Update ClientCreates an IntakeQ client, or updates an existing one when a Client ID is given. Without a Client ID, IntakeQ matches an existing client by first name plus email or phone.
Action
Find AppointmentsSearches IntakeQ appointments by client, date range, status or practitioner and returns up to 100 matches.
Action
Find ClientsSearches IntakeQ clients by name, email or client number and returns up to 100 matching clients with their full profiles.
Action
Find IntakesSearches IntakeQ intake forms by client or date and returns up to 100 intake summaries.
Action
Find InvoicesSearches IntakeQ invoices by client, date, status or number and returns up to 100 matches.
Action
Find Treatment NotesSearches IntakeQ treatment notes by client or date and returns up to 100 note summaries.
Action
Get AppointmentReturns one IntakeQ appointment by its ID, including client, service, time and practitioner.
Action
Get Booking SettingsReturns the practice's bookable services, locations and practitioners with their IDs.
Action
Get IntakeReturns one IntakeQ intake form by its ID, including the client and questionnaire.
Action
Get InvoiceReturns one IntakeQ invoice by its ID, with amounts and status.
Action
Get Treatment NoteReturns one IntakeQ treatment note by its ID.
Action
List PractitionersReturns every practitioner in the IntakeQ practice, with name, email and ID.
Action
List QuestionnairesReturns the practice's questionnaire (intake package) templates with their IDs.
Action
Remove Tag from ClientRemoves a tag from an IntakeQ client.
Action
Send QuestionnaireSends an IntakeQ questionnaire to a client by email, or by SMS when only a phone number is given.
Action
Update AppointmentReschedules an IntakeQ appointment or changes its service, location, status or reminder type.
Action
Add ContactRegisters a contact from a client in Wasi, creating the client if they do not already exist, and optionally associates them with a property.
Action
Add propertyCreates a new property listing in Wasi and returns its id.
Action
Add taskCreates a task (call, meeting, visit, etc.) in a Wasi user's schedule.
Action
Delete taskDeletes a task from a user's schedule in Wasi, identified by its id and assigned date.
Action
Get clientReturns a single Wasi client, including contact details, location, client types and tags.
Action
Get propertyReturns a single Wasi property by its id, including its location, prices, images and features.
Action
Get taskReturns one task from the Wasi schedule, including its type, status, assigned user and linked clients and properties.
Action
Get userReturns a Wasi user (employee) by id, including name, email, role and contact details.
Action
List tasksReturns the tasks on a user's Wasi schedule between a start and end date, optionally limited to one task type.
Action
List usersReturns all users (agents and administrators) of your Wasi company, with their email, type and profile details.
Action
Update propertyUpdates an existing Wasi property. Only the fields you fill in are changed.
Action
Update taskUpdates 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 IntakeQ
IntakeQ to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
IntakeQ to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
IntakeQ to MailchimpMailchimp marketing automation and email platform.
IntakeQ to StripeStripe is a payment processing platform for online businesses.
IntakeQ to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
IntakeQ to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Wasi
Vercel to WasiVercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.
HubSpot to WasiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WasiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WasiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WasiGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to WasiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
IntakeQ and Wasi, answered
What can start an automation from IntakeQ?
Any of IntakeQ's 3 triggers in the catalog, including New Appointment, New Client and New Submitted Intake. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wasi when something happens in IntakeQ?
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 IntakeQ?
Wasi has no triggers in the catalog today, so automations start in IntakeQ. 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 IntakeQ 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.
Can my AI client use IntakeQ and Wasi without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.