n8n is a workflow automation tool you can use in the cloud or run yourself. Velaro has its own n8n community node with a Velaro action node and a Velaro Trigger node. You can also use n8n's HTTP Request node to call any endpoint in the REST API Guide.

Install the Velaro Node

In n8n open Settings → Community Nodes → Install and enter n8n-nodes-velaro. Self-hosted n8n installs community nodes from the same screen.

Create Your Credentials

In Velaro go to Settings → API Keys → Create API key, name it for n8n, and choose the scopes you need. The examples here use read:contacts and write:contacts. Copy the key (it starts with vlk_) because it is shown only once. Create one key per tool so you can rotate it independently.

In n8n add a Velaro API credential, paste the key and keep the default base URL. n8n tests the credential for you. Never put the key in a URL.

The Velaro Action Node

Use the Velaro node to find, create or update a contact by email, add a tag, add a note, list conversations, appointments, agents and teams, and fetch a single contact or conversation. Each list call returns one page of up to 100 results.

Adding a tag creates it if it does not exist, and any Email Campaign set to start on "Contact tag added" begins for that contact.

The Velaro Trigger Node

The Velaro Trigger node starts a workflow when Velaro sends an event, such as contact tag added, conversation started or conversation closed. It registers the webhook when you activate the workflow and removes it when you deactivate.

Every delivery is signed. The trigger node verifies the signature for you. If you receive webhooks in your own code, verify the HMAC-SHA256 signature of the raw request body with your signing secret before trusting the payload.

Use the HTTP Request Node Instead

Add an HTTP Request node, set Authentication to Generic Credential Type, then Header Auth, with Name Authorization and Value Bearer vlk_your_key. Send JSON to https://api-admin-us-east.velaro.com/api/v1/contacts to create or update a contact. To receive events without the trigger node, add an n8n Webhook node, copy its Production URL, and subscribe it with POST /webhooks (scope write:webhooks).

Limits and Cost

n8n uses the same API-call allowance as Make, Zapier and Power Automate. There is no separate connection fee. See the Plan Limits section of the REST API Guide for how limits work and where to see yours.

Troubleshooting

401 Unauthorized: check the credential holds the full key, and for Header Auth that the value starts with Bearer .

Trigger does not fire: the workflow must be active. Test URLs only work while n8n is listening.

Contact not tagged: confirm the key has the write:contacts scope.

Ask Moshky

Ask Moshky to review which API keys and webhooks your account has, then use a key limited to the scopes the workflow needs.