Integration
Connect Wachete and WordPress.com
When New notification for monitor fires in Wachete, your agent runs Create Comment in WordPress.com, or New Comment in WordPress.com to Create monitor in Wachete. 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 Wachete and WordPress.com to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Wachete and WordPress.com can do together
From Wachete to WordPress.com
When New notification for monitor in Wachete
then Create Comment in WordPress.com
When Any new notification in Wachete
then Create Page in WordPress.com
From WordPress.com to Wachete
When New Comment in WordPress.com
then Create monitor in Wachete
When New Post in WordPress.com
then Update monitor in Wachete
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 Wachete and WordPress.com
Triggers and actions 4 triggers · 28 actions
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.
Trigger
New CommentTriggers when a new approved comment is added to a post on your site.
Trigger
New PostTriggers when a new post is published on your site.
Action
Add mediaUploads one or more files to a WordPress.com site's media library from public URLs and returns the new media items.
Action
Create CategoryCreate a new category on a WordPress.com site.
Action
Create CommentCreate a new comment on a post on a WordPress.com site.
Action
Create PageCreate a new page on a WordPress.com site (a post with type=page).
Action
Create PostCreate a new post on a WordPress.com site. Status can be publish, draft, private, pending, or future.
Action
Create TagCreate a new tag on a WordPress.com site.
Action
Delete categoryDeletes a category from a WordPress.com site by its slug.
Action
Delete commentDeletes a comment on a WordPress.com site. The first delete moves it to the trash; deleting a trashed comment removes it permanently.
Action
Delete PostDelete (trash) a post on a WordPress.com site by post ID.
Action
Delete tagDeletes a tag from a WordPress.com site by its slug.
Action
Get commentReturns a single comment on a WordPress.com site, including its author, post, content and status.
Action
Get PostRetrieve a single post on a WordPress.com site by post ID.
Action
Get Site InfoRetrieve information about a WordPress.com site.
Action
List categoriesReturns the categories on a WordPress.com site, optionally filtered by a search term and sorted by name or post count.
Action
List CommentsList comments on a post on a WordPress.com site.
Action
List mediaReturns the items in a WordPress.com site's media library, optionally filtered by search text, file type, attached post or upload date.
Action
List PostsList posts on a WordPress.com site, optionally filtered by status, search term, or number to return.
Action
List tagsReturns the tags on a WordPress.com site, optionally filtered by a search term.
Action
List usersReturns the users of a WordPress.com site, optionally filtered by search text, role or capability.
Action
Update commentEdits an existing comment on a WordPress.com site — its text, author details, date or moderation status — and returns the updated comment.
Action
Update PostUpdate an existing post on a WordPress.com site by post ID.
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 Wachete
Wachete to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Wachete to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
Wachete to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Wachete to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wachete to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Wachete to AnthropicAnthropic builds Claude, a family of large language models.
More into WordPress.com
HubSpot to WordPress.comHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WordPress.comSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WordPress.comSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WordPress.comGoogle Sheets
Gmail to WordPress.comGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WordPress.comGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Wachete and WordPress.com, answered
What can start an automation from Wachete?
Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one.
What can your agent do in WordPress.com when something happens in Wachete?
Any of WordPress.com's 21 actions, including Create Category, Create Comment, Create Page and Create Post. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from WordPress.com to Wachete?
Yes. When something happens in WordPress.com, your agent can act in Wachete too. This page covers both directions: WordPress.com's triggers and Wachete's actions are listed here as well.
Do I have to build a connector for Wachete or WordPress.com?
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.
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.