Skip to main content
Velor

Platform · Actions

Your APIs. Called by the agent. Signed by default.

Define a webhook endpoint, describe what it does, and give it a JSON schema. Velor calls it with a signed request when the agent decides to act — with confirmation before anything irreversible happens.

How it works.

  1. 01

    Define

    Create an action in the dashboard: name, description, your webhook URL, and a JSON schema for the input parameters.

  2. 02

    Decide

    The agent reads the conversation, decides an action is appropriate, validates the required params, and (for destructive actions) presents a confirmation to the customer before proceeding.

  3. 03

    Call

    Velor sends a signed POST to your webhook with HMAC-SHA256 (Velor-Signature-256 + Velor-Timestamp headers). Your server validates the signature and executes the action.

  4. 04

    Return

    Your webhook returns a structured response. The agent incorporates the result into its reply — order status, confirmation numbers, updated state.

How it stays safe.

HMAC-SHA256 signed requests

Every webhook call includes Velor-Signature-256 (v1=hex) and Velor-Timestamp headers. Your server can verify the signature and reject replays older than 5 minutes — the same pattern as Stripe webhooks.

SSRF protection

Velor blocks webhook calls to private IP ranges, localhost, and internal cloud metadata endpoints. Your action URLs must resolve to public internet addresses.

Destructive-action confirmation

Mark any action as destructive:true and the agent will show the customer what's about to happen — and require explicit confirmation — before the webhook fires.

Schema-validated inputs

Define the JSON schema for each action's parameters. Velor validates the agent's proposed inputs against the schema before calling your webhook — no malformed requests reach your server.

The webhook contract.

POST https://api.yourcompany.com/velor/actions

Velor-Signature-256: v1=abc123...

Velor-Timestamp: 2024-04-18T20:00:00Z

Content-Type: application/json

{

"action": "order.lookup",

"params": { "order_id": "41208" },

"customer_id": "cus_xyz"

}

Your endpoint receives the signed body and must respond within the action’s own timeout_ms— 5 seconds unless you raise it, and 30 seconds at most. In web chat it is also shortened to fit the reply: a call never runs into the last 8 seconds of the 30-second reply window, which are kept for the answer. Return a JSON object; the agent reads it and incorporates the result.

Run it on your own tickets.

Every workspace starts with a 14-day free trial. No credit card. If you want a guided walkthrough against your data, we're happy to run one with you.