Skip to content
Responsive (formerly RFPIO) logo

Connectors / Sales · HTTP Connector

Automate Responsive (formerly RFPIO) with Tray.ai

Create a project, create a question and add a Q&A pair in Responsive (formerly RFPIO).

What can you do with Responsive (formerly RFPIO) on Tray.ai?

Responsive, formerly RFPIO, is response management software for answering RFPs, security questionnaires and due diligence requests from a shared library of approved answers. Tray.ai connects to Responsive (formerly RFPIO) through the HTTP Connector, so your workflows can call the Responsive (formerly RFPIO) API alongside the rest of your stack.

  • Create a project in Responsive when a new RFP is logged against an opportunity in your CRM.
  • Add a Q&A pair to the Responsive library when your security team approves a new answer.
  • When sales submits a questionnaire request through your request form, create an intake in Responsive.
Connects through
HTTP Connector
Authentication
A bearer token

Set it up

Connect Responsive (formerly RFPIO) to Tray.ai

Each step uses Responsive (formerly RFPIO)'s own API details, from its documentation.

Step 1

Save Responsive (formerly RFPIO)'s API token

Save the token Responsive (formerly RFPIO) issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Import a request from Responsive (formerly RFPIO)'s docs

Add an HTTP Client step and paste a cURL example from Responsive (formerly RFPIO)'s API docs. Tray.ai fills in the method, URL, headers, and query.

Step 3

Start with “Get a project”

It's one of 24 documented actions, under Projects. The response comes back as data the next step can map into your other apps.

Step 4

Hand it to an AI agent

Wrap “Create a project” and “Update a project” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.

Workflows to build with Responsive (formerly RFPIO)

Each one uses actions and events from Responsive (formerly RFPIO)'s own API documentation.

Start a Responsive project when a Salesforce deal needs an RFP

When

An opportunity reaches the RFP stage in Salesforce

Then

  1. Create a project with the account, deal, and due date
  2. Post the new project to the proposals channel in Slack

With Salesforce and Slack

Create Responsive intakes from security questionnaire requests

When

A security questionnaire request is created in Jira

Then

  1. Create an intake with the request details and due date
  2. Add a comment on the Jira issue with the intake link

With Jira

Send Responsive content usage reports to Google Sheets

When

On a schedule

Then

  1. Get content usage report
  2. Add the results to the library review sheet in Google Sheets

With Google Sheets

Apps you can build on Responsive (formerly RFPIO) data

Internal tools your team can build with an AI assistant, each one using Responsive (formerly RFPIO) calls from its API documentation.

RFP intake queue

Lists intake requests by status and lets a proposal manager open a project from one.

Answer library lookup

Searches approved answers so sellers can find a response and update answers in the library.

Content usage report

Shows which library answers are used most and pulls custom report data for the proposal team.

Give your AI agents Responsive (formerly RFPIO) tools

Build an MCP server on Responsive (formerly RFPIO) in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works

  • Create a project
  • Create a question
  • Add a Q&A pair
  • Create an intake
  • List users
  • List custom reports
  • Get a project
  • Update a project

What the Responsive (formerly RFPIO) API covers

6 resources and 24 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Projects

  • Create a project
  • Get a project
  • Update a project
  • Search projects
  • Delete projects

Questions

  • Create a question
  • Update a question
  • Search project questions
  • Delete a question

Content library

  • Add a Q&A pair
  • Update Q&A pairs
  • Search the library
  • Delete a Q&A pair

Intake

  • Create an intake
  • Update an intake
  • Get an intake
  • List intakes by status

Users

  • List users
  • Create a user
  • Update a user
  • Delete a user

Reports

  • List custom reports
  • Get custom report data
  • Get content usage report

Checked against Responsive (formerly RFPIO)'s own documentation on 2026-11-07

developer.responsive.io

Frequently asked questions

What can a Tray.ai workflow do in Responsive (formerly RFPIO)?

+

The Responsive (formerly RFPIO) API documents 24 actions across 6 resources (Projects, Questions, Content library, Intake, Users, Reports). For example: Create a project; Create a question; Add a Q&A pair. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Responsive (formerly RFPIO)?

+

The Responsive (formerly RFPIO) API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

See Responsive (formerly RFPIO) working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.