Integration
Connect Enchant and Tars
When New Customer fires in Enchant, your agent runs Create Contact in Tars, or New Call in Tars to Add Labels to Ticket in Enchant. 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 Enchant and Tars 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 Enchant and Tars can do together
From Enchant to Tars
When New Customer in Enchant
then Create Contact in Tars
When New or Updated Ticket in Enchant
then Send Campaign Message in Tars
From Tars to Enchant
When New Call in Tars
then Add Labels to Ticket in Enchant
When New Contact in Tars
then Create Contact in Enchant
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 Enchant and Tars
Triggers and actions 5 triggers · 31 actions
Trigger
New CustomerTriggers when a new customer is added to the help desk.
Trigger
New or Updated TicketTriggers when a ticket is created or changes (new message, state, assignee, labels).
Trigger
New Ticket CreatedTriggers when a new ticket is created, optionally only in the inboxes you choose.
Action
Add Labels to TicketAdds one or more labels to a ticket, keeping its existing labels.
Action
Create AttachmentUploads a file as an attachment so its id can be added to a note or reply.
Action
Create ContactAdds an email address, phone number or Twitter handle to a customer.
Action
Create CustomerCreates a customer in your Enchant help desk, optionally with an email address.
Action
Create TicketCreates an email ticket for a customer, matched or created by email, with the customer's first message.
Action
Delete ContactDeletes one contact (email, phone or Twitter handle) from a customer.
Action
Find Customer by EmailFinds the customer with a given email address.
Action
Get AttachmentReturns an attachment's file name, MIME type and size.
Action
Get CustomerReturns one customer with their name, summary and contacts.
Action
Get TicketReturns one ticket by its id.
Action
List customersReturns customers from your Enchant help desk, optionally filtered by contact or creation date.
Action
List messagesReturns all replies and notes on a ticket, oldest to newest as Enchant lists them.
Action
List TicketsReturns up to 100 tickets, newest first, optionally filtered by state, inbox or assigned user.
Action
List UsersReturns the help desk's users (agents) with their names and email addresses.
Action
Remove Labels from TicketRemoves one or more labels from a ticket.
Action
Update CustomerUpdates a customer's name or summary. Only the fields you fill in change.
Action
Update TicketUpdates a ticket's state, assigned user, inbox or subject. Only the fields you fill in change.
Trigger
New CallTriggers when a new voice call is registered in Tars.
Trigger
New ContactTriggers when a new contact is added in Tars.
Action
Create ContactCreates a Tars contact. The contact needs an email or a phone number.
Action
Delete Call ContentDeletes a Tars call's content (transcript, recordings and variables).
Action
Delete ContactDeletes a Tars contact.
Action
Get AgentReturns one Tars agent with its kind, status and published version.
Action
Get Call ConcurrencyReturns how many Tars calls are running now against your concurrency limit.
Action
Get ContactReturns one Tars contact by its ID, with name, email, phone, tags and origin.
Action
List AgentsReturns your Tars chat and voice agents.
Action
List CallsReturns Tars voice calls, newest first, optionally for one agent.
Action
List ContactsReturns Tars contacts, optionally filtered by tag or origin.
Action
List Phone NumbersReturns the phone numbers in your Tars organization.
Action
Send Campaign MessageSends a Tars campaign message (e.g. a WhatsApp template) to one phone number.
Action
Start ConversationStarts a conversation with a user through a Tars chat agent's trigger, e.g. a WhatsApp message.
Action
Update ContactUpdates a Tars contact's name, email, phone or tags. Send at least one.
Action
Validate Campaign MessageChecks a Tars campaign message for a recipient and returns its quoted price, without sending it.
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 Enchant
Enchant to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Enchant to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Enchant to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Enchant to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Enchant to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Enchant to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Tars
HubSpot to TarsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TarsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TarsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TarsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TarsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TarsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Enchant and Tars, answered
What can start an automation from Enchant?
Any of Enchant's 3 triggers in the catalog, including New Customer, New or Updated Ticket and New Ticket Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Tars when something happens in Enchant?
Any of Tars's 14 actions, including Create Contact, Send Campaign Message, Update Contact and Get Agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tars to Enchant?
Yes. When something happens in Tars, your agent can act in Enchant too. This page covers both directions: Tars's triggers and Enchant's actions are listed here as well.
Do I have to build a connector for Enchant or Tars?
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 Enchant and Tars 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.