Integration
Connect PocketSmith and WordPress
When New transaction fires in PocketSmith, your agent runs Add comment in WordPress, or New Comment in WordPress to Add category in PocketSmith. 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 PocketSmith and WordPress 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 PocketSmith and WordPress can do together
From PocketSmith to WordPress
When New transaction in PocketSmith
then Add comment in WordPress
When New transaction in PocketSmith
then Add page in WordPress
From WordPress to PocketSmith
When New Comment in WordPress
then Add category in PocketSmith
When New Media in WordPress
then Add transaction in PocketSmith
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 PocketSmith and WordPress
Triggers and actions 8 triggers · 29 actions
Trigger
New transactionFires when a new transaction appears in the authorised user's PocketSmith accounts.
Action
Add categoryCreate a new category for the authorised user.
Action
Add transactionCreate a new transaction in a PocketSmith transaction account.
Action
Delete categoryDelete a category by id.
Action
Delete transactionDelete a transaction by id.
Action
Get accountRetrieve a single account by id.
Action
Get categoryRetrieve a single category by id.
Action
Get transactionRetrieve a single transaction by id.
Action
List accountsList all bank/investment accounts for the authorised user.
Action
List categoriesList all categories for the authorised user.
Action
List transaction accountsList the transaction accounts (e.g. individual bank feeds) belonging to the authorised user, needed as the parent for creating transactions.
Action
List transactionsList transactions for the authorised user, with filters for date range, category, account, type and search text.
Action
Update categoryUpdate an existing category's title, colour or parent.
Action
Update transactionUpdate fields on an existing transaction (amount, payee, date, category, note, labels).
Trigger
New CommentTriggers when a new comment is posted on your WordPress site.
Trigger
New MediaTriggers when a new media item (image, video, audio or document) is uploaded to the WordPress media library.
Trigger
New pageTriggers when a new page is created on the WordPress site.
Trigger
New PostTriggers when a new post is published on your WordPress site.
Trigger
New UserTriggers when a new user registers on your WordPress site.
Trigger
Updated PostTriggers when a post is created or updated, newest changes first.
Trigger
Updated UserTriggers when a WordPress user is added or their profile is changed (name, email, roles, bio and other details).
Action
Add categoryCreates a new post category on your WordPress site and returns the created category.
Action
Add commentAdds a new comment to a WordPress post or page.
Action
Add pageCreates a new page on your WordPress site with the title, content, status and other details you provide.
Action
Add tagCreates a new tag on your WordPress site.
Action
Create PostCreates a new post on your WordPress site with the title, content, status, categories and tags you provide.
Action
Create UserCreates a new user account on your WordPress site with the login name, email and password you provide.
Action
Delete postDeletes a post, moving it to the trash or removing it permanently.
Action
Delete userPermanently deletes a WordPress user and reassigns their posts and links to another user.
Action
Find comments by criteriaFinds comments on the WordPress site matching search text, post, author, status, date range and other criteria.
Action
Find pages by criteriaReturns the pages on your WordPress site that match the search text, slug, author, status, dates and other criteria you supply.
Action
Find PostFinds posts on your WordPress site matching a search text, slug, author, category, tag, status or date range.
Action
Find UserFinds WordPress users matching a search text, slug, role or other criteria and returns the matching users.
Action
Update pageUpdates an existing page on your WordPress site. Only the fields you fill in are changed.
Action
Update PostUpdates an existing WordPress post's title, content, status, categories, tags and other details. Only the fields you fill in are changed.
Action
Update UserUpdates an existing WordPress user's profile, such as their name, email, roles or password. Fields left blank are not changed.
Action
Upload MediaUploads a file from a URL to the WordPress media library and returns the new media item.
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 PocketSmith
PocketSmith to Open Government, ArgentinaArgentina Government Open Data. Public open-data portal — search dataset catalogs and retrieve published...
PocketSmith to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PocketSmith to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
PocketSmith to StripeStripe is a payment processing platform for online businesses.
PocketSmith to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
PocketSmith to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into WordPress
HubSpot to WordPressHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WordPressSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WordPressSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WordPressGoogle Sheets
Gmail to WordPressGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WordPressGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
PocketSmith and WordPress, answered
What can start an automation from PocketSmith?
Any of PocketSmith's 1 trigger in the catalog, including New transaction. Describe the moment in plain language and your agent picks the right one.
What can your agent do in WordPress when something happens in PocketSmith?
Any of WordPress's 16 actions, including Create Post, Create User, Update page and Update Post. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from WordPress to PocketSmith?
Yes. When something happens in WordPress, your agent can act in PocketSmith too. This page covers both directions: WordPress's triggers and PocketSmith's actions are listed here as well.
Do I have to build a connector for PocketSmith or WordPress?
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.