Integration
Connect Fibery to Xitoring
When Entity Updated (Or Created) fires in Fibery, your agent runs Add ticket in Xitoring. 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 Xitoring 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 Xitoring
When Entity Updated (Or Created) in Fibery
then Add ticket in Xitoring
When New Entity in Fibery
then Add check in Xitoring
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 Xitoring
Triggers and actions 3 triggers · 23 actions
Trigger
Entity Updated (Or Created)Triggered when an entity in the chosen database is created or updated.
Trigger
New EntityTriggers when a new Entity (Task, Document, etc.) is created.
Trigger
New TypeTriggers when a new type is created.
Action
Add commentAdd a comment to an entity.
Action
Add EntityCreates a new Entity (Task, Document, etc.).
Action
Delete EntityDelete an entity by id.
Action
Find EntityFinds an Entity with matching field values.
Action
Get DocumentReturns the content of a Fibery rich-text document (e.g. a comment body or rich-text field) by its document secret.
Action
Get EntityRetrieve one entity by id with selected fields.
Action
Update EntityUpdates existing Entity (Task, Document, etc.).
Action
Add checkCreate a new uptime/website/server check.
Action
Add groupStore a new check/server group.
Action
Add heartbeatCreate a new heartbeat check.
Action
Add maintenance scheduleCreate a new maintenance window.
Action
Add ticketCreate a new support ticket.
Action
Delete checkDelete a check.
Action
Delete serverRemove a server from monitoring.
Action
Get checkRetrieve a single check by id.
Action
Get incidentGet a single incident's data.
Action
Get serverRetrieve a single server by id.
Action
List checksList all checks.
Action
List groupsList all groups.
Action
List maintenance schedulesList maintenance schedules.
Action
List serversList all monitored servers.
Action
Resolve incidentResolve an open incident.
Action
Update checkUpdate an existing check.
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 Xitoring
HubSpot to XitoringHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to XitoringSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to XitoringSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to XitoringGoogle Sheets
Gmail to XitoringGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to XitoringGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Fibery and Xitoring, 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 Xitoring when something happens in Fibery?
Any of Xitoring's 16 actions, including Update check, Add check, Add group and Add heartbeat. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Xitoring to Fibery?
Xitoring has no triggers in the catalog today, so automations start in Fibery. If you need the other direction, ask: your agent reads Xitoring's API documentation and adds it.
Do I have to build a connector for Fibery or Xitoring?
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 Xitoring 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.