Skip to main content

Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack

Workflow preview

Workflow preview
100%
Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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...

Best for

  • Engineering automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatanthropic, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.if, n8n-nodes-base.gmail

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cheng Siong Chin.

Original n8n.io source

1.1 Workflow description

Title
Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack
Workflow name
Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack

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 insurance programs, it eliminates manual review of driving patterns, speed, braking, and mileage while ensuring compliance. Scheduled execution fetches telematics data via HTTP from vehicles or mobile apps. Anthropic Claude analyzes behavior with structured output parsing, generating risk scores from acceleration, harsh braking, speeding, and time-of-day driving. Calculator node applies scores to premiums, and HTTP node updates policy systems. High-risk cases trigger Gmail alerts to underwriting managers and Slack notifications to claims teams. Final HTTP sync ensures compliance across all systems.

Setup Steps

  1. Configure Schedule node for desired analysis frequency
  2. Set up HTTP node with telematics platform API
  3. Add Anthropic API key to Chat Model node for behavioral risk analysis
  4. Connect policy management system API credentials in HTTP nodes
  5. Integrate Gmail and Slack with underwriting team addresses

Prerequisites

Anthropic API key, telematics data platform API access

Use Cases

Auto insurance carriers implementing usage-based insurance programs

Customization

Modify AI prompts to incorporate additional risk factors like weather conditions

Benefits

Reduces premium calculation time from days to minutes

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Daily/Weekly Schedule

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.3

Block 2 - Workflow Configuration

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Fetch Telematics Data

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 4 - Risk Scoring AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3.1

Block 5 - Anthropic Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices
Version 1.3

Block 6 - Risk Score Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 7 - Calculate Premium Adjustment

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Update Premium in System

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 9 - Check for High Risk

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 10 - Send Risk Alert Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 11 - Send Slack Notification

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 12 - Sync with Underwriting Rules

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 13 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack
Complexity advanced
Nodes 18
Categories Engineering, AI Summarization
Author Cheng Siong Chin
Published 29 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/12279/12279.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Score telematics driving risk with Claude and adjust insurance premiums via HTTP, Gmail, and Slack do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, AI Summarization use case.