Integration
Connect PocketSmith and Quilia
When New transaction fires in PocketSmith, your agent runs Create Contact in Quilia, or Appointment Created in Quilia 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 Quilia 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)Example flows
What PocketSmith and Quilia can do together
From PocketSmith to Quilia
When New transaction in PocketSmith
then Create Contact in Quilia
When New transaction in PocketSmith
then Update a Contact in Quilia
From Quilia to PocketSmith
When Appointment Created in Quilia
then Add category in PocketSmith
When Appointment Updated in Quilia
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 Quilia
Triggers and actions 4 triggers · 31 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
Appointment CreatedTriggers when a new appointment is created in Quilia.
Trigger
Appointment UpdatedTriggers when an appointment is updated in Quilia.
Trigger
New Client ActivityTriggers when a client performs an activity in Quilia, such as uploading a document to their case.
Action
Add New ClientCreates a new client in Quilia with their name, phone, email, address and date of birth.
Action
Create ContactCreates a contact (such as a witness, adjustor, employer or medical provider) attached to a case or a client.
Action
Delete a ContactPermanently deletes a company or people contact from your Quilia organization.
Action
Delete CasePermanently deletes a case, including its members, documents and chat history.
Action
Delete ClientPermanently deletes a client from your firm, including their case memberships.
Action
Delete DocumentsDeletes one or more Quilia documents, removing both the records and their stored files.
Action
Find a DocumentFinds a document by its id and returns its type plus a secure download link that expires after 30 minutes.
Action
Find Client by PhoneFinds a client in your firm by phone number and returns the client record with the cases they belong to.
Action
Invite Clients to CaseInvites clients or staff to a Quilia case. Clients are texted an invite; staff are added as invited. Returns who was invited and who was skipped.
Action
List ClientsReturns the firm's clients, optionally filtered by name, email or phone.
Action
List Webhook EventsReturns the webhook events your Quilia firm can subscribe to, with their descriptions and payload schemas.
Action
Retrieve a Single ClientReturns a single client by id, including the cases the client belongs to.
Action
Retrieve Individual CaseReturns one case by its ID, including its status, type, dates, client, organization and case members.
Action
Simulate Webhook EventSends a sample Quilia webhook event to an endpoint URL so you can test a webhook integration.
Action
Update a ContactUpdates an existing Quilia contact (a company or a person). Only the fields you fill in are changed.
Action
Update CaseUpdates an existing case's status, type, opening date or custom CMS data. Only the fields you fill in are changed.
Action
Update Client InformationUpdates an existing client's contact details, address and demographic information. Only the fields you fill in are changed.
Action
Upload DocumentsUploads a document file to a client's case in Quilia and returns the new document ids.
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 Quilia
HubSpot to QuiliaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QuiliaGoogle Sheets
Gmail to QuiliaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QuiliaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to QuiliaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to QuiliaMailchimp marketing automation and email platform.
Questions
PocketSmith and Quilia, 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 Quilia when something happens in PocketSmith?
Any of Quilia's 18 actions, including Create Contact, Update a Contact, Update Case and Update Client Information. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Quilia to PocketSmith?
Yes. When something happens in Quilia, your agent can act in PocketSmith too. This page covers both directions: Quilia's triggers and PocketSmith's actions are listed here as well.
Do I have to build a connector for PocketSmith or Quilia?
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 PocketSmith and Quilia 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.