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 and tag contacts. 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 contact in Velaro.

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. Create an API key at Settings → API Keys with the read:contacts and write:contacts scopes.

2. Add an HTTP module to your Make scenario.

3. URL: https://api-admin-us-east.velaro.com/api/v1/contacts (production).

4. Method: POST. Headers: Authorization: Bearer vlk_your_key and Content-Type: application/json.

5. Body type: Raw, content type JSON.

Create or update a contact

POST /api/v1/contacts creates the contact, or updates it if the email already exists. Include tags to tag it in the same call.

{ "email": "jane@example.com", "firstName": "Jane", "lastName": "Doe", "company": "Acme", "tags": ["make-lead"] }

Response: { "id": 123, "created": true, "email": "jane@example.com", "tags": ["make-lead"] }

Update one field on an existing contact

PATCH /api/v1/contacts/{id} with only the fields to change, for example { "jobTitle": "Director" }. Fields you leave out stay as they are. Needs the Write contacts permission.

Tag a contact (and the conversation's visitor)

POST /api/v1/contacts/tag with { "email": "jane@example.com", "tag": "escalation-needed" } (or contactId instead of email). The tag is created if it is new. Tagging fires the Contact tag added trigger for Email Campaigns. To tag the visitor of a conversation, use the visitor email from the webhook payload.

Look up contacts

GET /api/v1/contacts?email=jane@example.com or GET /api/v1/contacts?search=acme. Use GET /api/v1/me to check that a key works and see its scopes.

The same requests work in Zapier (Webhooks by Zapier → Custom Request) and Power Automate (HTTP action).

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 /api/v1/contacts → 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 POST to Velaro /api/v1/contacts/tag with the visitor email and tag "escalation-needed".

Payload Fields for AI Calls

When the AI calls your Make scenario during a conversation, it sends a data object. Under Settings → Integrations → Make → Payload Fields, you can declare the exact fields your scenario expects.

• Declared fields become the required keys of the call. The AI is told the exact keys to send and fills each one from the conversation.
• If the AI sends a key that is not declared, the call is returned to it with the list of valid keys, so it can retry with the right ones.
• Leave the list empty to let the AI choose its own keys.
• Moshky can show and update this list for you. Ask it to show or change your Make Payload Fields, and it will preview the change and wait for your approval before saving.

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).

Limits and Cost

Calls from this tool use the same API-call allowance as every other automation tool, with no separate connection fee. See the Plan Limits section of the REST API Guide for how limits work and where to see yours.