









































Works out-of-box with your favorite AI agents

Riskonnect EHS is the health and safety solution within Riskonnect's integrated risk management platform, used by manufacturers, healthcare systems, retailers, energy companies and public bodies. It covers incident management and near-miss reporting, OSHA recordkeeping, audits and inspections, corrective and preventive actions (CAPA), job safety analysis, chemical inventory, contractor management, permit-to-work and PPE, and it connects to an LMS for training. Incidents arrive from mobile, web, email, text or API and are routed by severity and business rules to a safety officer or other owner. The module links to Riskonnect claims management.
Where a connection exposes these records, the Riskonnect EHS MCP lets safety teams query them in plain language. An EHS manager asks for incidents and near misses at one site last quarter, by type and severity, with corrective actions past due. A compliance lead checks which cases are flagged as OSHA recordable before the annual summary is posted. A site manager pulls open findings from the latest inspection of one facility. The agent can draft a near-miss report for a supervisor to complete.
You sign in to Riskonnect through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client, and get_connection_details shows which objects and fields that connection offers. Riskonnect runs on the Salesforce platform, so the connecting user's profile, permission sets and sharing rules decide which records the agent sees. Incident records often hold injury and personal details, so limit that user to the sites and record types the job needs.
Have any questions? We’re here to help You
You connect Riskonnect EHS through Makini: sign in to Riskonnect in Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client. The endpoint carries a token scoped to what the connecting user can do, and every call is logged. Ask the agent to run get_connection_details first to see which incident, inspection and other objects the connection exposes.
Yes, Riskonnect EHS tracks OSHA-recordable incidents, generates the 300 and 300A forms and supports electronic submission to OSHA. Before posting or submitting, an agent can list cases at one establishment with missing required details, or with a classification that does not match the days away recorded, for the safety coordinator to fix. The submission itself stays in Riskonnect with the person responsible.
Agentforce for Riskonnect is Riskonnect's own AI, running on Salesforce alongside Riskonnect so it shares the same data layer, security model and workflow engine. An MCP connection through Makini instead lets the assistant your team already uses, such as Claude, ChatGPT or Cursor, query Riskonnect records. In both cases the connecting user's Salesforce access decides which incidents and claims are visible.
Riskonnect scores each incident on severity, impact and business rules, then routes it automatically to the right owner, such as a safety officer, an adjuster or the legal team, and escalates to crisis management when thresholds are crossed. Intake arrives by mobile, web, email, text or API. An agent can list incidents by score and owner to show which ones have waited longest for a response.
Riskonnect Health & Safety offers configurable JSA templates with standardized workflows and bowtie analysis to visualize hazard risk, along with permit tracking for hazardous environments. Where the connection exposes these records, a supervisor can ask the agent before a shift briefing for the JSA that applies to a task and the hazards recorded for that site. The supervisor still reviews the JSA with the crew.
Yes, Riskonnect EHS links to Riskonnect claims management, and intake submissions can become either a formal incident or a claim. Where the connection exposes both, an agent can tell a risk manager which incidents from one quarter turned into claims and which stayed incident-only. Claims often hold legal and personal details, so give the connecting user claims access only if the job needs it.
An AI agent can create Riskonnect EHS incidents only where the connection allows writes and the user has permission, and the record then enters the same scoring and routing as any other report. Riskonnect also checks intake for duplicates, which matters if the agent files reports that staff may already have submitted from mobile. Start with read access and test writes in a non-production org if you have one.
Riskonnect EHS forms are dynamic and adapt to the incident or claim type, and each customer configures its own fields, picklist values and severity scales. A prompt that works for one organization may name fields that do not exist in another. Check get_connection_details before relying on a field, and agree with your EHS team what each severity or classification value means.