Skip to main content
Velor

Integrations

Plugs into your existing stack.

Velor offers ten pre-built integrations that install in the dashboard with your own API credentials: Shopify, Stripe, Zendesk, Gorgias, Intercom, Jira, ServiceNow, Slack, Microsoft Teams and Segment. Salesforce and HubSpot are available on request. For everything else, define a custom HMAC-signed action against your own API — the agent orchestrates it exactly like a first-class integration.

Live today

Ten pre-built connectors.

Each lands with an install flow in the dashboard, takes the API credentials you already hold, and exposes a named set of actions the agent can invoke mid-conversation. Credentials are envelope-encrypted with AES-256-GCM under a Velor-held key before being written to the database.

Shopify

Read customer and order data so your agent can resolve shipping questions and order status without a human lookup, and cancel or refund an order with a teammate's approval.

  • Order lookup by number, email, or customer ID
  • Shipment tracking and delivery status
  • Customer profile resolution for address and contact verification
  • Order cancellation and refunds, held for a teammate to approve

Stripe

Handle billing conversations that touch real accounts — subscription status, charge history, refunds — without handing card data back to the agent.

  • Subscription status, plan, and renewal date lookup
  • Customer charge history, including failed payments
  • Refunds guarded by an in-chat confirmation step — on voice and other channels they go to a teammate for approval instead. Upgrades and downgrades are not agent actions
  • Stripe-managed — card details never pass through Velor

Zendesk

Create and manage tickets without leaving the conversation, or hand escalations to your Zendesk queue with the conversation attached.

  • Ticket creation directly from the agent conversation
  • Ticket status lookup and update
  • Optional: each escalation opens a Zendesk ticket carrying the handoff brief and the transcript, redacted to your PII rules
  • Public replies on that ticket reach the customer on their own channel, once the Zendesk webhook is configured, and the customer's follow-ups are added to the ticket as internal notes

Gorgias

Hand escalations to your Gorgias queue with the conversation attached, and keep the thread in one place.

  • Each escalation opens a Gorgias ticket carrying the handoff brief and the transcript as an internal note, redacted to your PII rules
  • The customer's follow-ups are added to the ticket as internal notes
  • Public replies from your Gorgias team reach the customer on their own channel, once the Gorgias HTTP integration from the connector's install page is configured
  • Ticket status lookup for a verified customer's own tickets

Intercom

Look up Intercom contacts and their tags, and leave internal notes on a conversation. Escalation handoff to Intercom is not built.

  • Internal notes posted on an Intercom conversation
  • Contact lookup and profile retrieval
  • Read a contact's tags (tags are not written)

Jira

Turn an escalation into a tracked issue without leaving the conversation, and add comments to the issue from the same thread. Issue events Jira sends back are routed to your workflows; they are not relayed to the customer.

  • Issue search by JQL or free text before filing, so escalations do not duplicate an open ticket
  • Issue creation drafted from the conversation, into your default project key
  • Comments posted to all watchers, or restricted to internal visibility
  • Issue lookup by key returning status, assignee and the latest comments

ServiceNow

File and progress incidents on your ServiceNow instance from inside the conversation, with the work notes your process expects.

  • Incident search before filing, so a second report lands on the open incident
  • Incident creation with short description and detail drafted from the conversation
  • Work notes (internal by default) or customer-visible comments on an existing incident
  • Incident lookup by number returning the full record

Slack

Page the right channel the moment a conversation escalates, with the transcript and the customer attached — and pull channel context back in before escalating.

  • Structured handoff alert to your on-call CS channel on escalation
  • User lookup by email so the alert @-mentions the right teammate
  • Channel history read for context before escalating into a thread
  • Freeform channel messages where a structured alert does not fit

Microsoft Teams

Escalation and resolution cards the agent can post into the Teams channel your support team already lives in.

  • Escalation card with the conversation link and summary, available to the agent as a tool
  • Resolution summary card, available to the agent as a tool
  • Incoming-webhook setup — no Teams app approval to wait on

Segment

