Integration
Connect Laposta to Expensify
When A New Relation Has Been Added fires in Laposta, your agent runs Add policy in Expensify. 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 Laposta and Expensify 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 Laposta can start in Expensify
When A New Relation Has Been Added in Laposta
then Add policy in Expensify
When A Relation Has Been Edited in Laposta
then Create Expense Report in Expensify
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 Laposta and Expensify
Triggers and actions 3 triggers · 12 actions
Trigger
A New Relation Has Been AddedTriggers when een new relation has been added to the list in your Laposta account.
Trigger
A Relation Has Been EditedTriggers when a relation of your Laposta list has been edited.
Trigger
A Relation Has Been RemovedTriggers when a relation of your Laposta list has been removed.
Action
Add or Edit a RelationEdit an existing relation, or add a new relation, in your Laposta list.
Action
Delete RelationDelete an existing relation.
Action
Add policy/Integration-Server/ExpensifyIntegrations type=create, inputSettings.type=policy (policyName, plan, owner). Creates a new policy/workspace.
Action
Create Expense ReportOnly for Expensify Premium users! Creates a new expense report.
Action
Create Single ExpenseCreates a single expense item.
Action
Export Report to PDFGiven a Report ID (from a trigger), export that report to a PDF document.
Action
Find ReportRetrieves a specific expense report, using the report's number.
Action
Get policy/Integration-Server/ExpensifyIntegrations type=get, inputSettings.type=policy, policyIDList. Returns policy details (categories, tags, employees, report fields).
Action
List policies/Integration-Server/ExpensifyIntegrations type=get, inputSettings.type=policyList. Lists policies (workspaces) accessible to the user.
Action
Update policy categories/Integration-Server/ExpensifyIntegrations type=update, inputSettings.type=policy, categories payload. Replaces/updates categories on a policy.
Action
Update policy employees/Integration-Server/ExpensifyIntegrations type=update, inputSettings.type=employees (policyID, file CSV/JSON of employees). Adds or updates employees and approval chain on a policy.
Action
Update policy tags/Integration-Server/ExpensifyIntegrations type=update, inputSettings.type=policy, tags payload. Updates tags on a policy.
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 Laposta
Laposta to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Laposta to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Laposta to MailchimpMailchimp marketing automation and email platform.
Laposta to StripeStripe is a payment processing platform for online businesses.
Laposta to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Laposta to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Expensify
HubSpot to ExpensifyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ExpensifySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ExpensifySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ExpensifyGoogle Sheets
Gmail to ExpensifyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ExpensifyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Laposta and Expensify, answered
What can start an automation from Laposta?
Any of Laposta's 3 triggers in the catalog, including A New Relation Has Been Added, A Relation Has Been Removed and A Relation Has Been Edited. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Expensify when something happens in Laposta?
Any of Expensify's 10 actions, including Create Expense Report, Create Single Expense, Update policy categories and Update policy employees. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Expensify to Laposta?
Expensify has no triggers in the catalog today, so automations start in Laposta. If you need the other direction, ask: your agent reads Expensify's API documentation and adds it.
Do I have to build a connector for Laposta or Expensify?
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.