Integration Request template

A single-page form that turns integrate-with-X requests into buildable specs. It asks which tool (a searchable dropdown of the usual suspects, with room for anything else), the concrete use case, which direction data should flow, and — the question that separates wishes from demand — whether the requester would upgrade plans to get it. That answer is your partner-roadmap sort key.

Use this template Start free — no card

7 questions · works on the free plan (500 responses/month) · fully customizable

What’s inside

The questions this template ships with — rename, reorder, or delete any of them in the builder.

01Which tool should we integrate with?Dropdown

02Link to the tool (if it's not in the list)Website

03What would you use the integration for?Long text

04Which direction matters?Multiple choice

05How important is this to you?Multiple choice

06Your email — we'll tell you when it's liveEmail

When to use this template

The integrations page of a SaaS, catching visitors who searched your docs for a connector that doesn't exist yet
A sales team logging the integration asks that come up on demo calls, in a form instead of a Slack thread
Prioritizing a Zapier alternative: if most requests are one-directional pushes to Slack or Sheets, a native connector may beat a full platform build
An API-first product deciding which official SDK or connector to build next

Tips to get more from it

The tool dropdown is searchable and allows Other, with a URL field to catch tools not on the list. Trim the eight defaults (Slack, Notion, Salesforce, HubSpot, Zapier, Google Sheets, Airtable, Jira) to tools you'd plausibly build.
The direction question (push, pull, or both) halves your engineering estimate when the answer is one-way — most requesters only need data flowing in one direction, and the use-case field will tell you which.
Sort the CSV export by the importance answer: I'd-upgrade-plans responses are revenue signals, and the email field means you can tell exactly those people when the integration ships.

Questions people ask

How do I decide which integration to build first?

Count requests, but weight them: a requester who says they would upgrade plans for it outweighs several nice-to-have votes. This form captures both the count and the weighting question, plus the use case behind each.

Why ask which direction the data should flow?

Because push-only and pull-only integrations are much cheaper to build than bidirectional sync. Knowing that most requesters need only one direction can move an integration from next-year to next-sprint.

Can I customize the list of tools?

Yes — the dropdown options are fully editable, and it already allows Other with an optional URL field, so tools you didn't anticipate still come through cleanly.