Integration
Connect Exist and PocketSmith
When New Attribute Value fires in Exist, your agent runs Add category in PocketSmith, or New transaction in PocketSmith to Get User Profile in Exist. 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 Exist and PocketSmith 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 Exist and PocketSmith can do together
From Exist to PocketSmith
When New Attribute Value in Exist
then Add category in PocketSmith
From PocketSmith to Exist
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 Exist and PocketSmith
Triggers and actions 2 triggers · 21 actions
- New Attribute Value
Triggers when a new daily value is recorded for the chosen Exist attribute, such as steps or mood.
- Acquire Attributes
Takes ownership of one or more Exist attributes for this app so it can write their values, creating templated attributes the user doesn't have yet.
- Create Attributes
Creates one or more new attributes in the user's Exist account, from a template or as custom attributes, and returns which succeeded and which failed.
- Get Attribute Values
Returns the daily values recorded for one of the user's Exist attributes, newest first.
- Get User Profile
Returns the authenticated Exist user's profile: name, avatar, timezone, local time and unit preferences.
- Increment Attribute Values
Adds amounts to the existing daily values of attributes your app owns in Exist, returning each attribute's new total.
- List Attributes with Values
Returns the user's Exist attributes together with their recent daily values.
- Release Attributes
Releases your ownership of one or more Exist attributes so another service can provide their data, or they become inactive.
- Update Attribute Values
Saves daily total values for attributes you own in Exist, up to 35 at a time, replacing any value already stored for those days.
- New transaction
Fires when a new transaction appears in the authorised user's PocketSmith accounts.
- Add category
Create a new category for the authorised user.
- Add transaction
Create a new transaction in a PocketSmith transaction account.
- Delete category
Delete a category by id.
- Delete transaction
Delete a transaction by id.
- Get account
Retrieve a single account by id.
- Get category
Retrieve a single category by id.
- Get transaction
Retrieve a single transaction by id.
- List accounts
List all bank/investment accounts for the authorised user.
- List categories
List all categories for the authorised user.
- List transaction accounts
List the transaction accounts (e.g. individual bank feeds) belonging to the authorised user, needed as the parent for creating transactions.
- List transactions
List transactions for the authorised user, with filters for date range, category, account, type and search text.
- Update category
Update an existing category's title, colour or parent.
- Update transaction
Update fields on an existing transaction (amount, payee, date, category, note, labels).
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 Exist
Exist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Exist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Exist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Exist to Google SheetsGoogle Sheets
Exist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Exist to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PocketSmith
Google Drive to PocketSmithGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PocketSmithMailchimp marketing automation and email platform.
Questions
Exist and PocketSmith, answered
What can start an automation from Exist?
Any of Exist's 1 trigger in the catalog, including New Attribute Value. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PocketSmith when something happens in Exist?
Any of PocketSmith's 13 actions, including Update category, Update transaction, Add category and Add transaction. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PocketSmith to Exist?
Yes. When something happens in PocketSmith, your agent can act in Exist too. This page covers both directions: PocketSmith's triggers and Exist's actions are listed here as well.
Do I have to build a connector for Exist or PocketSmith?
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.