Integration
Connect Vitally and Wachete
When Customer Created fires in Vitally, your agent runs Create monitor in Wachete, or New notification for monitor in Wachete to Create Task in Vitally. 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 Vitally 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 Vitally and Wachete can do together
From Vitally to Wachete
When Customer Created in Vitally
then Create monitor in Wachete
From Wachete to Vitally
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 Vitally and Wachete
Triggers and actions 10 triggers · 26 actions
- Customer Created
Triggers when a new account (customer) is created in Vitally.
- Custom Object Instance Created
Triggers when a new instance of a custom object is created.
- Custom Object Instance Updated
Triggers when an instance of a custom object is created or updated.
- Note Created
Triggers when a new note is created in Vitally.
- NPS Response Created
Triggers when a new NPS response is recorded in Vitally.
- Organization Created
Triggers when a new organization is created in Vitally.
- Project Created
Triggers when a new project is created in Vitally.
- Task Created
Triggers when a new task is created in Vitally.
- Create Account
Creates an account (customer) in Vitally, identified by your own external ID.
- Create Note
Creates a note on an account or organization in Vitally.
- Create NPS Response
Records an NPS survey response from a user in Vitally.
- Create Organization
Creates an organization in Vitally, identified by your own external ID.
- Create Project From Template
Creates a project for an account or organization from a project template.
- Create Task
Creates a task on an account or organization in Vitally.
- Find a Customer
Returns a account by its Vitally ID or external ID.
- Find a Custom Object Instance
Finds a custom object instance by ID, external ID, linked account or a custom field value.
- Find a Note
Returns a note by its Vitally ID or external ID.
- Find a Organization
Returns a organization by its Vitally ID or external ID.
- Find a Task
Returns a task by its Vitally ID or external ID.
- Find a Teammate
Finds a Vitally team member by email address.
- Find a User
Finds a user by email address, external ID or email domain.
- Get Account Health Scores
Returns an account's health score and its breakdown.
- Update Customer Traits
Updates the name or traits of a account in Vitally; traits are merged with existing ones.
- Update Organization Traits
Updates the name or traits of a organization in Vitally; traits are merged with existing ones.
- Update Project Status
Changes a project's status in Vitally.
- Update Task
Updates a task in Vitally, for example to reassign or complete it.
- Update User Traits
Updates the name or traits of a user in Vitally; traits are merged with existing ones.
- 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 Vitally
Vitally to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Vitally to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Vitally to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Vitally to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Vitally to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Vitally to AnthropicAnthropic builds Claude, a family of large language models.
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
Vitally and Wachete, answered
What can start an automation from Vitally?
Any of Vitally's 8 triggers in the catalog, including Customer Created, Custom Object Instance Created, Custom Object Instance Updated and Note Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in Vitally?
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 Vitally?
Yes. When something happens in Wachete, your agent can act in Vitally too. This page covers both directions: Wachete's triggers and Vitally's actions are listed here as well.
Do I have to build a connector for Vitally 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 Vitally 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.