Integration
Connect Clientify and Wachete
When New Contact fires in Clientify, your agent runs Create monitor in Wachete, or New notification for monitor in Wachete to Add task in Clientify. 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 Clientify 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 Clientify and Wachete can do together
From Clientify to Wachete
When New Contact in Clientify
then Create monitor in Wachete
When New Deal in Clientify
then Update monitor in Wachete
From Wachete to Clientify
When New notification for monitor in Wachete
then Add task in Clientify
When Any new notification in Wachete
then Create Contact in Clientify
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 Clientify and Wachete
Triggers and actions 5 triggers · 22 actions
Trigger
New ContactTriggers when a new contact is created in Clientify.
Trigger
New DealTriggers when a new deal is created in Clientify.
Trigger
New TaskTriggers when a new task is created in Clientify.
Action
Add companyCreates a company in Clientify with its contact details, address, tags and custom field values.
Action
Add taskCreates a task in Clientify, optionally assigned to a user and linked to contacts, companies and deals.
Action
Create Abandoned CartCreates an abandoned shopping cart for a Clientify contact, with the cart's items, shop and currency.
Action
Create ContactCreates a contact in Clientify. If a contact with the same email or phone already exists it is updated instead, unless forced insert is turned on.
Action
Create DealCreates a deal in Clientify, optionally linked to a contact and company and placed in a pipeline stage.
Action
Create OrderCreates an order in Clientify for a contact, with its line items.
Action
Delete contactDeletes a contact from Clientify.
Action
Find ContactFinds contacts by name, surname or email, optionally narrowed by phone, source, type or dates, and returns the matches.
Action
Get companyReturns the full details of a Clientify company by its id, including contact info, tags, custom fields and employees.
Action
Get contactReturns a Clientify contact's full details, including emails, phones, addresses, tags and custom fields.
Action
Get dealReturns a Clientify deal by its id, including amount, stage, pipeline, involved contacts and companies, tasks and custom fields.
Action
List contactsReturns the contacts in your Clientify account, optionally filtered by name/email, phone, source, type, or created/modified dates.
Action
Update companyUpdates an existing company in Clientify and returns the updated record.
Action
Update contactUpdates an existing Clientify contact's name, title, company, status and notes. Fields left blank keep their current values.
Action
Update dealUpdates an existing Clientify deal, changing only the fields you fill in.
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange 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 Clientify
Clientify to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clientify to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clientify to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clientify to Google SheetsGoogle Sheets
Clientify to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clientify to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Wachete
HubSpot to WacheteHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to WacheteSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to WacheteMailchimp marketing automation and email platform.
Shopify to WacheteShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to WacheteQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to WachetePipedrive is a sales CRM and pipeline management tool.
Questions
Clientify and Wachete, answered
What can start an automation from Clientify?
Any of Clientify's 3 triggers in the catalog, including New Contact, New Deal and New Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in Clientify?
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 Clientify?
Yes. When something happens in Wachete, your agent can act in Clientify too. This page covers both directions: Wachete's triggers and Clientify's actions are listed here as well.
Do I have to build a connector for Clientify 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 Clientify 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.