Before you start

An account in the tool you use, with a step that can send a web request (some tools offer it only on paid plans).
A VelBEE workspace and the settings permission.
The person’s details available as fields in your tool, at least a phone number or an email.

Note

There are no ready-made VelBEE apps in the Zapier or Make directories yet. You use their generic webhook or HTTP action instead. Some tools offer that action only on paid plans, so check yours.

The four steps

Your tool sends the fields. VelBEE saves one lead.

Add a source in VelBEE
Open Connect, press Add a source and choose Zapier, Make, n8n or a form tool. Copy the address and the key (shown once).
Add a “send a web request” step
In your tool add a step that sends a request: in Zapier a webhook POST action, in Make an HTTP request, in n8n an HTTP Request node. Use method POST and the address you copied.
Add the header Authorization with the value Bearer followed by a space and your key. If your tool cannot set that header, use X-Velbee-Token with the key as the value.

Send the person’s details as JSON

Map the fields from your trigger. Common names are recognised automatically.

Example body

{
  "name": "Ravi Kumar",
  "phone": "+91 98765 43210",
  "email": "ravi@example.com",
  "message": "Interested in a 3 BHK",
  "utm_campaign": "diwali"
}

Test it
Run the step once. Then open the source in VelBEE and check its Activity tab: you should see “Lead created”. If your tool uses unusual field names, map them under the source’s Settings.

Test from a terminal first

curlbash

curl -X POST https://api.velbee.com/v1/ingest/YOUR-SOURCE \
  -H "Authorization: Bearer YOUR-KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Test Person","phone":"+91 98765 43210"}'

A 201 answer means the lead was saved. Other answers are explained in the API reference.

What you will have at the end

A source in Connect of the type Zapier, Make, n8n or a form tool, with its address and key.
A step in your tool that sends each new enquiry to that address.
Leads that arrive with the source you named, and a line on the Activity tab for every request.

Troubleshooting

What you see	Likely cause	What to do
`401` Not authorised	The key is wrong, was renewed, or the header is missing.	Check the header is `Authorization: Bearer YOUR-KEY` (one space after Bearer). If your tool cannot set it, use `X-Velbee-Token`.
`404` Unknown source	The address was copied incompletely.	Copy the address again from the source in Connect.
`403` This form is switched off	The source is paused.	Resume it on its page.
`422` Please give a phone number or an email address	The body has neither, or the field names are not recognised.	Map a field named `phone` or `email`. Unusual names can be mapped in the source’s Settings.
`429` Too many requests	More than about 300 requests a minute for one source.	Slow the sending or batch it, then try again.
The lead has the details in its note	Fields VelBEE does not recognise are kept in the note.	Rename the field, or map it in the source’s Settings. Nothing is lost.

Questions

Is there a ready-made VelBEE app for Zapier or Make?

Not yet. You use their generic webhook or HTTP step, as described above.

What if the same person is sent twice?

A person who already has an open lead gets the new enquiry added to it. The answer says duplicate: true.

Can I read leads back out?

Not through the API yet. To be told when something changes in VelBEE, use webhooks.

Connect any tool that can send a webhook.

Before you start

The four steps

Add a source in VelBEE

Add a “send a web request” step

Send the person’s details as JSON

Test it