Integration
Connect Fiskl and incident.io
When Invoice Created or Updated fires in Fiskl, your agent runs Find Users On-Call in incident.io, or New Incident in incident.io to Create Invoice in Fiskl. 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 Fiskl and incident.io 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Fiskl and incident.io can do together
From Fiskl to incident.io
When Invoice Created or Updated in Fiskl
then Find Users On-Call in incident.io
When New Client in Fiskl
then Add follow-up in incident.io
From incident.io to Fiskl
When New Incident in incident.io
then Create Invoice in Fiskl
When New Incident in incident.io
then Add credit note in Fiskl
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 Fiskl and incident.io
Triggers and actions 4 triggers · 38 actions
Trigger
Invoice Created or UpdatedTriggers when an invoice is created or updated in Fiskl.
Trigger
New ClientTriggers when a new client is created in Fiskl.
Trigger
Status UpdatedTriggers when an invoice's status changes (for example from Sent to Paid).
Action
Add credit noteCreates a draft credit note for a client, optionally against a specific issued invoice. Totals, taxes and the credit note number are calculated by Fiskl.
Action
Add fixed assetRegisters a fixed asset in Fiskl with its depreciation plan; Fiskl then posts the depreciation entries automatically.
Action
Create Account TransactionRecords a ledger transaction (expense, income, transfer, bill or receivable) with one category line. Amounts are unsigned minor units; the type gives the direction.
Action
Create ClientCreates a new client (customer) in Fiskl and returns its id.
Action
Create InvoiceCreates a draft invoice for a client with one line item. Fiskl computes totals, taxes and the invoice number; set External ID so a retry never double-invoices.
Action
Create ProductCreates a new product in your Fiskl catalog. Price is in minor currency units (15000 = 150.00).
Action
Create ServiceCreates a new service in your Fiskl catalog. Price is in minor currency units (15000 = 150.00).
Action
Create VendorCreates a new vendor (supplier) in Fiskl and returns its id.
Action
Get clientReturns a single client by its id, including company name, contact details, address and currency.
Action
Get invoiceReturns a single invoice, including its client, totals, line items and taxes.
Action
Get productReturns a single product or service from your Fiskl catalog by its id.
Action
Get transactionReturns one account transaction with its category lines, amounts, contact and status details.
Action
Get vendorReturns a single vendor (supplier) by its id, including contact details, address and archive status.
Action
List clientsReturns the clients in your Fiskl company, optionally filtered by a search pattern, specific ids, archived status or date range.
Action
List paymentsReturns the payments recorded with a payment date within the date range you choose.
Action
List productsReturns the products and services in your Fiskl catalog, optionally filtered by name, kind or currency.
Action
List quotesReturns the company's quotes, optionally filtered by text, status, client, currency, amount or date range.
Action
List transactionsReturns the transactions recorded on one bank, cash, card or payables/receivables account within a date range, newest first.
Action
List vendorsReturns the vendors in your Fiskl company, optionally filtered by name, ids, country, archived status or date range.
Action
Mark invoice as paidRecords a payment for the invoice's full outstanding balance and moves it to Paid status. Returns the updated invoice.
Action
Record PaymentRecords a payment received against an invoice. Amount is in minor currency units.
Action
Send InvoiceEmails an invoice to the client and moves it to Sent. Recipients default to the client's email.
Action
Update clientUpdates an existing client's details, such as company name, email, contact and address.
Action
Update invoiceReplaces the details and all line items of an existing Open (unsent, unpaid) invoice. Totals, taxes and the invoice number are recalculated by Fiskl.
Action
Update productUpdates an existing product or service in your Fiskl catalog, replacing its name, type, price and other details.
Action
Update vendorUpdates an existing vendor's name, contact details, address, tax identifiers and notes.
Trigger
New IncidentTriggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode.
Action
Add follow-upCreates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels.
Action
Add incident updateShares an update on an incident: a message, a move to a new status, a new severity, or any combination.
Action
Create IncidentCreates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields.
Action
Find Users On-CallFinds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied.
Action
Get incidentReturns a single incident, including its status, severity, role assignments, timestamps and custom field values.
Action
Get ScheduleReturns a single on-call schedule, including its rotations, time zone and current shifts.
Action
List actionsReturns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date.
Action
List incidentsReturns incidents in your incident.io account, optionally filtered by status, severity, type, mode and created/updated dates.
Action
List schedulesReturns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift.
Action
List severitiesReturns every incident severity configured for your incident.io organisation.
Action
List usersReturns the users in your incident.io account, optionally filtered by email address or Slack user ID.
Action
Update incidentEdits an existing incident's name, summary, severity, status, call link, Slack channel name, custom fields, role assignments or timestamps. Only the values you provide are changed.
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 Fiskl
Fiskl to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Fiskl to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Fiskl to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Fiskl to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Fiskl to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Fiskl to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into incident.io
HubSpot to incident.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to incident.ioGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to incident.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to incident.ioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to incident.ioGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to incident.ioActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Fiskl and incident.io, answered
What can start an automation from Fiskl?
Any of Fiskl's 3 triggers in the catalog, including Invoice Created or Updated, New Client and Status Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in incident.io when something happens in Fiskl?
Any of incident.io's 12 actions, including Create Incident, Update incident, Add follow-up and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from incident.io to Fiskl?
Yes. When something happens in incident.io, your agent can act in Fiskl too. This page covers both directions: incident.io's triggers and Fiskl's actions are listed here as well.
Do I have to build a connector for Fiskl or incident.io?
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 Fiskl and incident.io 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.