Skip to main content

Overview

Integrate Make.com (formerly Integromat) scenarios with AgentFlow to automate complex business workflows. Connect 1000+ apps and services through conversational triggers.

Prerequisites

1

Make.com Account

Sign up at make.com - Free tier available
2

Create Scenario

Build and activate a scenario with webhook trigger
3

API Access

Get your webhook URL from Make.com
4

AgentFlow Admin Rights

Admin access to configure models

Step 1: Setup Make.com Scenario

Create New Scenario

  1. Log in to Make.com
  2. Click Create a new scenario
  3. Name it: AgentFlow Automation

Add Webhook Trigger

1

Add Webhooks Module

  • Click + to add first module
  • Search for Webhooks
  • Select Custom webhook
2

Create Webhook

  • Click Add to create new webhook
  • Name: AgentFlow Trigger
  • Click Save
3

Copy Webhook URL

Make will generate a URL like:
https://hook.eu1.make.com/abc123xyz789
Copy this URL for later use
4

Determine Data Structure

  • Click Determine data structure
  • Keep this tab open for testing

Build Automation Logic

Add modules to process the data:
1. Webhook Trigger (receives message)
2. Parse JSON (extract data)
3. Search Salesforce (find contact)
4. Update Contact (add note)
5. Send Email (notify sales rep)
6. Response (send confirmation)

Configure Response Module

1

Add Webhooks Response

  • After your logic, add WebhooksWebhook Response
  • Connect it to your final module
2

Format Response

Set response body:
{
  "data": {
    "scenario_result": "{{your.processed.data}}",
    "status": "success",
    "execution_id": "{{execution.id}}"
  }
}
3

Set Status Code

  • Status: 200
  • Headers: Content-Type: application/json

Activate Scenario

  1. Click Save (bottom left)
  2. Toggle ON to activate
  3. The webhook is now ready to receive requests

Step 2: Create AI Connection in AgentFlow

Manual Configuration

  1. Go to Admin DashboardAI Models
  2. Click Add Model
  3. Basic info:
    • Name: Make.com CRM Automation
    • Model ID: make-scenario-executor
    • Description: Automated CRM updates via Make.com
  4. API Configuration:
    • Endpoint: https://hook.eu1.make.com/abc123xyz789
    • Method: POST
  5. Headers (optional):
    {
      "make-api-key": "{{make_api_key}}",
      "Content-Type": "application/json",
      "User-Agent": "ChatPlatform/1.0"
    }
    
  6. Request schema:
    {
      "scenario_id": "{{scenario_id}}",
      "webhook_data": {
        "message": "{{message}}",
        "user_id": "{{user_id}}",
        "timestamp": "{{timestamp}}",
        "context": "{{context}}"
      },
      "execution_settings": {
        "mode": "webhook",
        "wait_for_completion": true,
        "timeout": 600
      }
    }
    
  7. Response path: data.scenario_result
  8. Click Save

Step 3: Import via YAML

YAML Configuration

Create make-workflow-config.yaml:
name: "Make.com Scenario Automation"
model_id: "make-scenario-executor"
description: "Execute Make.com scenarios via webhook triggers for automated workflow processing"
endpoint: "https://hook.eu1.make.com/{{scenario_id}}"
method: "POST"

headers:
  make-api-key: "{{make_api_key}}"
  Content-Type: "application/json"
  User-Agent: "ChatPlatform/1.0"

request_schema:
  scenario_id: "{{scenario_id}}"
  webhook_data:
    message: "{{message}}"
    user_id: "{{user_id}}"
    timestamp: "{{timestamp}}"
    context: "{{context}}"
  execution_settings:
    mode: "webhook"
    wait_for_completion: true
    timeout: 600
    retry_on_failure: true

response_path: "data.scenario_result"

message_format:
  preset: "custom"
  mapping:
    role:
      source: "role"
      target: "webhook_data.user_role"
      transform: "lowercase"
    content:
      source: "content"
      target: "webhook_data.message_content"
      transform: "none"
    timestamp:
      source: "timestamp"
      target: "webhook_data.timestamp"
      transform: "iso8601"
    context:
      source: "context"
      target: "webhook_data.additional_context"
      transform: "json_stringify"
  customFields:
    - name: "scenario_metadata"
      value:
        platform: "make.com"
        version: "2.0"
        execution_type: "webhook"
        region: "eu1"
      type: "object"
    - name: "error_handling"
      value:
        max_retries: 5
        retry_delay: 2000
        exponential_backoff: true
        fallback_action: "notify_admin"
      type: "object"

