Data connectors

Data connectors overview

Open the dashboard Service status Get support

Connect your own shop, CRM, licence server or any HTTP API and show its data to your team on the ticket — no code.

Clarify's integrations cover the big payment platforms — Stripe, PayPal, Tebex, Patreon. But your business runs on more than that: your own shop, a CRM, a licence server, an internal API. Data connectors let you plug any of those into Clarify and show their data to your team, right on the ticket — without writing a single line of code.

You describe where your system lives and what to send it. Clarify makes the request, reads the response, and drops the fields you care about onto a card the moment a ticket opens.

Data connectors are for your own systems. For the payment platforms, use a ready-made integration instead — it's less setup and handles the connection for you.

How a connector works

Every connector follows the same simple pipeline:

An input

A ticket field the member fills in — a licence key, an order number, an email — or a value Clarify reads automatically from Discord.

A request

Clarify sends that value to your system's API, exactly as you've described it.

A response

Your system replies with data — a customer record, an order, a subscription status.

A card

Clarify maps the fields from that response onto your placeholders and shows the result as a card on the ticket.

The card is built the same way as every other result card in Clarify: you pick which field from the response fills each %placeholder% token. See Cards and placeholders for how that works.

The killer feature: Discord auto-detect

Most lookups need the member to type something in first. Discord auto-detect doesn't.

When a connector is set to auto-detect, Clarify takes the member's own Discord ID the moment the ticket opens, sends it to your system, and shows the result — with zero input from anyone. If your system knows a customer by their Discord ID, your team sees who they are before the first reply.

Auto-detect is the fastest way to give staff full context on every ticket. Learn how to set it up in Discord auto-detect.

What connectors can do today

In this version, connectors are read-only lookups. They fetch data from your system and display it — they don't create, change or delete anything on your side. That keeps them safe to add to any ticket.

A lookup is the perfect fit for the questions your team asks all day: Is this person a real customer? What did they buy? Is their licence still valid? When does their plan renew? The answer appears on the ticket automatically, so nobody has to leave Discord to go and check.

Is it safe?

Yes. Connectors are built to be safe to point at your own infrastructure, and any keys or tokens you provide are encrypted and never shown back to you. Requests are locked to the endpoint you configure, so a connector can't be tricked into reaching anywhere else.

The full picture — how requests are contained, how your credentials are protected, and what data is stored — is in Connector security.

Get started

Build a connector

Point Clarify at your API, map the response, and design the card — step by step.

Discord auto-detect

Show a member's record automatically the instant their ticket opens, with no input.

Connector security

How your credentials are protected and how requests are kept contained.

Once built, a connector is linked to a category from its Connector Bindings, so it runs on exactly the ticket types you choose.

GitHub

Open GitHub issues straight from a ticket with /issue — using your repositories' issue templates, filled in from Discord, and linked back to the ticket.

Build a connector

Step-by-step guide to building a data connector — from base URL and authentication to mapping response fields onto your ticket cards.