Integration Request

Research

IT & Operations

Collect a named third-party integration ask with the tool, the job to be done, and how often the data would move.

integrationpartnerapirequest

Feature requests that say “please add Slack” skip the job. This template makes the requester name the tool, the direction, and the work they are doing in a spreadsheet today.

Who it is for

Product and partnerships people who prioritize integrations from real workflows, not logo hunting.

When to use it

Use it when they named a third party. Feature Request is an in-product idea. API Access Request is a key for something you already expose. Vendor Onboarding is after you chose a vendor.

What this form collects

Requester identity, company, named tool, direction, volume, the job, and an optional workaround.

  • Public integrations roadmap inbox
  • Sales-assisted “we only buy if you connect X”
  • Internal ops asking for a finance export

Preview mode: This is a live read-only render of the template. Sign up to clone it into your account, or customize it with the guest AI builder first.

Integration Request

Collect a named third-party integration ask with the tool, the job to be done, and how often the data would move.

Ready to use this template?

Frequently asked questions

Will they see a status?

Not from this form. Reply from the tracker you already use, or point at a public board in the success copy.

How is this different from Feature Request?

Feature Request describes a job inside your product. Integration Request names another company’s system. Different owners, different questions.

Should ISVs use this form?

If they want you to build it, yes. If they want to build on you, send them to API Access Request.

Nearby GRTforms templates for the same job or the next step after this one.

Browse all Research templates

Browse IT & Operations templates