Integration
Connect MOCO and Wachete
When New Client fires in MOCO, your agent runs Create monitor in Wachete, or New notification for monitor in Wachete to Create Contact in MOCO. 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 MOCO and Wachete 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 MOCO and Wachete can do together
From MOCO to Wachete
When New Client in MOCO
then Create monitor in Wachete
From Wachete to MOCO
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 MOCO and Wachete
Triggers and actions 28 triggers · 31 actions
- New Client
Triggers when a new client is created.
- New Company
Triggers when a new company is created.
- New Expense
Triggers when an expense is created.
- New Exported Invoice (Bookkeeping)
Triggers when a new invoice is exported (for the bookkeeping).
- New Incoming Payment
Triggers when a new incoming payment is created.
- New Invoice
Triggers when a new invoice is created.
- New Invoice Status
Triggers when the status of an invoice is changed.
- New Offer
Triggers when a new offer is created.
- New Outgoing Payment
Triggers when a new outgoing payment is created.
- New Planning Entry
Triggers when a new Planning Entry is created.
- New Presence
Triggers when a new Presence is created.
- New Project Assignment
Triggers when a person is assigned to a project.
- New Purchase
Triggers when a new purchase is created.
- New Recurred Expense
Triggers when an expense is recurred.
- New Task
Triggers when a new task is created.
- New Time Entry
Triggers when a new time entry is created.
- Unarchived Project
Triggers when a project is made active again.
- Updated Company
Triggers when a company was updated.
- Updated Expense
Triggers when an expense was updated.
- Updated Invoice
Triggers when an invoice was updated.
- Updated Lead
Triggers when a lead was updated.
- Updated Planning Entry
Triggers when a Planning Entry was updated.
- Updated Presence
Triggers when a Presence was updated.
- Updated Project
Triggers when a project was updated.
- Updated Purchase
Triggers when a purchase was updated.
- Updated Time Entry
Triggers when a time entry was updated.
- Create Comment
Creates a new Comment.
- Create Company
Creates a new company (customer only).
- Create Contact
Creates a new contact person.
- Create Expense
Creates a new Expense.
- Create Incoming Payment
Creates a new incoming payment.
- Create Lead
Creates a new lead.
- Create Outgoing Payment
Creates a new outgoing payment.
- Create Project
Creates a new Project.
- Create Purchase
Creates a new Purchase.
- Create Task
Creates a new project task.
- Create Time Entry
Create a new time entry.
- Find Company
Finds an existing Company.
- Find Contact
Finds an existing Contact.
- Find Expense
Finds an existing Expense.
- Find Invoice
Finds an existing Invoice.
- Find Lead
Finds an existing lead.
- Find Offer
Finds an existing Offer.
- Find Planning Entry
Finds an existing Planning Entry.
- Find Project
Finds an existing project.
- Find Purchase
Finds an existing Purchase.
- Find Task
Finds an active Task for a Project.
- Find Time Entry
Finds an existing Time Entry.
- Find User
Finds an existing active user.
- Record Presence
Record a new presence.
- Any new notification
Fires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
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 MOCO
MOCO to ip-apiip-api resolves an IP address or domain name to a physical location.
MOCO to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MOCO to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MOCO to StripeStripe is a payment processing platform for online businesses.
MOCO to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MOCO to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Wachete
HubSpot to WacheteHubSpot is your all-in-one stop for all of your marketing software needs.
Mailchimp to WacheteMailchimp marketing automation and email platform.
Pipedrive to WachetePipedrive is a sales CRM and pipeline management tool.
Questions
MOCO and Wachete, answered
What can start an automation from MOCO?
Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Expense and New Exported Invoice (Bookkeeping). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in MOCO?
Any of Wachete's 7 actions, including Create monitor, Update monitor, Get monitor and Get monitor data. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wachete to MOCO?
Yes. When something happens in Wachete, your agent can act in MOCO too. This page covers both directions: Wachete's triggers and MOCO's actions are listed here as well.
Do I have to build a connector for MOCO or Wachete?
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 MOCO and Wachete 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.