Integration
Connect PocketSmith and Saasu
When New transaction fires in PocketSmith, your agent runs Create Contact in Saasu, or New Contact in Saasu 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 Saasu 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 Saasu can do together
From PocketSmith to Saasu
When New transaction in PocketSmith
then Create Contact in Saasu
When New transaction in PocketSmith
then Create Item Invoice in Saasu
From Saasu to PocketSmith
When New Contact in Saasu
then Add category in PocketSmith
When New Contact in Saasu
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 Saasu
Triggers and actions 2 triggers · 34 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 ContactTriggers when a new contact is added to your Saasu file.
Action
Add activityCreates an activity (task, call, meeting, note) in your Saasu file, optionally attached to a contact or transaction.
Action
Add companyCreates a company record in Saasu.
Action
Add itemCreates an inventory or combo item in Saasu.
Action
Add journalCreates a manual journal entry with debit and credit lines in a Saasu file.
Action
Create ContactCreates a new contact (person) in your Saasu file and returns its id.
Action
Create Item InvoiceCreates an item-layout invoice, quote or order in Saasu with inventory item line items.
Action
Create Service InvoiceCreates a service-layout sale or purchase invoice in Saasu, with line items described by account and amount.
Action
Delete contactDeletes a contact from your Saasu file.
Action
Delete invoiceDeletes a sale or purchase invoice from the Saasu file.
Action
Delete itemDeletes an inventory item from the Saasu file.
Action
Email invoiceEmails a Saasu invoice to the email address you specify.
Action
Find accountsReturns the accounts in your Saasu chart of accounts, filtered by type, status, bank-account flag or header account.
Action
Find companiesReturns the companies in your Saasu file whose name matches, optionally limited to a last-modified date range.
Action
Find ContactFinds Saasu contacts matching an email, name, company or other criteria and returns the matching contacts.
Action
Find itemsReturns the inventory and combo items whose code or description matches the search text.
Action
Get contactReturns a single Saasu contact by its ID.
Action
Get invoiceReturns a single Saasu invoice (sale or purchase) by its ID, including line items and totals.
Action
Get journalReturns a single journal transaction, including its date, reference, summary and journal line items.
Action
Update contactUpdates an existing contact in Saasu, such as their name, email, phone numbers, addresses and customer/supplier flags.
Action
Update invoiceUpdates an existing Saasu sale or purchase invoice, replacing its details and line items.
Action
Update itemUpdates an existing inventory or combo item in Saasu, such as its code, description, prices, accounts and tax codes.
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 Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
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.
More into Saasu
HubSpot to SaasuHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SaasuGoogle Sheets
Gmail to SaasuGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SaasuGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SaasuGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to SaasuMailchimp marketing automation and email platform.
Questions
PocketSmith and Saasu, 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 Saasu when something happens in PocketSmith?
Any of Saasu's 21 actions, including Create Contact, Create Item Invoice, Create Service Invoice and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Saasu to PocketSmith?
Yes. When something happens in Saasu, your agent can act in PocketSmith too. This page covers both directions: Saasu's triggers and PocketSmith's actions are listed here as well.
Do I have to build a connector for PocketSmith or Saasu?
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.