Integration
Connect Broot to Wasi
When New Campaign Contact Created fires in Broot, 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 Broot 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)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 Broot can start in Wasi
When New Campaign Contact Created in Broot
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 Broot and Wasi
Triggers and actions 3 triggers · 13 actions
- New Campaign Contact Created
- New Item on Contact
Starts your automation whenever a new item is added on a contact in Broot.
- New Update on Item on Contact Section
Retrieves records from Linkrwave when an item is updated in the Contact section.
- Create Item on Contact Section
Adds a contact to your Broot contact section, with their company, role, campaign and an optional attached file.
- 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 Broot
Broot to ESPNESPN's sports data: team schedules and team lists for the NFL, NBA, MLB, NHL, WNBA and college leagues...
Broot to TicketmasterTicketing platform providing an API for searching events, venues, and attractions for concerts, sports, and...
Broot to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Broot to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Broot to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Broot to Google SheetsGoogle Sheets
More into Wasi
Gmail to WasiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WasiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Broot and Wasi, answered
What can start an automation from Broot?
Any of Broot's 3 triggers in the catalog, including New Campaign Contact Created, New Item on Contact and New Update on Item on Contact Section. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wasi when something happens in Broot?
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 Broot?
Wasi has no triggers in the catalog today, so automations start in Broot. 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 Broot 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 Broot 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.