Integration
Connect MOCO to FilePost
When New Client fires in MOCO, your agent runs Update file in FilePost. 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 MOCO and FilePost 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 MOCO can start in FilePost
When New Client in MOCO
then Update file in FilePost
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 MOCO and FilePost
Triggers and actions 26 triggers · 34 actions
- New Client
Triggers when a new client is created.
- New Company
Triggers when a new company is created.
- New Expense
Triggers when an expense is created.
- New Exported Invoice (Bookkeeping)
Triggers when a new invoice is exported (for the bookkeeping).
- New Incoming Payment
Triggers when a new incoming payment is created.
- New Invoice
Triggers when a new invoice is created.
- New Invoice Status
Triggers when the status of an invoice is changed.
- New Offer
Triggers when a new offer is created.
- New Outgoing Payment
Triggers when a new outgoing payment is created.
- New Planning Entry
Triggers when a new Planning Entry is created.
- New Presence
Triggers when a new Presence is created.
- New Project Assignment
Triggers when a person is assigned to a project.
- New Purchase
Triggers when a new purchase is created.
- New Recurred Expense
Triggers when an expense is recurred.
- New Task
Triggers when a new task is created.
- New Time Entry
Triggers when a new time entry is created.
- Unarchived Project
Triggers when a project is made active again.
- Updated Company
Triggers when a company was updated.
- Updated Expense
Triggers when an expense was updated.
- Updated Invoice
Triggers when an invoice was updated.
- Updated Lead
Triggers when a lead was updated.
- Updated Planning Entry
Triggers when a Planning Entry was updated.
- Updated Presence
Triggers when a Presence was updated.
- Updated Project
Triggers when a project was updated.
- Updated Purchase
Triggers when a purchase was updated.
- Updated Time Entry
Triggers when a time entry was updated.
- Create Comment
Creates a new Comment.
- Create Company
Creates a new company (customer only).
- Create Contact
Creates a new contact person.
- Create Expense
Creates a new Expense.
- Create Incoming Payment
Creates a new incoming payment.
- Create Lead
Creates a new lead.
- Create Outgoing Payment
Creates a new outgoing payment.
- Create Project
Creates a new Project.
- Create Purchase
Creates a new Purchase.
- Create Task
Creates a new project task.
- Create Time Entry
Create a new time entry.
- Find Company
Finds an existing Company.
- Find Contact
Finds an existing Contact.
- Find Expense
Finds an existing Expense.
- Find Invoice
Finds an existing Invoice.
- Find Lead
Finds an existing lead.
- Find Offer
Finds an existing Offer.
- Find Planning Entry
Finds an existing Planning Entry.
- Find Project
Finds an existing project.
- Find Purchase
Finds an existing Purchase.
- Find Task
Finds an active Task for a Project.
- Find Time Entry
Finds an existing Time Entry.
- Find User
Finds an existing active user.
- Record Presence
Record a new presence.
- Create Intake Link
Creates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
- Delete File
Permanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
- Delete intake link
Closes a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
- Get file
Returns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
- Get intake link
Returns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
- List Files
Returns the files stored in your FilePost account, newest first, together with the total number of files.
- List intake links
Returns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
- Update file
Changes whether a stored file's name appears in its public link, and returns the file with its new link.
- Upload File
Uploads a file to FilePost and returns its shareable link.
- Upload File From URL
Stores a file from a public web link in FilePost and returns its shareable link.
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 MOCO
MOCO to ip-apiip-api resolves an IP address or domain name to a physical location.
MOCO to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MOCO to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MOCO to StripeStripe is a payment processing platform for online businesses.
MOCO to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MOCO to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into FilePost
HubSpot to FilePostHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to FilePostGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to FilePostGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FilePostGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MOCO and FilePost, answered
What can start an automation from MOCO?
Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Expense and New Exported Invoice (Bookkeeping). Describe the moment in plain language and your agent picks the right one.
What can your agent do in FilePost when something happens in MOCO?
Any of FilePost's 10 actions, including Create Intake Link, Update file, Upload File and Upload File From URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from FilePost to MOCO?
FilePost has no triggers in the catalog today, so automations start in MOCO. If you need the other direction, ask: your agent reads FilePost's API documentation and adds it.
Do I have to build a connector for MOCO or FilePost?
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 MOCO and FilePost 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.