Vote or request an integration
Logos, a Vote button and “Request another…” right on your integrations page.
A Vote list next to your integrations page: logo tiles, one-line summaries, a Vote button and an inline “Request another…” field that finds duplicates.
Set it up
Make a board for integrations
One request per integration. The list reads this board; it has to be on the portal because votes go through the public API.
Settings → Boards → New board
Give each one a logo and a line
Type the website and TheyAsked fetches its icon once (or pick an emoji, or upload). Add a one-line summary. From Claude, update_post does the same.
Inbox → request → Vote list card
{ "post": "shopify", "icon": { "kind": "domain", "value": "shopify.com" }, "summary": "Orders, customers and refunds" }Build the list
Pick the board, a title (“Vote or request an integration”), an eyebrow and a key. Order by hand, by votes or newest; show counts and status if you want.
Settings → Vote lists → New list
Put it where the question comes up
A button that opens it in the widget panel, or the list inline on the page. Same list in a WebView with ?list=integrations.
<button onclick="TheyAsked('open', { list: 'integrations' })"> Request an integration </button> <!-- or inline, sized to its content --> <div data-theyasked-list="integrations"></div>
What you learn
- Votes per integration
- With the accounts and MRR behind each logo.
- Source: Vote list
- Filter Insights to votes and requests that came through a list.
- Requests you didn’t list
- “woo commerce” is matched to WooCommerce; new names arrive as requests.
- Your own analytics
- voted and requested events, with the list key, for your product analytics.
Who it's for
- Commerce platforms
- Which marketplaces, payment providers and shipping carriers to add next.
- Developer tools
- Which languages, frameworks and CI providers.
- Analytics products
- Which data sources and destinations.