Under the hood

It proposes the contract, you correct it

From the URL and your one-line goal, Vela drafts the inputs and outputs the connector should have. You fix the wording, add a field, drop one you do not need — before a single request is made.

It stops when only you can decide

Which of the three “Confirm” buttons is the real one. Whether a client should be created or matched. These are checkpoints, not chat: a short question, your answer, and it carries on.

It never asks twice

A decision you have made is remembered for the rest of the build and reused during repairs, so a connector that gets fixed six weeks later does not come back asking you to re-explain your own booking flow.

You watch it happen

The browser is streamed live while it works. If it takes a wrong turn you see it at the moment it happens rather than in a log afterwards.

The session expired

The most common failure, and the least interesting. Vela re-logs in with the stored credentials and retries once, silently. You are not notified, because nothing happened that you could act on.

The target genuinely changed

A field moved, an endpoint was renamed, a response shape shifted. Vela replays the evidence captured during the build against the new behaviour, repairs the connector, and tells you what changed. If the repair cannot be verified, the connector is marked degraded rather than quietly returning wrong data.

The caller sent something wrong

A malformed date, a staff id that does not exist. This returns an input error. Vela will not substitute a plausible value to make the call succeed — a booking placed on a guessed date is worse than a failed call, and much harder to notice.

Credentials

Encrypted at rest with AES-256-GCM. Decrypted only inside the execution sandbox, only for the connector they belong to. Never sent to the model, never written to logs. Deleting them from the connector page is immediate — the connector then asks for a fresh login the next time it needs a session.

The generated script

Runs in a separate process with filesystem access limited to its own temporary directory, an allow-listed environment, and no ability to reach private or link-local addresses. It is dry-run validated in that sandbox before it is ever deployed.

Your data

The traffic captured during a build exists to reconstruct and repair the connector. You can delete a connector, its evidence and its sessions in one click, and nothing survives it.

AI voice & chat agents

An agent that answers the phone has to actually book.

A voice agent that can only read availability hands the call back to a human at the moment that matters. Vela gives the agent a write tool with an idempotency key, so a retry on a dropped call cannot create a second appointment. Export straight to Vapi, Retell, Voiceflow, or as an OpenAI/Claude tool schema.

No-code automation

Stop telling clients their software cannot be automated.

n8n, Make and Zapier all assume the target has an API. When it does not, the scenario stops at a manual step. A Vela connector is an HTTP node like any other — the export arrives pre-filled, with the auth header and the body schema already in place.

Agencies

Sell the integration, not the maintenance.

The reason custom integrations are unprofitable is not building them, it is the Tuesday morning when the vendor ships a redesign. Vela health-checks every connector daily and repairs against the evidence captured at build time. Unlimited client workspaces and API keys are included at every size.