Discord auto-detect
Most connector lookups ask the member for something — an order number, an email, a username. Discord auto-detect skips the asking. When a ticket opens, Clarify quietly runs the connector using the opener's own Discord ID, fetches their record, and drops the result card onto the ticket. The member types nothing. The card is just there.
It's the difference between "please paste your account ID" and your team seeing the right account the moment the ticket lands.
When to use it
Reach for auto-detect whenever a member's record in your system can be found from their Discord identity — because they linked their Discord account in your shop, your CRM stores their Discord ID, or your platform can look someone up by it. Typical cases:
- A shop or membership site where accounts are linked to Discord.
- A CRM or database that keeps each customer's Discord ID.
- Any API that can return "the record for this Discord user".
If your system has no way to recognise a Discord ID, auto-detect can't help — use a normal typed ticket input instead and let the member supply the reference.
How it works
When a member opens a ticket, Clarify already knows their Discord ID — the unique number Discord assigns to every account. Auto-detect feeds that ID into your connector operation, runs it in the background, and maps the response onto a result card using your placeholders. No modal, no prompt, no waiting on the member.
There are two shapes it can take, depending on how your API answers.
Direct — feed the Discord ID into the request
Your API accepts a Discord ID as one of its parameters. Clarify passes the opener's ID straight into that parameter (a path segment, a query string, or a field in the request body) and your API returns exactly that member's record. This is the cleanest shape: one member in, one record out.
List-match — find the member in a list you return
Your API doesn't take a Discord ID, but it does return a list of records that each contain one — for example, "all members", where every member row carries their linked Discord ID. Clarify calls that operation, then scans the list and picks the row whose Discord ID matches the ticket opener. That matched row becomes the card.
Turn it on for an operation
Auto-detect is a property of a single connector operation — the same connector can have one operation that auto-detects and others that ask for typed input.
Open your connector
Go to Connectors in the dashboard and open the connector you want to edit.
Enable auto-detect on the operation
On the operation, switch on Discord auto-detect. Clarify then asks where the Discord ID goes:
- For a direct operation, choose the request parameter the ID should fill.
- For a list-match operation, choose the field in each returned record that holds the Discord ID, so Clarify knows what to match against.
Map the result to a card
Point the fields you care about — name, plan, status, balance — at the %placeholder% tokens on your result card, exactly as you would for a typed lookup. See Cards and placeholders for how mapping works.
Attach it to a category
Add the connector's input to the categories where you want the card to appear. Because the operation auto-detects, it runs on ticket open with no field shown to the member.
What the member sees
Nothing extra. The create modal is unchanged — they fill in whatever normal ticket inputs the category asks for (or none), and submit. The auto-detect lookup happens silently in the background, and the result card appears on the ticket for your team. If no matching record is found, no card is shown; the ticket opens as usual.
Auto-detect elsewhere in Clarify
The same idea powers a couple of built-in integrations, so the pattern may already look familiar:
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.
Connector security
How Clarify keeps user-built connectors safe — only real public endpoints, encrypted credentials, no redirects, and capped responses.