# Request an integration


> There is a form. What to put in it, and what to do while you wait.
If the integration you want feels like it belongs in the built-in set, ask. There is a request form linked from the Integrations tab, and you can also go through the {{< support-link "support portal" >}}.

## What makes a request useful

Say what you want on screen, not just which product to connect. "Connect Jira" is a product. "The current sprint's blocked tickets, on a wall in the engineering area, updating through the day" tells us what to build.

Two other things help. How many screens it would run on, and whether it needs to be live to the minute or whether a refresh every few minutes is fine, because that changes the design.

What customers ask for is what gets built next. A request is not a commitment, and we prioritise by what is being asked for across industries.

## While you wait

**A web page.** If the tool has a dashboard, kiosk, or TV view, point a screen at that URL. It is often already exactly what an integration would have produced. See [Web pages](/docs/content/web-pages/).

**A published link.** Google Sheets and Google Slides both publish to the web, and the published URL goes straight in as content.

**A secret in an app.** If an app can take an API key directly, store it as a [secret](/docs/apps/setting-up/settings-and-secrets/) rather than waiting.

**Zapier, or the API.** See [Zapier and the API](/docs/integrations/beyond/zapier-and-the-api/).