Skip to main content

​
Webhook Integration with Famulor Automation

Mid-call actions can not only execute direct API calls but can also be connected via webhooks to the Famulor Automation Platform. This enables complex, multi-step workflows and the use of all available integrations on the no-code platform.

​
Overview of the Webhook Integration

Direct API vs. Webhook

Direct API Call: Simple 1:1 data query or transmissionWebhook Integration: Complex workflows involving multiple systems, data processing, and business logic

Advanced Capabilities

  • Multi-system integrations within one workflow
  • Conditional logic and decision trees
  • Data preparation and transformation
  • Time-delayed actions and follow-ups

​
How It Works

​
Configuring the Webhook Tool

​
1. Basic Configuration

ParameterValue
Function nametrigger_famulor_automation
Description”Starts a Famulor Automation workflow using call data as input. Use this for complex multi-system operations.”
HTTP MethodPOST
URLhttps://app.famulor.de/api/webhook/automation/{flow_id}
Timeout15000ms

​
2. Request Body Template

{
  "trigger_source": "mid_call_tool",
  "conversation_context": {
    "customer_email": "{email}",
    "customer_phone": "{phone}",
    "customer_name": "{full_name}",
    "company_name": "{company}",
    "conversation_summary": "{summary}",
    "detected_intent": "{intent}",
    "urgency_level": "{urgency}",
    "timestamp": "{current_timestamp}"
  },
  "workflow_parameters": {
    "lead_source": "phone_call",
    "follow_up_required": true,
    "priority": "{calculated_priority}",
    "assigned_team": "{team_assignment}"
  },
  "custom_data": {
    "budget_mentioned": "{budget_info}",
    "timeline_mentioned": "{timeline}",
    "pain_points": "{pain_points}",
    "competitor_mentioned": "{competitors}"
  }
}

​
3. Parameter Schema

{
  "type": "object",
  "properties": {
    "flow_id": {
      "type": "string",
      "description": "ID of the Famulor Automation workflow to execute"
    },
    "email": {
      "type": "string",
      "format": "email",
      "description": "Customer's email address"
    },
    "phone": {
      "type": "string",
      "description": "Customer's phone number"
    },
    "full_name": {
      "type": "string",
      "description": "Customer's full name"
    },
    "company": {
      "type": "string",
      "description": "Customer's company name"
    },
    "summary": {
      "type": "string",
      "description": "Summary of key conversation points"
    },
    "intent": {
      "type": "string",
      "enum": ["support", "sales", "information", "complaint", "partnership"],
      "description": "Detected conversation intent"
    },
    "urgency": {
      "type": "string",
      "enum": ["low", "medium", "high", "critical"],
      "description": "Urgency level based on conversation content"
    },
    "calculated_priority": {
      "type": "string",
      "enum": ["low", "medium", "high"],
      "description": "Calculated priority for follow-up actions"
    },
    "team_assignment": {
      "type": "string",
      "enum": ["sales", "support", "success", "technical"],
      "description": "Recommended team for follow-up"
    },
    "budget_info": {
      "type": "string",
      "description": "Mentioned budget information"
    },
    "timeline": {
      "type": "string",
      "description": "Mentioned timeframe or deadline"
    },
    "pain_points": {
      "type": "array",
      "items": {"type": "string"},
      "description": "Array of identified pain points"
    },
    "competitors": {
      "type": "array",
      "items": {"type": "string"},
      "description": "Mentioned competitors or alternative solutions"
    }
  },
  "required": ["flow_id", "email", "summary", "intent"]
}

​
Practical Examples of Webhook Workflows

​
1. Lead Qualification & Routing

Workflow Name: "Smart Lead Processing"
Trigger: Webhook from Mid-call Action

Steps:
  1. Duplicate check in HubSpot
  2. If new → create lead
  3. If known → retrieve contact history
  4. Lead scoring based on:
     - Company size (Clearbit/LinkedIn)
     - Budget info from conversation
     - Urgency level
     - Previous interactions
  5. Team assignment based on score:
     - >80: Enterprise Sales Team
     - 50-80: Standard Sales Team  
     - <50: Inside Sales/Nurturing
  6. Start follow-up sequence:
     - Confirmation email to customer
     - Slack notification to team
     - Task creation in CRM
     - Calendar invite for follow-up call

Workflow_Conditions:
  If urgency == "critical":
    → Immediate SMS to sales manager
    → Set priority flag in CRM
    → Schedule meeting within 4 hours
  
  If competitor_mentioned:
    → Trigger competitive intelligence tool
    → Send battle card to sales rep
    → Alert pricing strategy team
  
  If budget > 100k:
    → Assign to enterprise team
    → Set C-level executive as contact owner
    → Provide custom demo environment

​
2. Customer Success Automation

Trigger: intent == "support"

Workflow Steps:
  1. Create HubSpot ticket
  2. Search similar tickets (knowledge base)
  3. If FAQ solution exists:
     → Automated response email
     → Mark ticket as "self-service"
  4. If complex:
     → Assign technical team
     → Start SLA timer
     → Notify customer about response time
  5. Integrations with:
     → Jira (for bug tracking)
     → Confluence (knowledge base updates)
     → Slack (team communication)

