Error Sense AI

How It Works

1. Analyzes the error response from the integration

2. Generates a short summary for quick understanding

3. Provides a detailed explanation with root cause analysis and suggested fixes

Customizing with AI Instructions

Instruction Hierarchy

1. Global Workspace

• Applies to all actions across your workspace

• Use for: naming conventions, data patterns, general context

• Example: "Our customer IDs always start with 'CUST-' prefix"

2. Integration-Level

• Applies to all actions within a specific integration (e.g., all HubSpot actions)

• Use for: API quirks, rate limits, field mappings

• Example: "In HubSpot, we use custom property 'revos_id' as the primary identifier"

3. Action-Level

• Applies to a specific action (e.g., "HubSpot - Upsert Contact")

• Use for: field requirements, validation rules, action-specific troubleshooting

• Example: "Email must match format: firstname.lastname@company.com"

When to Add Instructions

• AI explanations miss domain-specific context (custom fields, naming conventions)

• Same errors repeat and need consistent troubleshooting guidance

• Your integration has known quirks or rate limits the AI doesn't know about

• Error resolutions require internal knowledge (contacts, procedures, workarounds)

• You clicked Dislike on an explanation

• AI suggestions don't match your actual workflow

• Troubleshooting steps are outdated or incomplete

• New error patterns emerged that need documentation

• AI explanations are already accurate and helpful

• Errors are self-explanatory from the raw error message

• The issue is a one-time occurrence unlikely to repeat

Managing Instructions

• Admin role required to create, edit, or delete

• Growth or Enterprise plan

Add Instruction

Edit Instruction

1. Find the instruction card

2. Click the Edit (pencil) icon

3. Modify content in the markdown editor

4. Click Save

Delete Instruction

1. Find the instruction card

2. Click the Delete (trash) icon

3. Confirm in the dialog

Writing Effective Instructions

Best Practices

Good: "Contact email must match format: name@ourcompany.com.
      Check the source system for malformed emails."

Bad: "Make sure emails are correct."

Common issues:
- 'DUPLICATE_VALUE' - contact exists with different email
- 'INVALID_PROPERTY' - missing custom field in HubSpot

If sync fails with 'RATE_LIMIT', wait 10 minutes and retry.
Our HubSpot limit: 100 API calls per 10 seconds.

## Required Fields
- `email` - Must be unique
- `company_id` - Must exist in CRM

## Common Fixes
1. Check source data quality
2. Verify API credentials

Recommended Content by Level

Viewing Error Explanations

Where to Find

1. Navigate to a table with actions

2. Find a failed action run

3. Click Explain with AI

1. Click on a row with error message to open the executions drawer

2. Click Explain with AI

1. Open Dashboard

2. Find a failed action run

3. Click Explain with AI

AI Error Explanation Dialog

• Error Summary

• Cause Analysis

• Resolution

• Input - Data sent to the action

• Error - Raw error response from the integration

Feedback Buttons

Improving with Dislike Feedback

• Global instruction - Workspace-wide guidance

• Integration instruction - All actions in this integration

• Action instruction - This specific action

Edit Menu

Instruction Editor

• Title showing scope (Global, Integration, or Action name)

• Integration icon for context

• Markdown editor for writing instructions

• Cancel/Save buttons

How Instructions Are Applied

1. Collects applicable instructions (global + integration + action)

2. Combines them with error details and action context

3. Generates explanation incorporating your guidance

• Global: "Our CRM uses UUID format for all IDs"

• Integration: "We use 'external_id' property for matching"

• Action: "Email field is required and must be lowercase"

FAQ