suggestion_prompts:
  - "Create a scenario to sync customer data between CRM and email marketing"
  - "Set up automated lead qualification and routing"
  - "Build a scenario for invoice generation and payment tracking"
  - "Create an automated social media posting workflow"
  - "Set up a scenario for order fulfillment and shipping notifications"

Import Steps

  1. Replace {{scenario_id}} with your webhook path
  2. Admin DashboardAI ModelsImport Model
  3. Upload YAML file
  4. Review configuration
  5. Click Import

Step 4: Assign to Group

  1. Admin DashboardGroups
  2. Select or create group (e.g., “Sales Team”)
  3. Manage Models → Enable Make.com Automation
  4. Set permissions:
    • Execution limit: 500/day
    • Priority: Medium
    • Access hours: 24/7
  5. Save Changes

Step 5: Use in Chat

Trigger Scenarios from Chat

  1. Chat InterfaceNew Conversation
  2. Select Make.com model
  3. Send message to trigger

Example Use Cases

Add new contact: John Doe, email: john@example.com, company: Acme Inc, status: lead

Advanced Scenarios

Multi-App Integration

1

Data Source

Google Sheets - Read customer data
2

Processing

OpenAI - Analyze and categorize
3

CRM Update

Salesforce - Create/update records
4

Notification

Slack - Alert team members
5

Storage

Airtable - Log execution

Conditional Routing

// Router module configuration
if ({{message.type}} === "urgent") {
  // Route to priority channel
  return "urgent_path";
} else if ({{message.value}} > 10000) {
  // Route to high-value workflow
  return "high_value_path";
} else {
  // Standard processing
  return "standard_path";
}

Error Handling

Add error handlers to your scenario:
  1. Click wrench icon on any module
  2. Select Add error handler
  3. Choose error handling method:
    • Ignore: Continue execution
    • Rollback: Undo changes
    • Retry: Attempt again
    • Commit: Finalize and stop

Regional Endpoints

Make.com has different webhook regions:
RegionEndpoint Format
EU (Europe)https://hook.eu1.make.com/...
EU2 (Europe)https://hook.eu2.make.com/...
US (United States)https://hook.us1.make.com/...
US2 (United States)https://hook.us2.make.com/...
Choose the region closest to your users for best performance.

Troubleshooting

Check:
  • Scenario is activated (toggle ON)
  • Webhook URL is correct
  • No module errors in scenario
  • Execution history shows attempts
Fix: Review scenario logs in Make.com
Cause: Scenario takes too longSolutions:
  • Increase timeout: timeout: 900
  • Use async execution
  • Optimize scenario (remove unnecessary modules)
  • Split into smaller scenarios
Check:
  • Data structure in webhook trigger
  • Mapping in subsequent modules
  • JSON format is valid
Fix: Use “Determine data structure” to debug
Cause: Exceeded monthly operationsFix:
  • Upgrade Make.com plan
  • Optimize scenario efficiency
  • Implement caching

Operations & Pricing

Understanding Operations

Each action in Make.com counts as an operation:
  • API calls
  • Data transformations
  • App connections

Pricing Tiers

PlanOperations/MonthPrice
Free1,000$0
Core10,000$9
Pro10,000$16
Teams10,000$29
EnterpriseCustomCustom
Optimize scenarios to reduce operations - use filters and routers strategically.

Best Practices

Scenario Design

Keep scenarios focused on single workflows

Error Handling

Always add error handlers to critical modules

Testing

Test with sample data before going live

Documentation

Document scenario purpose and data flow

Monitoring

Regularly check execution history

Optimization

Monitor and reduce operation usage

CRM Automation

  • Salesforce + Gmail + Slack
  • Auto-create contacts from emails
  • Notify team of new leads

E-commerce

  • Shopify + Stripe + SendGrid
  • Process orders
  • Generate invoices
  • Send confirmation emails

Marketing

  • Twitter + Buffer + Airtable
  • Schedule posts
  • Track engagement
  • Log analytics

HR & Operations

  • BambooHR + Google Workspace + Slack
  • Onboard new employees
  • Create accounts
  • Notify teams

Migration from Zapier

1

Export Zapier Workflows

Document current Zap triggers and actions
2

Rebuild in Make.com

Make.com offers more flexibility with:
  • Visual workflow builder
  • Advanced data transformation
  • Better error handling
  • Lower cost per operation
3

Update AgentFlow

Import new Make.com YAML configs
4

Test Thoroughly

Verify all workflows function correctly
5

Deactivate Zapier

Once confirmed, disable old Zaps

Next Steps

I