Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack
Ready for 3.0What this workflow does
This AI workflow has 12 nodes and runs on a schedule (every day at 02:00). Along the way it connects Anthropic Chat Model, Gmail and Slack.
How it runs
Trigger: On a schedule (every day at 02:00).
- Workflow Configuration (Edit Fields (Set)): sets 6 fields: telematicsApiUrl, premiumApiUrl, underwritingApiUrl…
- Fetch Telematics Data (HTTP Request): calls an HTTP API
- Risk Scoring AI Agent (AI Agent): runs an AI agent, with model: Anthropic Chat Model; output parser: Risk Score Output Parser
- Calculate Premium Adjustment (Edit Fields (Set)): sets 4 fields: premiumAdjustmentPercent, newPremiumMultiplier, adjustmentReason…
- Update Premium in System (HTTP Request): calls an HTTP API (POST)
- Check for High Risk (If): checks a condition and branches into true / false
- Send Risk Alert Email (Gmail): uses Gmail
- Send Slack Notification (Slack): uses Slack
- Sync with Underwriting Rules (HTTP Request): calls an HTTP API (POST)
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - AI Agent
@n8n/n8n-nodes-langchain.agent - Anthropic Chat Model
@n8n/n8n-nodes-langchain.lmChatAnthropic - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack
From the author
How It Works This workflow automates insurance premium adjustments by analyzing telematics data with AI-driven risk assessment and syncing changes across underwriting systems. Designed for carriers, actuaries, and underwriting teams managing usage-based…