Integration
Connect Fibery to FilePost
When Entity Updated (Or Created) fires in Fibery, 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 Fibery 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 Fibery can start in FilePost
When Entity Updated (Or Created) in Fibery
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 Fibery and FilePost
Triggers and actions 3 triggers · 17 actions
- Entity Updated (Or Created)
Triggered when an entity in the chosen database is created or updated.
- New Entity
Triggers when a new Entity (Task, Document, etc.) is created.
- New Type
Triggers when a new type is created.
- Add comment
Add a comment to an entity.
- Add Entity
Creates a new Entity (Task, Document, etc.).
- Delete Entity
Delete an entity by id.
- Find Entity
Finds an Entity with matching field values.
- Get Document
Returns the content of a Fibery rich-text document (e.g. a comment body or rich-text field) by its document secret.
- Get Entity
Retrieve one entity by id with selected fields.
- Update Entity
Updates existing Entity (Task, Document, etc.).
- 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 Fibery
Fibery to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Fibery to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Fibery to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Fibery to Google SheetsGoogle Sheets
Fibery to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Fibery to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into FilePost
Questions
Fibery and FilePost, answered
What can start an automation from Fibery?
Any of Fibery's 3 triggers in the catalog, including Entity Updated (Or Created), New Entity and New Type. Describe the moment in plain language and your agent picks the right one.
What can your agent do in FilePost when something happens in Fibery?
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 Fibery?
FilePost has no triggers in the catalog today, so automations start in Fibery. 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 Fibery 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 Fibery 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.