What it does
OSHA Incident Report Classifier helps EHS and compliance teams evaluate workplace incidents against OSHA 29 CFR 1904 recordkeeping requirements. It deterministically determines recordability, identifies the correct OSHA 300 Log column (G-J), flags time-sensitive OSHA notification deadlines (8 hours for fatalities, 24 hours for amputations/hospitalization/loss of an eye), and generates Form 300/301 obligation summaries. When live credentials are configured, the agent creates an EHS incident record in Notion and sends an alert to the EHS manager's Slack channel. All output carries a decision-support disclaimer — human EHS Manager review is required before any regulatory filing. Built for manufacturing and industrial safety teams who need fast, consistent OSHA recordability triage instead of manually parsing 29 CFR 1904 for every incident.
Example prompts
- Classify this workplace incident under OSHA 29 CFR 1904
- Is this incident OSHA recordable and which 300 Log column applies?
- Check if OSHA notification is required for this fatality
- Run the full OSHA classification and log it in Notion
Tools (7)
Tools the agent exposes — your AI client calls them automatically when it needs them.
- run_full — Run the OSHA incident classification pipeline end-to-end: classify under 29 CFR 1904, synthesize narrative, create Notion EHS record, send Slack notification.
- classify_incident — Classify a workplace incident under OSHA 29 CFR 1904 recordkeeping rules (deterministic, no LLM).
- check_notification_requirements — Check whether and how urgently OSHA must be notified of a workplace incident.
- assess_recordability — Quickly assess whether a workplace incident is OSHA recordable and the relevant 300 Log column.
- plan_inputs — Plan/brainstorm the inputs for a tool: returns questions, schema and a ready-to-edit example.
- list_capabilities — List the agent's tools and descriptions.
- discover_intent — Map a free-text description of what the user wants to do to the most relevant OSHA tool.
What you'll need to connect
This agent will ask you for the following. You enter them when you connect — they're encrypted and never shared with the creator.
- Notion API Key · optionalOptional. When set, the agent creates an OSHA incident record in your Notion EHS database after classification.Create an internal integration in Notion (notion.so/my-integrations) and copy its secret, then share the relevant pages with that integration.Paste the value as a single line.Only sent to: api.notion.com
- Slack Bot Token · optionalOptional. When set, the agent sends an OSHA incident alert to the EHS manager's Slack channel. Must start with xoxb-.Create a Slack app (api.slack.com/apps), add the scopes the agent needs, install it to your workspace, and copy the bot/user token.Paste the value as a single line.Only sent to: slack.com
- EHS Slack Channel · optionalSlack channel ID or name where OSHA incident alerts are sent. Required when Slack Bot Token is set.Create a Slack app (api.slack.com/apps), add the scopes the agent needs, install it to your workspace, and copy the bot/user token.Paste the value as a single line.Only sent to: slack.com
- Service account JSON · optionalGet this from *'s account or API settings.Paste the full JSON of your service-account key file (not a file path). FindAgent stores it securely and gives the agent a file path to it.Only sent to: *
- Anthropic API Key · optionalOptional. Leave blank on a sampling-capable client to use the host model with no key.Create a key on the Anthropic Console API keys page (console.anthropic.com → API keys).Paste the value as a single line.Only sent to: api.anthropic.com
How you're protected
FindAgent runs these safety checks on every agent automatically. They're always on and can't be turned off.
- Prompt-injection scanning
Every request is checked for known prompt-injection and jailbreak attempts before the agent runs. This is always on.
- Secret-leak scanning
Every response is scanned for leaked API keys, tokens, and other secrets before it reaches you. This is always on.