--- title: "Connect Open Science Framework and ilert - APIANT.ai" description: "When \"New comment\" fires in Open Science Framework, your agent runs \"Find User on Call\" in ilert." canonical: "https://apiant.ai/connect/ilert-to-open-science-framework" --- # Connect Open Science Framework and ilert When **New comment** fires in [Open Science Framework](https://apiant.ai/connections/open-science-framework), your agent runs **Find User on Call** in [ilert](https://apiant.ai/connections/ilert), or **New or Updated Incident** in ilert to **Get file** in Open Science Framework. Describe the whole flow and it is built, tested on every scenario and kept running. Open Science Framework **3** triggers Open Science Framework **19** actions ilert **1** trigger ilert **12** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Open Science Framework and ilert 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 Open Science Framework and ilert can do together ### From Open Science Framework to ilert - When **New comment** in Open Science Framework then **Find User on Call** in ilert - When **New preprint** in Open Science Framework then **Add Alert** in ilert ### From ilert to Open Science Framework - When **New or Updated Incident** in ilert then **Get file** in Open Science Framework - When **New or Updated Incident** in ilert then **Get project** in Open Science Framework 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 Open Science Framework and ilert ## Triggers and actions 4 triggers · 31 actions - Trigger **New comment** Polling trigger that fires when a new comment is added to an OSF project. - Trigger **New preprint** Polling trigger that fires when a new OSF preprint is created. - Trigger **New registration** Polling trigger that fires when a new OSF registration is created. - Action **Get collection** Retrieve a single OSF collection. - Action **Get contributor** Retrieve a single contributor on an OSF project. - Action **Get file** Retrieve metadata for a single OSF file. - Action **Get preprint** Retrieve a single OSF preprint. - Action **Get project** Retrieve a single OSF project by id. - Action **Get registration** Retrieve a single OSF registration. - Action **Get resource** Retrieve a single OSF outcome resource. - Action **Get user** Retrieve a single OSF user. - Action **Get wiki page** Retrieve a single OSF wiki page. - Action **List collections** List OSF collections. - Action **List comments** List comments on an OSF project. - Action **List contributors** List the contributors on an OSF project. - Action **List preprints** List OSF preprints. - Action **List project files** List the files stored in an OSF project. - Action **List projects** List OSF projects (nodes) visible to the user. - Action **List registrations** List OSF registrations. - Action **List resources** List OSF outcome resources. - Action **List users** List OSF users. - Action **List wiki pages** List the wiki pages on an OSF project. - Trigger **New or Updated Incident** Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed. - Action **Accept Incident** Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert. - Action **Add Alert** Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify). - Action **Add maintenance window** Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time. - Action **Create Incident** Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified. - Action **Find User on Call** Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call. - Action **Get alert** Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders. - Action **Get incident** Returns a single ilert incident by its id, including its status, severity, affected services and responders. - Action **Get maintenance window** Fetches a maintenance window by ID. An error occurs if the maintenance window is not found. - Action **List Alert Sources** Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy. - Action **List incidents** Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date. - Action **List users** Returns the users in your ilert account, with their name, email, role and contact settings. - Action **Resolve Incident** Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation. ## Each app on its own - [ **Open Science Framework** The Open Science Framework (OSF) is a repository and archive for research projects — study designs...](https://apiant.ai/connections/open-science-framework) - [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert) Reviews ## What our customers say ## More from Open Science Framework - [ **Open Science Framework to TrackingTime** Time Tracking app that helps to manage projects, track working times and measure productivity.](https://apiant.ai/connect/open-science-framework-to-trackingtime) - [ **Open Science Framework to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/open-science-framework-to-salesforce) - [ **Open Science Framework to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/open-science-framework-to-slack) - [ **Open Science Framework to Google Sheets** Google Sheets](https://apiant.ai/connect/open-science-framework-to-google-sheets) - [ **Open Science Framework to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/open-science-framework-to-stripe) - [ **Open Science Framework to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/open-science-framework-to-shopify) ## More into ilert - [ **HubSpot to ilert** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ilert) - [ **Google Sheets to ilert** Google Sheets](https://apiant.ai/connect/google-sheets-to-ilert) - [ **Gmail to ilert** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ilert) - [ **Google Calendar to ilert** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ilert) - [ **Google Drive to ilert** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-ilert) - [ **ActiveCampaign to ilert** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-ilert) Questions ## Open Science Framework and ilert, answered ### ### What can start an automation from Open Science Framework? Any of Open Science Framework's 3 triggers in the catalog, including New comment, New preprint and New registration. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in ilert when something happens in Open Science Framework? Any of ilert's 12 actions, including Create Incident, Accept Incident, Add Alert and Add maintenance window. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from ilert to Open Science Framework? Yes. When something happens in ilert, your agent can act in Open Science Framework too. This page covers both directions: ilert's triggers and Open Science Framework's actions are listed here as well. ### ### Do I have to build a connector for Open Science Framework or ilert? 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 Open Science Framework and ilert 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.