--- title: "Connect incident.io to Temsor - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Verify email\" in Temsor." canonical: "https://apiant.ai/connect/incident-io-to-temsor" --- # Connect incident.io to Temsor When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Verify email** in [Temsor](https://apiant.ai/connections/temsor). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Temsor **11** 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 Temsor 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 Temsor - When **New Incident** in incident.io then **Verify email** in Temsor - When **New Incident** in incident.io then **Close promise** in Temsor 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 Temsor ## Triggers and actions 1 trigger · 21 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 **Close promise** Marks an open call promise as kept or broken, with an optional short note, and returns the updated promise. - Action **Find calls by query** Searches the call archive and returns the calls, call promises and extracted facts that match a text query, optionally narrowed by promise status, extension, competitor, date range or the extension a promise got stuck at. - Action **Get call** Returns one call by its id, including its transfer path, handoff graph and count of open promises. - Action **List calls** Returns the most recent calls in your Temsor call archive, with each call's direction, trunk, summary, transfer path and open promise count. - Action **List persons** Returns the people seen in your call history — callers with their phones and names, and extensions seen on transfers — optionally filtered by call, kind or search text. - Action **List promises** Returns the call promises tracked for agent handoff, filtered by status (open by default), each with its caller, promise text, transfer path and where it got stuck. - Action **Redact text** Erases a caller's personal data from the Temsor call index — a promise, call, person, fact or utterance by id, or everything linked to a caller's phone number — by anonymizing or deleting it, and records an audit entry. - Action **Validate IBAN** Validates an IBAN from any of 70+ countries, checking its checksum, country length and account structure, and returns the bank and branch codes plus a corrected suggestion when only the check digits are wrong. - Action **Validate phone number** Validates a phone number and returns it in standard international (E.164) and national form, with its country and line type. - Action **Validate Turkish ID** Validates a Turkish identifier — national ID (TCKN), tax number (VKN), IBAN, licence plate, IMEI, barcode, KEP address, MERSİS number, postal code or ISBN — detecting the type automatically when you don't specify it, and returns whether it is valid plus resolved details. - Action **Verify email** Checks an email address: its syntax, whether the domain can receive mail, whether it is disposable or a role account, and suggests a correction for common domain typos. ## 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) - [ **Temsor** Validates Turkish national ID, tax number, IBAN, phone, plate and parses addresses](https://apiant.ai/connections/temsor) 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 Temsor - [ **HubSpot to Temsor** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-temsor) - [ **Salesforce to Temsor** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-temsor) - [ **Slack to Temsor** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-temsor) - [ **Google Sheets to Temsor** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-temsor) - [ **Gmail to Temsor** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-temsor) - [ **Google Calendar to Temsor** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-temsor) Questions ## incident.io and Temsor, 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 Temsor when something happens in incident.io? Any of Temsor's 11 actions, including Close promise, Find calls by query, Get call and List calls. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Temsor to incident.io? Temsor has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Temsor's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Temsor? 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 Temsor 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.