--- title: "Connect Coworks to Instatus - APIANT.ai" description: "When \"Contact Updated\" fires in Coworks, your agent runs \"Add component\" in Instatus." canonical: "https://apiant.ai/connect/coworks-to-instatus" --- # Connect Coworks to Instatus When **Contact Updated** fires in [Coworks](https://apiant.ai/connections/coworks), your agent runs **Add component** in [Instatus](https://apiant.ai/connections/instatus). Describe the whole flow and it is built, tested on every scenario and kept running. Coworks **10** triggers Coworks **7** actions Instatus **14** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Coworks and Instatus 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 Coworks can start in Instatus - When **Contact Updated** in Coworks then **Add component** in Instatus - When **CRM Entry Updated** in Coworks then **Add incident update** in Instatus 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 Coworks and Instatus ## Triggers and actions 10 triggers · 21 actions - Trigger **Contact Updated** Triggers when a contact in your Coworks CRM is created or changed. - Trigger **CRM Entry Updated** Triggers when a CRM contact or lead is added or changed in Coworks. - Trigger **Lead Updated** Triggers when a lead in Coworks is created or changed, including changes to its status, custom fields, or any other returned detail. - Trigger **Member Deactivate** Triggered when a member is deactivated and is no longer an active member. - Trigger **Member Updated** Triggers when a member is added or any of a member's details change. - Trigger **New Checkin** Triggered when a new check-in is recorded for a member, visitor or passport holder in your Coworks community. - Trigger **New Contact** Triggered when a new contact is created in your Coworks CRM. - Trigger **New CRM Entry** Triggered when a new CRM entry, either a contact or a lead, is created. - Trigger **New Lead** Triggers when a new lead is created in the Coworks CRM. - Trigger **New Member** Triggered when a new member is created in your Coworks community. - Action **Get room occupancy** Returns the rooms at a campus with their occupancy, optionally limited to one room type. - Action **List active memberships** Returns the community's paid memberships, optionally limited to one status. Free subscriptions are not included. - Action **List checkins** Returns check-ins for your Coworks community, optionally filtered by campus, check-in type, date range or person name. - Action **List CRM contacts and leads** Returns the contacts and leads in your Coworks CRM, optionally filtered by campus, type, lead status, source and date. - Action **List members** Returns the members of your Coworks community, optionally narrowed to specific teams or a campus, and optionally including inactive members. - Action **List rooms** Returns the rooms at a campus, optionally narrowed to one room type. - Action **List teams** Returns the teams in your Coworks community, optionally narrowed by team, campus, or join date. - Action **Add component** Creates a new component on an Instatus status page and returns the created component. - Action **Add incident update** Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses. - Action **Add maintenance** Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options. - Action **Add subscriber** Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones. - Action **Create Incident** Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers. - Action **Delete incident** Deletes an incident from an Instatus status page. - Action **Get component** Returns one component on an Instatus status page, including its name, current status, description and group. - Action **Get incident** Returns a single incident on a status page, including its updates, affected components and the teammate who created it. - Action **Get maintenance** Returns one scheduled maintenance on a status page, including its updates and affected components. - Action **List components** Returns the components on an Instatus status page, with each component's name, status and group. - Action **List maintenances** Returns the scheduled, in-progress and completed maintenances on an Instatus status page. - Action **List status pages** Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status. - Action **List subscribers** Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status. - Action **Update component** Updates a component on an Instatus status page, such as its name, description, status, order or group. ## Each app on its own - [ **Coworks** Coworks is a coworking management platform solution for automating running a coworking space.](https://apiant.ai/connections/coworks) - [ **Instatus** Instatus is a tool to monitor services, manage incidents with your team, and share real-time status with...](https://apiant.ai/connections/instatus) Reviews ## What our customers say ## More from Coworks - [ **Coworks to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/coworks-to-hubspot) - [ **Coworks to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/coworks-to-salesforce) - [ **Coworks to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/coworks-to-slack) - [ **Coworks to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/coworks-to-google-sheets) - [ **Coworks to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/coworks-to-gmail) - [ **Coworks to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/coworks-to-google-calendar) ## More into Instatus - [ **HubSpot to Instatus** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-instatus) - [ **Salesforce to Instatus** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-instatus) - [ **Slack to Instatus** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-instatus) - [ **Google Sheets to Instatus** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-instatus) - [ **Gmail to Instatus** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-instatus) - [ **Google Calendar to Instatus** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-instatus) Questions ## Coworks and Instatus, answered ### ### What can start an automation from Coworks? Any of Coworks's 10 triggers in the catalog, including Contact Updated, CRM Entry Updated, Lead Updated and Member Updated. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Instatus when something happens in Coworks? Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Instatus to Coworks? Instatus has no triggers in the catalog today, so automations start in Coworks. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it. ### ### Do I have to build a connector for Coworks or Instatus? 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 Coworks and Instatus 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.