Conversation events sent into your existing analytics stack when the agent calls Segment as a tool during a conversation.

  • `track` calls the agent can make as a tool; the pipeline does not send lifecycle events on its own
  • `identify` calls the agent can make to attach traits once a visitor gives their email
  • Your own write key — events land in the sources and warehouses you already run

If you run a small shop, here is what works with your stack.

The plain version, tool by tool. The website chat widget, a knowledge base built from your own pages, and handoff to you by email work without any of these.

  • Shopify

    Partly

    Order lookup, tracking, cancel and refund through your own Shopify token. Lookups for a visitor need your site to sign that visitor in with Velor identity verification; without it the agent answers policy questions and hands order questions to you.

  • Gmail / Google Workspace

    Partly

    Sign in with Google, and email support by forwarding your support address to an intake address we set up with you. There is no Gmail plug-in: no drafts or labels in your inbox.

  • Intercom

    Partly

    Import your help-center articles and look up contacts. Handing a conversation off into Intercom is not built.

  • Help Scout

    Not supported

    No connector or import. Export a CSV for history and paste or upload your articles.

  • Freshdesk

    Not supported

    No connector yet (on the roadmap below). A CSV export works for history.

  • WhatsApp

    Partly

    Through your own Twilio WhatsApp sender, which you obtain and Meta approves. Not yet used in production, so plan on setup time.

On request

Two CRM connectors we switch on with you.

Both are built, and the agent invokes their actions through the same dispatcher the nine above use. The difference is the handshake: these connect through an OAuth app registered against your Salesforce org or HubSpot account rather than an API key you paste in, so we set the connection up with you during onboarding instead of leaving it self-serve. We set it up with you during onboarding.

Salesforce

Available on request. The connector is built and the agent can call it; the OAuth app is registered per environment, so we switch it on with you rather than leaving it self-serve. Until we have, the dashboard says so and shows how to ask; once it is on, you connect it yourself.

  • Contact lookup by email during a conversation
  • Activity logging as a completed Salesforce Task on the Contact
  • Connected App OAuth — your Salesforce org, your scopes

HubSpot

Available on request, on the same footing as Salesforce — built and agent-callable, switched on with you because the OAuth app is registered per environment. Until then the dashboard says so and shows how to ask; once it is on, you connect it yourself.

  • Contact lookup and full record retrieval by email
  • Notes logged on the HubSpot Contact for a complete activity history
  • Deal lookup and stage updates for the contact in conversation
Build your own

If it has an API, it's an integration.

Every pre-built connector is implemented on top of the same custom-actions system we expose to you. You write a JSON-schema action against your endpoint, Velor handles the orchestration — HMAC signing, SSRF protection, rate limiting, confirmation guardrails, retries — end-to-end.

Every pre-built connector is built on the same custom-actions system, so the same path reaches CRMs, order management systems, and internal APIs that are not on this page.

JSON
{
"name": "crm.customer_lookup",
"endpoint": "https://api.acme.com/velor/customer-lookup",
"method": "POST",
"destructive": false,
"parameters": {
"type": "object",
"required": ["email"],
"properties": {
"email": { "type": "string", "format": "email" }
}
},
"rate_limit": { "per_minute": 120 },
"timeout_ms": 2000
}
Roadmap

What's next on the connector roadmap.

Ranked by demand from the deals we're actively running. If yours isn't on here and you need it to be, mention it on your intro call — we prioritize against real contracts. If you build integrations for your own customers, we also work with agencies and technology partners.

  • Freshdesk

    Soon

    Ticket creation and intelligent routing for teams already running on Freshdesk.

  • Front

    Soon

    Shared-inbox escalation so the right teammate picks up where the agent left off.

  • Gmail

    Soon

    Shared-inbox native integration — draft creation, label routing, and status updates via the Gmail API.

  • Linear

    Soon

    Issue creation straight from support conversations so engineering context never gets lost in a Slack thread.

  • Notion

    Soon

    KB sync — keep your Notion knowledge base in lockstep with what the agent actually retrieves.

Don't see your stack? Ask.

If your system has an HTTP API, it can usually be reached with a custom action. If that's in scope for your build, we'll walk through it on the call.