Integration
Connect Wachete to HitPay
When New notification for monitor fires in Wachete, your agent runs Add customer in HitPay. 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 Wachete and HitPay 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 Wachete can start in HitPay
When New notification for monitor in Wachete
then Add customer in HitPay
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 Wachete and HitPay
Triggers and actions 2 triggers · 28 actions
- 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.
- Add customer
Creates a customer in your HitPay account with their contact details and optional address.
- Add order
Creates a new draft order in HitPay.
- Add subscription plan
Creates a subscription plan with a name, amount and billing frequency that customers can be signed up to for recurring billing.
- Create Payment Request
Creates a HitPay payment request and returns its checkout link for the buyer to pay.
- Delete customer
Deletes a customer from your HitPay account.
- Delete invoice
Deletes an invoice from your HitPay business account.
- Delete Payment Request
Deletes a payment request. Completed payment requests cannot be deleted.
- Delete product
Deletes a product from your HitPay product catalog.
- Get balances
Returns your HitPay account balances for each currency, including available, pending and reserve amounts.
- Get charge
Returns the details of a single HitPay charge, including amount, fees, status, payment method, customer and refunds.
- Get customer
Returns the details of a HitPay customer, including contact information and address.
- Get order
Returns the full details of a HitPay order, including its line items, charges, customer and totals.
- Get Payment Request Details
Returns a payment request's details and status, including its amount, customer, checkout URL and any payments made against it.
- Get product
Returns the details of a product, including its price, variations and images.
- List charges
Returns the charges (payments) on your HitPay account, optionally filtered by status, date, amount, customer, payment request or payout.
- List customers
Returns all customers saved in your HitPay account.
- List invoices
Returns the invoices in your HitPay account, optionally filtered by customer email, status or reference.
- List payouts
Returns payouts of your HitPay balance to your linked bank account, newest first, optionally filtered by status and creation date.
- List products
Returns the products in your HitPay account, optionally filtered by status, category, source, inventory, location, channel or keyword.
- Refund Payment
Refunds all or part of a successful payment, returning the refund record.
- Update customer
Updates an existing customer's details, such as name, email, phone and address.
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 Wachete
Wachete to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Wachete to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
Wachete to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Wachete to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wachete to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Wachete to AnthropicAnthropic builds Claude, a family of large language models.
More into HitPay
HubSpot to HitPayHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to HitPaySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HitPayGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HitPayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HitPayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Wachete and HitPay, answered
What can start an automation from Wachete?
Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one.
What can your agent do in HitPay when something happens in Wachete?
Any of HitPay's 21 actions, including Create Payment Request, Update customer, Add customer and Add order. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from HitPay to Wachete?
HitPay has no triggers in the catalog today, so automations start in Wachete. If you need the other direction, ask: your agent reads HitPay's API documentation and adds it.
Do I have to build a connector for Wachete or HitPay?
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 Wachete and HitPay 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.