Skip to Content
IntegrationsMake.com

Make.com Integration

Connect VelaFlows to Make.com  to build multi-step automation scenarios triggered by real-time VelaFlows events.

Overview

The integration uses Make.com’s Custom Webhook module to receive events from VelaFlows. When something happens in VelaFlows (new conversation, lead stage change, message received), a webhook fires and triggers your Make.com scenario.

Setup Guide

Step 1: Create a Custom Webhook in Make.com

  1. Log in to Make.com  and create a new scenario
  2. Add a Webhooks module as the trigger
  3. Select Custom webhook
  4. Click Add to create a new webhook
  5. Give it a name like “VelaFlows Events”
  6. Copy the webhook URL — you’ll need it in the next step

The URL looks like:

https://hook.make.com/abc123def456ghi789

Step 2: Create a Webhook Subscription in VelaFlows

Using the VelaFlows API, create a webhook subscription that sends events to your Make.com webhook URL:

curl -X POST "https://api.velaflows.com/api/v1/webhooks/subscriptions" \
  -H "Authorization: Bearer $VELAFLOWS_TOKEN" \
  -H "x-workspace-id: $VELAFLOWS_WORKSPACE" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hook.make.com/abc123def456ghi789",
    "events": [
      "conversation.created",
      "conversation.message.received"
    ],
    "secret": "my-make-webhook-secret"
  }'

You can also create the subscription in the VelaFlows dashboard:

  1. Go to Settings > Developer > Webhooks
  2. Click Create Subscription
  3. Paste the Make.com webhook URL
  4. Select the events you want to receive
  5. Click Create

Step 3: Configure Your Make.com Scenario

  1. Back in Make.com, click Run once to wait for a test event
  2. Trigger the event in VelaFlows (e.g., send yourself a message)
  3. Make.com will receive the webhook and show you the data structure
  4. Add your action modules (Slack, Gmail, Google Sheets, etc.)
  5. Map the VelaFlows fields to your action inputs
  6. Turn on the scenario

Step 4: Test the Integration

  1. Trigger a real event in VelaFlows
  2. Check the Make.com scenario history to confirm it ran
  3. Verify the action was performed (Slack message sent, sheet updated, etc.)

Webhook Payload Format

Make.com receives a JSON payload like this:

{
  "event": "conversation.message.received",
  "timestamp": "2026-03-24T10:30:00.000Z",
  "workspaceId": "64f1a2b3c4d5e6f7a8b9c0d1",
  "data": {
    "conversationId": "65a1b2c3d4e5f6a7b8c9d0e1",
    "channelType": "whatsapp",
    "message": {
      "_id": "65a1b2c3d4e5f6a7b8c9d0e3",
      "content": "Hi, I need help with my order",
      "type": "text",
      "direction": "incoming",
      "createdAt": "2026-03-24T10:30:00.000Z"
    },
    "contact": {
      "name": "John Doe",
      "phone": "+1234567890"
    }
  }
}

In Make.com, you can access fields like:

  • data.message.content — the message text
  • data.contact.name — the customer’s name
  • data.channelType — which channel (whatsapp, telegram, etc.)

Example: New Conversation to Slack

Build a scenario that sends a Slack notification when a new conversation starts:

Scenario Setup

  1. Trigger: Webhooks > Custom webhook (VelaFlows)
  2. Filter: Only if data.channelType equals whatsapp
  3. Action: Slack > Send a Message

Slack Message Template

New WhatsApp conversation from {{data.contact.name}}

Channel: {{data.channelType}}
Message: {{data.message.content}}
Time: {{timestamp}}

View in VelaFlows: https://app.velaflows.com/dashboard/inbox

Tips

  • Use filters in Make.com to only process specific event types or channels
  • Add error handlers to gracefully handle failures (retry, ignore, alert)
  • Use routers to send different events to different action paths
  • Rate limits: Make.com has its own operation limits — check your plan
  • Webhook verification: VelaFlows signs webhook payloads with your secret for security. Make.com processes these automatically.
OverviewZapier