--- title: "Connect incident.io and Timing - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Create Project\" in Timing, or \"New Project\" in Timing to \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/incident-io-to-timing" --- # Connect incident.io and Timing When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Create Project** in [Timing](https://apiant.ai/connections/timing), or **New Project** in Timing to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Timing **4** triggers Timing **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 Timing 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 and Timing can do together ### From incident.io to Timing - When **New Incident** in incident.io then **Create Project** in Timing - When **New Incident** in incident.io then **Update Project** in Timing ### From Timing to incident.io - When **New Project** in Timing then **Find Users On-Call** in incident.io - When **New Team** in Timing then **Add follow-up** in incident.io 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 Timing ## Triggers and actions 5 triggers · 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. - Trigger **New Project** Triggered when a new project is created in Timing. - Trigger **New Team** Triggered when you are added to a new team in Timing. - Trigger **New Time Entry** Triggered when a new time entry is logged in Timing. - Trigger **New Timer Started and Running** Triggered when a new timer is started and is still running in Timing. - Action **Batch Update Time Entries** Updates several Timing time entries at once — moves them to a project, retitles them, sets notes, billing status or custom fields. Anything left blank is left untouched on the entries. - Action **Create Project** Creates a new project in Timing, optionally under a parent project, and returns the created project. - Action **Create Time Entry** Logs a finished block of work in Timing between a start and end time, optionally against a project, and returns the created time entry. - Action **Delete Project** Deletes a project in Timing, along with all of its child projects. - Action **Delete Time Entry** Deletes a time entry in Timing. - Action **Find Project** Searches your Timing projects by title and returns the first match, plus the full list of matches. - Action **Find Team** Finds a team you belong to in Timing by its name and returns the first match, plus every team whose name matched. - Action **Generate Report** Builds a time report in Timing over a date range, broken down by the columns you choose, and returns the report rows with their durations. - Action **Get Activity Hierarchy** Returns a readable breakdown of what you worked on in Timing over a date range, as tab-indented text grouped by project and app with durations. - Action **List Projects** Returns the projects you can see in Timing, optionally filtered by title, team, or hiding archived ones. - Action **List Team Members** Returns the active members of a Timing team. People with a pending invitation are not included. - Action **List Teams** Returns all the Timing teams you are a member of. - Action **List Time Entries** Returns your Timing time entries, optionally narrowed by date range, project, team member, search text or billing status. - Action **Show Latest Time Entry** Returns your most recent time entry in Timing. - Action **Show Project** Returns a single Timing project with its colour, notes, billing default, parent and child projects. - Action **Show Running Timer** Returns the timer that is currently running in Timing. Errors with a not-found if no timer is running. - Action **Show Time Entry** Returns a single Timing time entry with its times, duration, project, notes and billing status. - Action **Start Timer** Starts a running timer in Timing, stopping any timer that is already running, and returns the new entry. - Action **Stop Timer** Stops the timer that is currently running in Timing and returns the finished time entry. - Action **Update Project** Updates a Timing project's name, colour, notes, archive state or billing default. Anything left blank keeps its current value. - Action **Update Time Entry** Updates a Timing time entry — its times, project, title, notes or billing status. Anything left blank keeps its current value. ## 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) - [ **Timing** Timing is an automatic time tracking app for macOS.](https://apiant.ai/connections/timing) 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 Timing - [ **Favro to Timing** Plan a wedding, build an award winning video game or even send a rocket into space.](https://apiant.ai/connect/favro-to-timing) - [ **Pipefy to Timing** The easy button for processes and workflows Easily organize and run all your processes in one place, leaving...](https://apiant.ai/connect/pipefy-to-timing) - [ **HubSpot to Timing** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-timing) - [ **Salesforce to Timing** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-timing) - [ **Slack to Timing** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-timing) - [ **Gmail to Timing** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-timing) Questions ## incident.io and Timing, 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 Timing when something happens in incident.io? Any of Timing's 21 actions, including Create Project, Create Time Entry, Update Project and Update Time Entry. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Timing to incident.io? Yes. When something happens in Timing, your agent can act in incident.io too. This page covers both directions: Timing's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Timing? 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 Timing 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.