Integration
Connect Google Forms and Request Tracker (RT)
When New Form Response fires in Google Forms, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Add Question in Google Forms. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Google Forms and Request Tracker (RT) to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Google Forms and Request Tracker (RT) can do together
From Google Forms to Request Tracker (RT)
When New Form Response in Google Forms
then Create Ticket in Request Tracker (RT)
From Request Tracker (RT) to Google Forms
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Google Forms and Request Tracker (RT)
Triggers and actions 5 triggers · 25 actions
- New Form Response
Triggers when a new form response is received.
- New or Updated Form Response
Triggers when a form response is added or modified.
- Add Question
Adds a question (short answer, paragraph, multiple choice, checkboxes or drop-down) to an existing form.
- Create Form
Creates a new, empty Google Form with a title. Add questions with Add Question.
- Get Form
Returns a form's title, description, responder link and questions.
- Get Form Response
Returns one response submitted to a form, with its answers.
- List Form Responses
Returns the responses submitted to a form, with each response's answers.
- Update Form Info
Updates a form's title and/or description; a field left blank is kept.
- Ticket Correspondence
Triggers when a ticket is replied to (that is, corresponded with).
- Ticket Created
Triggers when a new Request Tracker ticket is created.
- Ticket Status Changed
Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
- Add asset
Create an asset.
- Add user
Create a user.
- Comment on a Ticket
Add an internal comment to a ticket and send to any internal watchers.
- Create Ticket
Create a new ticket in Request Tracker.
- Find Attachment
Locate an attachment by ID.
- Find Ticket
Locate a ticket by ID.
- Find Tickets
Issue a query to find matching tickets.
- Find Transaction
Find a transaction by ID
- Get asset
Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
- Get queue
Get a queue by id or name.
- Get user
Get a user by id or name.
- List queues
List all queues visible to user.
- List ticket history
List transactions of a ticket.
- Reply to a Ticket
Reply to the requestor and any internal or external watchers of a ticket.
- Update ticket
General ticket update (Owner, Priority, Queue, custom fields).
- Update Ticket Due Date
Update the due date of a ticket.
- Update Ticket Status
Update the status of a ticket.
- Update Ticket Subject
Update the subject of a ticket.
- Update user
Update a user.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Google Forms
Google Forms to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Forms to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Forms to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Forms to Google SheetsGoogle Sheets
Google Forms to MailchimpMailchimp marketing automation and email platform.
Google Forms to StripeStripe is a payment processing platform for online businesses.
More into Request Tracker (RT)
Gmail to Request Tracker (RT)Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Request Tracker (RT)Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Google Forms and Request Tracker (RT), answered
What can start an automation from Google Forms?
Any of Google Forms's 2 triggers in the catalog, including New Form Response and New or Updated Form Response. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Request Tracker (RT) when something happens in Google Forms?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to Google Forms?
Yes. When something happens in Request Tracker (RT), your agent can act in Google Forms too. This page covers both directions: Request Tracker (RT)'s triggers and Google Forms's actions are listed here as well.
Do I have to build a connector for Google Forms or Request Tracker (RT)?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.