​
3. Sales Opportunity Management

​
Advanced Webhook Configurations

​
Multi-Workflow Orchestration

Main Workflow: "Customer Intake Processing"

Parallel Executed Sub-Workflows:
  1. CRM Processing:
     - Lead/contact creation
     - Deal management
     - Activity logging
  
  2. Communication Automation:
     - Email sequences
     - SMS notifications
     - Slack updates
  
  3. Data Enrichment:
     - Company information (Clearbit)
     - Social media profiles
     - Technographic data
  
  4. Compliance Processing:
     - GDPR consent management
     - Data retention policies  
     - Audit trail creation

Workflow: "High-Value Lead Processing"

Sequence:
  1. Initial Processing:
     - Create lead
     - Basic enrichment
     - Calculate score
  
  2. Approval Gate:
     If lead score > 90:
       → Manager approval required
       → Hold until approval
     Else:
       → Direct processing
  
  3. Post Approval:
     - Assign enterprise team
     - Initiate premium onboarding
     - Define executive sponsor
  
  4. Follow-up:
     - 24h check-in
     - Weekly status updates
     - Plan quarterly business reviews

​
Error Handling & Retry Logic

Retry Configuration:
  Max retries: 3
  Backoff strategy: exponential
  Initial delay: 2s
  Max delay: 30s
  
Retry Conditions:
  - HTTP 429 (rate limiting)
  - HTTP 502/503 (service unavailable)
  - Timeout errors
  - Network connection issues

Fallback on final failure:
  - Error notification to admin
  - Fallback to simple direct API call
  - Manual processing queue

​
Response Processing

​
Webhook Response Format

{
  "workflow_id": "wf_12345",
  "execution_id": "exec_67890", 
  "status": "completed",
  "execution_time_ms": 3450,
  "results": {
    "lead_created": {
      "hubspot_contact_id": "12345",
      "lead_score": 85,
      "assigned_owner": "sales@example.com"
    },
    "notifications_sent": {
      "email_confirmation": "sent",
      "slack_notification": "sent",
      "sms_alert": "skipped"
    },
    "follow_up_scheduled": {
      "task_id": "task_98765",
      "due_date": "2024-01-16T10:00:00Z",
      "assigned_to": "max.sales@example.com"
    }
  },
  "errors": [],
  "warnings": [
    "SMS service temporarily unavailable"
  ]
}

​
AI Integration of Webhook Results

Natural_Language_Processing:
  Success_Response:
    "Perfect! I have processed your request and scheduled a follow-up 
     for tomorrow at 10 am. My colleague Max will get in touch with you."
  
  Partial_Success:
    "Everything is set up. There was a minor technical note regarding the SMS service, 
     but you have received the email confirmation."
  
  Warning_Handling:
    "Your request was processed successfully. If you do not receive confirmation 
     within the next hour, please feel free to contact us."

​
Performance & Monitoring

​
Webhook Performance Metrics

MetricTarget ValueCritical Value
Execution Time< 5 seconds> 15 seconds
Success Rate> 95%< 85%
Retry Rate< 10%> 25%
Partial Success Rate> 98%< 90%

​
Monitoring & Alerting

1

Real-time Monitoring

Dashboard Metrics:
  - Webhook success rate
  - Average execution time
  - Error rate by workflow type
  - Queue size under high load
2

Alerting Rules

Critical Alerts:
  - Success rate < 90% over 5 minutes
  - Execution time > 10s for > 10 requests
  - Error rate > 20% over 2 minutes

Warning Alerts:
  - Queue size > 50 pending
  - Retry rate > 15%
  - Individual workflow failures

​
Best Practices

​
Workflow Design

Ensure Idempotency

  • Workflows can be executed multiple times
  • Implement duplicate checks
  • State management for retry scenarios
  • Use transactional operations

Performance Optimization

  • Identify steps that can be executed in parallel
  • Set appropriate timeout values
  • Avoid unnecessary API calls
  • Use caching for frequent queries

​
Security Considerations

Authentication:
  - Bearer token for Famulor API
  - Webhook signature verification
  - IP whitelisting for webhook endpoints
  - Rate limiting for webhook calls

Data Protection:
  - Avoid sensitive data in URL parameters
  - Use HTTPS for all webhook calls
  - Payload encryption if needed
  - Automatic PII redaction in logs

Audit Trail:
  - Log all webhook executions
  - Data processing evidence
  - User consent tracking
  - Retention policy compliance

GDPR Considerations:
  - Support right to deletion
  - Follow data minimization principles
  - Observe purpose limitation
  - Control cross-border data transfers

Integration Examples

Discover practical webhook workflow examples:
Tip: Start with simple webhook workflows and expand gradually. The Famulor Automation Platform offers comprehensive debugging tools to track and optimize workflow executions.
Important Notice: Webhook workflows can automate complex business processes. Thoroughly test all workflows in a staging environment before deploying them in production.