Skip to main content

Automation Workflows

Connect EolasFlow to your existing tools and build powerful automations using no-code platforms like n8n, Zapier, or Make. Create custom workflows that trigger actions when calls complete, sync data with your CRM, or build your own MCP tools.

Why Automate?

No Code Required

Build integrations visually without writing code

Connect Everything

Link EolasFlow to 500+ apps and services

Real-Time Actions

Trigger workflows instantly when calls complete
PlatformBest ForPricing
n8nSelf-hosted, full control, complex workflowsFree (self-hosted)
ZapierSimple automations, 5000+ app integrationsFree tier available
MakeVisual workflows, advanced logicFree tier available

Using Webhooks with n8n

n8n is a powerful open-source automation tool. Here’s how to connect it to EolasFlow.

Step 1: Create a Webhook in n8n

1

Open n8n

Access your n8n instance (self-hosted or cloud).
2

Create New Workflow

Click New Workflow and give it a name like “EolasFlow Call Handler”.
3

Add Webhook Trigger

Add a Webhook node as the trigger. Select POST method.
4

Copy Webhook URL

n8n generates a unique URL like:
https://your-n8n.com/webhook/abc123
5

Test the Webhook

Click Listen for Test Event to activate.

Step 2: Register in EolasFlow

1

Go to Integrations

Navigate to Dashboard → Integrations → Webhooks.
2

Add Endpoint

Click Add Endpoint and enter:
  • Name: n8n Call Handler
  • URL: Your n8n webhook URL
  • Auth: None (or add if your n8n requires it)
3

Test Connection

Click Test to verify n8n receives the request.
4

Enable on Campaign

Go to your campaign, enable webhooks, and select this endpoint.

Step 3: Build Your Workflow

Now in n8n, add nodes to process the webhook data:
Webhook → Parse Data → Your Actions
Example: Send to Slack when call completes
  1. Add IF node: Check if event === "call.completed"
  2. Add Slack node: Send message with call summary
  3. Connect: Webhook → IF → Slack
Example: Update CRM after call
  1. Add HTTP Request node to call your CRM API
  2. Map fields: customer name, phone, call outcome
  3. Connect: Webhook → HTTP Request

Using Webhooks with Zapier

Create a Zap

1

Create New Zap

In Zapier, click Create Zap.
2

Choose Trigger

Select Webhooks by ZapierCatch Hook.
3

Copy Webhook URL

Zapier provides a unique URL for your Zap.
4

Register in EolasFlow

Add this URL as a webhook endpoint in EolasFlow.
5

Test

Trigger a test call, then continue in Zapier to map fields.
6

Add Actions

Add actions like “Create Google Sheet Row” or “Send Email”.
ActionUse Case
Google SheetsLog all calls to a spreadsheet
GmailSend follow-up emails after calls
SlackNotify team of important calls
HubSpotUpdate CRM contacts
CalendlySchedule follow-up meetings

Using Webhooks with Make

1

Create Scenario

In Make, create a new scenario.
2

Add Webhook Module

Add WebhooksCustom Webhook as trigger.
3

Copy URL

Copy the generated webhook URL.
4

Register in EolasFlow

Add as webhook endpoint and test.
5

Build Flow

Add modules to process call data.

Building Custom MCP Servers

Want your AI agents to access external data during calls? Build an MCP server using n8n or your own code.

MCP with n8n

You can create a simple MCP-compatible endpoint in n8n:
1

Create Webhook Endpoint

Add a Webhook node that accepts POST requests.
2

Handle tools/list

Add logic to return available tools when method === "tools/list".
3

Handle tools/call

Add logic to execute tools when method === "tools/call".
4

Return JSON-RPC Response

Format responses as JSON-RPC 2.0.
Example tools/list response:
{
  "jsonrpc": "2.0",
  "result": {
    "tools": [
      {
        "name": "lookup_customer",
        "description": "Look up customer by phone number",
        "inputSchema": {
          "type": "object",
          "properties": {
            "phone": { "type": "string" }
          },
          "required": ["phone"]
        }
      }
    ]
  },
  "id": 1
}

MCP Server Requirements

Your MCP server must:
  • Accept POST requests with JSON-RPC 2.0 format
  • Handle tools/list to return available tools
  • Handle tools/call to execute tools
  • Respond within the timeout (default 5 seconds)
For production MCP servers, consider building a dedicated service rather than using n8n for better performance.

Workflow Ideas

Post-Call CRM Update

EolasFlow Webhook (call.completed)

Parse transcript & outcome

Update CRM contact

Create follow-up task

Lead Qualification Alert

EolasFlow Webhook (call.completed)

Check if outcome = "interested"

Send Slack notification to sales team

Create calendar event for follow-up

Call Analytics Dashboard

EolasFlow Webhook (all events)

Log to Google Sheets

Update metrics dashboard

AI-Powered Follow-Up

EolasFlow Webhook (call.completed)

Send transcript to ChatGPT

Generate personalized follow-up email

Send via Gmail

Webhook Payload Reference

When EolasFlow sends a webhook, you receive:
{
  "event": "call.completed",
  "call_id": "CA1234567890",
  "campaign_id": "uuid",
  "timestamp": "2024-01-15T14:30:00Z",
  "customer": {
    "name": "John Smith",
    "phone": "+15551234567",
    "email": "[email protected]"
  },
  "call_data": {
    "duration_seconds": 180,
    "status": "completed",
    "outcome": "interested",
    "recording_url": "https://...",
    "transcript": "Agent: Hello...",
    "summary": "Customer interested in demo"
  }
}
Use these fields in your automation workflows.

Best Practices

Start Simple: Build a basic workflow first, then add complexity.
Test Thoroughly: Use test calls before connecting to production systems.
Handle Errors: Add error handling nodes in case external APIs fail.
Monitor Performance: Keep MCP tool responses under 5 seconds.
Secure Endpoints: Use authentication for production webhook endpoints.

Resources

Next Steps