--- title: "Connect incident.io to HitPay - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add customer\" in HitPay." canonical: "https://apiant.ai/connect/incident-io-to-hitpay" --- # Connect incident.io to HitPay When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add customer** in [HitPay](https://apiant.ai/connections/hitpay). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions HitPay **21** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and HitPay to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What incident.io can start in HitPay - When **New Incident** in incident.io then **Add customer** in HitPay - When **New Incident** in incident.io then **Add order** in HitPay 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 incident.io and HitPay ## Triggers and actions 1 trigger · 31 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds 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 incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - Action **Add customer** Creates a customer in your HitPay account with their contact details and optional address. - Action **Add order** Creates a new draft order in HitPay. - Action **Add subscription plan** Creates a subscription plan with a name, amount and billing frequency that customers can be signed up to for recurring billing. - Action **Create Payment Request** Creates a HitPay payment request and returns its checkout link for the buyer to pay. - Action **Delete customer** Deletes a customer from your HitPay account. - Action **Delete invoice** Deletes an invoice from your HitPay business account. - Action **Delete Payment Request** Deletes a payment request. Completed payment requests cannot be deleted. - Action **Delete product** Deletes a product from your HitPay product catalog. - Action **Get balances** Returns your HitPay account balances for each currency, including available, pending and reserve amounts. - Action **Get charge** Returns the details of a single HitPay charge, including amount, fees, status, payment method, customer and refunds. - Action **Get customer** Returns the details of a HitPay customer, including contact information and address. - Action **Get order** Returns the full details of a HitPay order, including its line items, charges, customer and totals. - Action **Get Payment Request Details** Returns a payment request's details and status, including its amount, customer, checkout URL and any payments made against it. - Action **Get product** Returns the details of a product, including its price, variations and images. - Action **List charges** Returns the charges (payments) on your HitPay account, optionally filtered by status, date, amount, customer, payment request or payout. - Action **List customers** Returns all customers saved in your HitPay account. - Action **List invoices** Returns the invoices in your HitPay account, optionally filtered by customer email, status or reference. - Action **List payouts** Returns payouts of your HitPay balance to your linked bank account, newest first, optionally filtered by status and creation date. - Action **List products** Returns the products in your HitPay account, optionally filtered by status, category, source, inventory, location, channel or keyword. - Action **Refund Payment** Refunds all or part of a successful payment, returning the refund record. - Action **Update customer** Updates an existing customer's details, such as name, email, phone and address. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **HitPay** HitPay is a one-stop payments and commerce platform for SMEs.](https://apiant.ai/connections/hitpay) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into HitPay - [ **HubSpot to HitPay** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-hitpay) - [ **Salesforce to HitPay** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-hitpay) - [ **Slack to HitPay** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-hitpay) - [ **Google Sheets to HitPay** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-hitpay) - [ **Gmail to HitPay** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-hitpay) - [ **Google Calendar to HitPay** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-hitpay) Questions ## incident.io and HitPay, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in HitPay when something happens in incident.io? Any of HitPay's 21 actions, including Create Payment Request, Update customer, Add customer and Add order. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from HitPay to incident.io? HitPay has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads HitPay's API documentation and adds it. ### ### Do I have to build a connector for incident.io or HitPay? 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 incident.io and HitPay 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.