Integration
Connect Intercom and Wachete
When New company fires in Intercom, your agent runs Create monitor in Wachete, or Any new notification in Wachete to Create message in Intercom. 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 Intercom 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)Wachete watches the web pages your team cares about, and Intercom is where you talk to customers about them. Joining the two means a change on a watched page can open a conversation, raise a ticket or leave a note on the right contact in Intercom, and new companies or contacts in Intercom can get a monitor set up in Wachete.
Example flows
What Intercom and Wachete can do together
From Intercom to Wachete
When New company in Intercom
then Create monitor in Wachete
When New or updated contact in Intercom
then Get monitor data in Wachete
From Wachete to Intercom
When Any new notification in Wachete
then Create message in Intercom
When New notification for monitor in Wachete
then Add note to contact in Intercom
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 Intercom and Wachete
Triggers and actions 6 triggers · 31 actions
Trigger
New companyFires when a new company is created.
Trigger
New conversationPolls for conversations, most recently updated first. Fires for each new conversation.
Trigger
New or updated contactPolls for contacts, most recently updated first. Fires for each new or updated contact.
Trigger
New ticketFires when a new ticket is created.
Action
Add note to contactAdds a note to the specified contact as the specified admin.
Action
Add note to conversationAdds an internal note to the specified conversation as an admin.
Action
Add tag to contactAttaches a tag to the specified contact.
Action
Assign conversationAssigns the conversation to an admin or team.
Action
Close conversationCloses the specified conversation.
Action
Create messageCreates an admin-initiated email or in-app message to a contact.
Action
Delete companyDelete a company by ID.
Action
Delete contactDeletes a contact by ID.
Action
Find admin by emailFetches an admin's details. Lists all admins; match by email.
Action
Find contact by emailSearches contacts by email and returns matches.
Action
Find ticketsSearch tickets by criteria.
Action
Get companyRetrieve a company by ID.
Action
Get contactFetches a contact's details by ID.
Action
Get conversationFetches a conversation's details by ID.
Action
Get ticketRetrieve a ticket by ID.
Action
List companiesList all companies.
Action
List segmentsList all segments.
Action
List tagsLists all tags for the workspace.
Action
Open conversationOpens (marks open) the specified conversation.
Action
Remove tag from contactDetaches a tag from the specified contact.
Action
Send conversation replySends a reply to the specified conversation as an admin.
Action
Snooze conversationSnoozes the specified conversation until the given unix timestamp.
Action
Start conversationStarts a new conversation with the specified contact.
Action
Track eventSubmit a data event for a contact.
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 Intercom
Intercom to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Intercom to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Intercom to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Intercom to StripeStripe is a payment processing platform for online businesses.
Intercom to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Intercom to PipedrivePipedrive is a sales CRM and pipeline management tool.
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
Intercom and Wachete, answered
Can a change on a watched page create a support ticket in Intercom?
Yes. A new notification for a chosen Wachete monitor can trigger the Add ticket action in Intercom, with the page name and the change details in the ticket. You can also pull the captured diff from Wachete first so the ticket carries the exact text that changed.
Can new Intercom records set up monitoring in Wachete automatically?
Yes. The New company trigger in Intercom can run the Create monitor action in Wachete using the URL held on the company record. When a contact record changes later, the Update monitor action can change the monitor's URL, name or check frequency.
What can start an automation from Intercom?
Any of Intercom's 4 triggers in the catalog, including New company, New or updated contact, New conversation and New ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in Intercom?
Any of Wachete's 7 actions, including Create monitor, Get monitor data, Update monitor and Get monitor. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wachete to Intercom?
Yes. When something happens in Wachete, your agent can act in Intercom too. This page covers both directions: Wachete's triggers and Intercom's actions are listed here as well.
Do I have to build a connector for Intercom 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 Intercom 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.