Paid Application Handoff
Description
3 steps
- 1
Read the new response
At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.
- 2
Decide the next action
Decide the next action from the response, score, date, or category.
- 3
Apply to operations
Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.
Gmail
Setup steps
Setup Steps
This workflow includes external service integrations. Follow the steps below to set it up.
- 1
Read the new response
At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.
Integration: FORMLOVA - 2
Decide the next action
Decide the next action from the response, score, date, or category.
Integration: FORMLOVA - 3
Apply to operations
Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.
Integration: Gmail
Prompt Example
Goal: Hand off paid event or paid application checks to the right operator. Fields: Respondent email address, Response body, and Target date and time. Extract payment status, application details, receipt need, and special notes. Rules: Notify the owner through Gmail when payment needs confirmation, and log the operations record in Google Sheets. Hold unpaid or unclear items for review. Actions: For registrations collected through FORMLOVA paid forms and Stripe Connect, match responses against verifiable payment records. Prepare the operator notice through Gmail MCP and operations record through Google Sheets MCP. Use payment_check_pending, confirmed, or needs_manual_review as business tags only when supported by records; respondent statements alone do not prove payment or admission. This handoff does not refund or alter payments. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance. External connections: Separate Gmail / Google Sheets MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.
For you
- steps
- 3 steps
- Required plan
- Premium+
- Required integrations
- FORMLOVAGmail
What this workflow solves
Form responses arrive, but handoff for paid applications and reservation checks still depends on manual checking, causing delayed or missed follow-up.
Best for
- reservation desks
- paid application workflows
Expected outcome
When you run the prompt in chat, each reviewed response moves into a clear handoff for paid applications and reservation checks state, so the team can focus on the next required action.
Setup notes
- Connect FORMLOVA MCP in your AI client and confirm permission to read and update responses for the target form.
- Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them.
- Separate Gmail / Google Sheets MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.
- This recipe records data through external MCP calls made by your AI client. It does not configure native FORMLOVA Google Sheets sync or CRM integration.
- The required FORMLOVA plan is Premium or higher. Native email operations follow the tool's recipient, copy, time confirmation, and monthly sending limits.
- Business labels are not response statuses. Read current tags/notes immediately before updating and preserve them when appending; tags allow at most 20 values of 50 characters each. Ask if values cannot be read or limits would be exceeded.
FAQ
Can this work with an existing form?
Yes. Map the existing response fields to the required slots and adjust the notification or record destination.
Read the background
More in this category
Gmail Reservation Confirmation
ReservationsFreeAn official workflow for sending reservation confirmation through Gmail.
Reservation Cancel + Waitlist
ReservationsFreeAn official workflow for contacting waitlisted people when a reservation is canceled.
Reservation Reminder + No-show Prevention
ReservationsStandard+An official workflow for day-before reminders to reduce no-shows.
