Skip to main content
Trigger Hooks provide a powerful automation framework that executes custom actions when specific events occur in your AI Sync system. Unlike webhooks that send data to external endpoints, trigger hooks perform internal actions and workflows within your AI Sync environment.

​
🔄 Trigger Hook Workflow

1

Event Detection

System monitors for specified events (calls, agent actions, campaigns)
2

Condition Evaluation

Trigger conditions are evaluated against event data and context
3

Hook Execution

Qualifying events trigger the configured hook actions
4

Action Processing

Multiple actions can be executed sequentially or in parallel
5

Result Logging

Execution results and outcomes are logged for monitoring

​
📊 Trigger Hook vs Webhooks Comparison

FeatureWebhooksTrigger Hooks
PurposeSend data to external systemsExecute internal actions
DirectionOutbound HTTP requestsInternal processing
ResponseDepends on external endpointImmediate internal execution
ActionsLimited to HTTP callsMultiple action types available
LatencyNetwork dependentMinimal internal latency
ReliabilityExternal system dependentInternal system controlled
Use CasesCRM integration, notificationsAutomation, data processing, workflows

​
📋 Trigger Hook Management

Navigate to Setup > Trigger Hooks to manage your automation configurations. Trigger Hook Management

​
Trigger Hook Table Overview

ColumnDescriptionExample
#Sequential hook ID1, 2, 3
TitleHook name/identifierLead Qualification, Follow-up Scheduler
Updated AtLast modification timestamp09-09-2025 10:27 AM
Created AtHook creation timestamp09-09-2025 10:23 AM
ActionManagement optionsEdit, Delete, Duplicate, Test

​
Quick Actions

Add New Hook

Create new trigger hooks for your automation needs

Edit Configuration

Modify existing hook settings and conditions

​
🎛️ Trigger Hook Configuration

​
Creating a New Trigger Hook

1

Access Trigger Hooks

Navigate to Setup > Trigger Hooks and click “Add”
2

Basic Information

  • Title: Descriptive name for the trigger hook
  • Description: Optional detailed description of the hook’s purpose
  • Status: Enable/disable the hook
3

Trigger Configuration

  • Trigger When: Select the event type that activates the hook
  • Conditions: Set up conditional logic for when the hook should execute
  • Filters: Apply additional filters based on data attributes
4

Action Configuration

  • Hook URL: Internal or external endpoint to call
  • Hook Method: HTTP method (GET, POST, PUT, DELETE)
  • Type: Define the hook type and processing method
  • Role: Specify user role requirements for execution
5

Test and Activate

Test the trigger hook with sample data and activate for live events
Add Trigger Hook

​
Field Definitions

Title
  • Purpose: Human-readable identifier for the trigger hook
  • Format: Text string (max 255 characters)
  • Example: “Lead Qualification Hook”, “Follow-up Scheduler”
Description
  • Purpose: Detailed explanation of hook functionality
  • Format: Text area (optional)
  • Example: “Automatically qualifies leads based on call sentiment and duration”
Trigger When
  • Purpose: Defines the event that activates the hook
  • Options:
    • Power List Dial 1 Time - After first dial attempt
    • Power List Dial 2 Times - After second dial attempt
    • Power List Dial 3 Times - After third dial attempt
    • Call Ended - When any call completes
    • Call Answered - When call is answered
    • Agent Response - When AI agent responds
    • Lead Generated - When new lead is created
    • Appointment Scheduled - When appointment is booked
    • SMS Sent/Received - SMS events
    • Campaign Started/Ended - Campaign lifecycle events
Conditions
  • Purpose: Additional logic to filter when hook executes
  • Format: Conditional expressions
  • Examples:
    • call_duration > 60 (calls longer than 1 minute)
    • sentiment == "positive" (positive sentiment only)
    • lead_score >= 80 (high-quality leads only)
Hook URL
  • Purpose: Endpoint URL to send hook data
  • Format: Valid HTTP/HTTPS URL
  • Examples:
    • https://api.yourcrm.com/webhook/leads
    • https://app.hookk.com/webhook
    • https://internal.ai-sync.com/process-lead
Hook Method
  • Purpose: HTTP method for the hook request
  • Options: GET, POST, PUT, DELETE, PATCH
  • Default: POST
  • Usage: POST for creating data, PUT for updates, GET for queries
Type
  • Purpose: Categorizes the hook for processing and organization
  • Options:
    • Lead Processing - Lead qualification and routing
    • CRM Integration - Customer relationship management
    • Analytics - Data analysis and reporting
    • Notification - Alerts and notifications
    • Workflow - Business process automation
    • Other - Custom or miscellaneous hooks
Role
  • Purpose: Defines which user roles can trigger this hook
  • Options:
    • Agent - AI agents can trigger the hook
    • Admin - Administrator users only
    • Manager - Manager level and above
    • User - Any authenticated user
    • System - System-level automated triggers
  • Security: Ensures proper access control for sensitive operations

​
Edit Trigger Hook

Edit Trigger Hook When editing existing trigger hooks, you can modify all configuration parameters while maintaining execution history and performance metrics.

​
🎪 Available Trigger Events

Call Events

Triggers:
  • Call Started/Ended/Answered
  • Power List Dial Attempts
  • Call Transferred
Use Cases:
  • Real-time monitoring
  • Progressive lead nurturing
  • CRM updates
Data: Call status, duration, participant info, recordings

Agent Events

Triggers:
  • Agent Response Generated
  • Escalation Required
  • Performance Threshold
Use Cases:
  • Quality monitoring
  • Performance optimization
  • Training triggers
Data: Agent metrics, response content, conversation context

Lead Events

Triggers:
  • Lead Generated/Qualified
  • Status/Score Changed
Use Cases:
  • CRM synchronization
  • Lead routing
  • Sales notifications
Data: Demographics, qualification scores, interaction history

Campaign Events

Triggers:
  • Campaign Started/Completed
  • Milestone Reached
  • Performance Alert
Use Cases:
  • Performance monitoring
  • Budget management
  • Result processing
Data: Campaign metrics, progress, ROI statistics

Appointment Events

Triggers:
  • Scheduled/Confirmed/Cancelled
  • Rescheduled
Use Cases:
  • Calendar integration
  • Reminder automation
  • No-show prevention
Data: Appointment details, participant info, availability

Follow-up Events

Triggers:
  • Follow-up Due
  • Task Created
  • Deadline Approaching
Use Cases:
  • Task automation
  • Deadline management
  • Customer retention
Data: Task details, assigned members, due dates

​
📦 Hook Payload Structure

​
Standard Payload Format

All trigger hooks receive a consistent JSON payload structure: