The Make.com integration (formerly Integromat) lets you connect Velaro to hundreds of apps using visual automation scenarios that trigger on Velaro events or call Velaro's REST API to take action.

What the Make.com Integration Does

Velaro sends webhook events to your Make scenario when conversations start, resolve, or when forms are submitted. Make can also call Velaro's REST API directly to create contacts, tag conversations, or send messages. This makes it possible to build multi-step automations with logic, filters, and branches — for example: new chat arrives → create a Monday.com item → notify a Slack channel → tag the Velaro conversation.

How to Connect via Webhook

The simplest way to receive Velaro events in Make is to configure a webhook:

1. In Make, create a new scenario and add a Webhooks → Custom Webhook module as the trigger.

2. Copy the webhook URL that Make provides.

3. In Velaro, go to Settings → Integrations → Make → Add Webhook.

4. Paste the Make webhook URL and select which events to send.

5. Save. Velaro will immediately start sending events to that URL.

You can add multiple webhooks — one per Make scenario — if you want different events routed to different automations.

Webhook Events

All events are sent as JSON via HTTP POST. Make parses the JSON body automatically when you use the Custom Webhook module.

How to Call Velaro's REST API from Make

To take action inside Velaro from a Make scenario, use the HTTP → Make a Request module:

1. Add an HTTP module to your Make scenario.

2. Set the URL to your Velaro API endpoint (e.g., https://velaro-admin-staging.azurewebsites.net/Contacts).

3. Set the method (GET, POST, PATCH).

4. In the Headers section, add: Authorization: Bearer YOUR_VELARO_API_KEY.

5. Set the request body as JSON for POST/PATCH requests.

Get your API key from Settings → API Keys → Create Key in Velaro.

Common Use Cases

New chat → Monday.com item → Slack notification

Trigger: conversation_started webhook → Create Item in Monday.com (visitor name, channel) → Send Slack message to #new-leads with the Monday item link.

Resolved conversation → Google Sheets row

Trigger: conversation_resolved webhook → Add Row to Google Sheets (agent name, duration, CSAT, tags). Builds a reporting dataset without any manual logging.

Form submitted → create Velaro contact + send to ActiveCampaign

Trigger: form_submitted webhook → HTTP POST to Velaro /Contacts API → HTTP POST to ActiveCampaign to add subscriber. Keeps both systems in sync from a single form submission.

Low CSAT → Escalation ticket

Trigger: conversation_resolved webhook → Filter: csat ≤ 2 → Create Jira issue → HTTP PATCH to Velaro to tag conversation as "escalation-needed".

Troubleshooting

Make scenario is not receiving events

Confirm the webhook URL in Velaro Settings → Integrations → Make matches the URL in your Make scenario. Test the connection by clicking Send Test Event in the Velaro webhook settings. If Make does not receive the test, check that the Make scenario is active (not paused).

Webhook payload is missing fields

The fields included in the payload depend on the event type and what data was collected in the conversation. If a visitor did not provide an email, visitorEmail will be null. Use Make's router or filters to handle missing fields gracefully.

API calls from Make return 401

Your Velaro API key may have expired or been deleted. Create a new key at Settings → API Keys and update the Authorization header in your Make HTTP module.

Webhook fires but Make returns an error

Check your Make scenario's execution history (Scenario → History) for the error detail. Common causes: JSON parsing error (check that Velaro's payload matches the expected structure) or a downstream module failed (check each module's output).