Cards & placeholders
When Clarify looks something up — a Stripe payment, a Patreon membership, a response from one of your own systems — it needs to show that result to your team inside the ticket. It does this with a card: a rich Discord message you design once, which Clarify fills with live data every time it runs.
Cards are also what your members click to open a ticket. The same editor builds both.
What a card is
A card is a Discord message layout built with Discord's modern "Components V2" building blocks — headings, text, buttons, dividers and sections. You design the shape and wording; Clarify handles the rest.
You'll meet cards in three places:
Placeholders: how live data gets in
You don't type the actual amount or customer name into a card — that changes with every lookup. Instead you drop in a placeholder: a token wrapped in percent signs that Clarify swaps for the real value at the moment the card is shown.
For example, a card that reads:
Payment of %amount% — status %status% — from %customer%
might render as:
Payment of €49.00 — status succeeded — from [email protected]
Common placeholders include %amount%, %status% and %customer%, but the tokens available depend entirely on what the lookup returns. A Patreon membership offers different fields to a Stripe payment; your own connector offers whatever your API sends back.
%status%. Clarify replaces every one it recognises; anything it can't match is left untouched so you can spot it.Mapping fields to placeholders
Clarify can't know that your API's order_total should fill %amount% — so you tell it, by clicking.
Open the card step
In the setup wizard for an integration or data connector, go to the result card (blueprint) step.
Add your text and placeholders
Write the card the way you want your team to read it. Where a live value should appear, insert a placeholder.
Click a response field to map it
Clarify shows the fields the lookup returns. Click a field, then click the placeholder it should fill — that's the whole mapping. No formulas, no code.
Save
Your card is stored with the module. From then on, every lookup fills it with fresh data automatically.
If you don't design a card
You don't have to build anything to get started. If you leave the card step untouched, Clarify generates a sensible default card from the response — laying out the returned fields in a readable message so your team sees the data straight away.
Design your own card when you want tighter wording, fewer fields, or a layout that matches how your team works. Otherwise the default is a perfectly good starting point.
Cards on panels
The same editor builds creation panels — the message members click to open a ticket. Here the card holds your welcome copy and the button or dropdown that starts a ticket, rather than lookup data. See Panels for the full walkthrough.
%user_name% and %tag_name%. Those are covered in Categories, not here.Where to go next
Categories & ticket fields
How categories sort tickets into types and ticket fields collect what your team needs before a conversation begins.
Roles & permissions
How Clarify decides who on your team can handle tickets in Discord, who can change settings on the dashboard, and who is blocked from opening tickets.