Integration
Connect Vitally and wethod
When Customer Created fires in Vitally, your agent runs Create a contact in wethod, or New Client in wethod 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 wethod 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 wethod can do together
From Vitally to wethod
When Customer Created in Vitally
then Create a contact in wethod
When Custom Object Instance Created in Vitally
then Create an invoice in wethod
From wethod to Vitally
When New Client in wethod
then Create Task in Vitally
When New Contact in wethod
then Update Customer Traits in 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 wethod
Triggers and actions 15 triggers · 70 actions
Trigger
Customer CreatedTriggers when a new account (customer) is created in Vitally.
Trigger
Custom Object Instance CreatedTriggers when a new instance of a custom object is created.
Trigger
Custom Object Instance UpdatedTriggers when an instance of a custom object is created or updated.
Trigger
Note CreatedTriggers when a new note is created in Vitally.
Trigger
NPS Response CreatedTriggers when a new NPS response is recorded in Vitally.
Trigger
Organization CreatedTriggers when a new organization is created in Vitally.
Trigger
Project CreatedTriggers when a new project is created in Vitally.
Trigger
Task CreatedTriggers when a new task is created in Vitally.
Action
Create AccountCreates an account (customer) in Vitally, identified by your own external ID.
Action
Create NoteCreates a note on an account or organization in Vitally.
Action
Create NPS ResponseRecords an NPS survey response from a user in Vitally.
Action
Create OrganizationCreates an organization in Vitally, identified by your own external ID.
Action
Create Project From TemplateCreates a project for an account or organization from a project template.
Action
Create TaskCreates a task on an account or organization in Vitally.
Action
Create UserCreates a user in Vitally and links them to accounts or organizations.
Action
Find a CustomerReturns a account by its Vitally ID or external ID.
Action
Find a Custom Object InstanceFinds a custom object instance by ID, external ID, linked account or a custom field value.
Action
Find a NoteReturns a note by its Vitally ID or external ID.
Action
Find a OrganizationReturns a organization by its Vitally ID or external ID.
Action
Find a TaskReturns a task by its Vitally ID or external ID.
Action
Find a TeammateFinds a Vitally team member by email address.
Action
Find a UserFinds a user by email address, external ID or email domain.
Action
Get Account Health ScoresReturns an account's health score and its breakdown.
Action
Update Customer TraitsUpdates the name or traits of a account in Vitally; traits are merged with existing ones.
Action
Update Organization TraitsUpdates the name or traits of a organization in Vitally; traits are merged with existing ones.
Action
Update Project StatusChanges a project's status in Vitally.
Action
Update TaskUpdates a task in Vitally, for example to reassign or complete it.
Action
Update User TraitsUpdates the name or traits of a user in Vitally; traits are merged with existing ones.
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
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 wethod
HubSpot to wethodHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to wethodSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to wethodSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to wethodGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to wethodGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to wethodGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Vitally and wethod, 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 wethod when something happens in Vitally?
Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from wethod to Vitally?
Yes. When something happens in wethod, your agent can act in Vitally too. This page covers both directions: wethod's triggers and Vitally's actions are listed here as well.
Do I have to build a connector for Vitally or wethod?
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 wethod 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.