Forty GravityOps AI Feed setups for jobs that come up on client sites: triaging tickets, summarizing applications, scoring leads, translating entries, drafting replies, pulling dates and numbers into real fields, and generating images. Each recipe is one Gravity Forms form plus one AI feed.
We ran every recipe on this site on November 18, 2026 with our own Anthropic and OpenAI API keys: one invented sample entry per form, with one retry if the first run failed. Each tested output below is what the feed wrote into the entry, unedited. 40 of 40 recipes passed. A recipe without a passing run shows NOT TESTED YET instead of an output.
How to use a recipe
- Add your Anthropic API key (text feeds) and OpenAI API key (image feeds) in the GravityOps AI Feed settings.
- Download the form export and import it under Forms > Import/Export > Import Forms.
- AI feeds are not part of a Gravity Forms form export, so add the feed yourself: open the imported form, go to Settings > AI Text (or AI Image), add a feed and copy the settings listed with the recipe. Or add it in code with
GFAPI::add_feed( $form_id, $meta, 'goaif_text' )using the meta in the feed file. - The AI output fields use Administrative visibility, so visitors never see them. The feed fills them after submission.
- Rewrite the system prompt for each client: their voice, their rules. The output fields and their instructions are what put each value in the right place.
Pro or Premium
Each recipe is labelled by the field type it writes to, because that is what the plan controls. Pro covers generation after form submission into Single Line Text, Paragraph Text and Hidden fields, and AI Image feeds into a File Upload field. Premium (or Agency) adds Drop Down, Radio Buttons, Checkboxes, Multi Select, Number (not calculated), Date, Time, Email, Website, Phone, Name, Address and List destinations, plus frontend generate buttons, Gravity Flow steps, administrator reruns and token caps.
Settings every recipe shares
- Text feeds: Model Claude Sonnet 5.5, Effort Low, Thinking Provider default, Speed Standard, Max Tokens 4096, Existing Values Fill only empty targets, Trigger Mode After form submission, Execution Mode Synchronous.
- Image feeds: Model GPT Image 2.6 Flare, Trigger Mode After form submission, Quality Low, Complexity Low, Output Format JPEG, Content Filter Standard (provider default).
- Synchronous means the generated values are in the entry before the confirmation and notifications run, so you can use the output fields in both.
All 40 at a glance
Downloads: all-forms.json (all 40 forms in one import file) · all-feeds.json (every feed with its settings and meta) · results.json (test results)
The recipes
01. Support ticket summary and next step
Condenses a long support message into a one-line summary and a suggested next step, so whoever picks up the ticket starts from the point.
Plan: Pro. Writes to Single Line Text and Paragraph Text fields.
Fields
- Customer name (Single Line Text; required)
- Customer email (Email; required)
- Subject (Single Line Text; required)
- Message (Paragraph Text; required)
- Ticket summary (Single Line Text; AI output)
- Suggested next step (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-01 · Support ticket summary and next step |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Support ticket from {Customer name:1}.
Subject: {Subject:3}
Message:
{Message:4}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| summary | Ticket summary | One sentence, under 20 words, saying what the customer needs. |
| next_step | Suggested next step | One or two sentences with the first thing support should check or do. No promises to the customer. |
Sample input (invented)
- Customer name: Marta Okafor
- Customer email: marta.okafor@example.net
- Subject: Checkout form spins after update
- Message: Since the plugin update yesterday our checkout form spins forever after I click Pay. The card is charged by our payment processor but no entry shows up in Gravity Forms. It happened to two customers this morning. We are on WordPress 6.8 and PHP 8.2. Can you help today? This is costing us orders.
Tested output
- Ticket summary: Marta needs urgent help: checkout spins after Pay, cards get charged, but no Gravity Forms entry is created.
- Suggested next step: Check the plugin update changes and the site's error logs for failed submissions on WordPress 6.8 and PHP 8.2. Then compare the two affected customers' charges in the payment processor against missing entries.
Download: 01-support-ticket-summary-form.json (form export) · 01-support-ticket-summary-feed.json (feed settings and meta)
02. Job application summary
Gives the hiring manager a three-bullet summary of an application before they open the full entry. It summarizes; it does not rate the person.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Applicant name (Single Line Text; required)
- Role (Drop Down; required; choices: Front-end developer, Project manager, Support specialist)
- Years of experience (Single Line Text; required)
- Cover letter (Paragraph Text; required)
- Screening summary (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-02 · Job application summary |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Screening summary |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Summaries are for a human reviewer. Do not rate, rank or recommend the applicant.
User Prompt
Application for the {Role:2} role from {Applicant name:1} ({Years of experience:3} years of experience).
Cover letter:
{Cover letter:4}
Write exactly three short bullet points: relevant experience, notable projects or skills, and one thing the reviewer should ask about. Start each bullet with "- ".
Sample input (invented)
- Applicant name: Jonah Ferreira
- Role: Front-end developer
- Years of experience: 4
- Cover letter: I have spent four years building WordPress sites for small nonprofits and local shops, mostly custom themes and Gravity Forms work: multi-page donation forms, conditional logic for event registration, and a member portal. I care about accessibility and test every form with a screen reader. I am looking for a team where I can work on larger builds and learn more PHP.
Tested output
- Screening summary: – Relevant experience: Jonah Ferreira has 4 years of experience building WordPress sites for small nonprofits and local shops, mostly custom themes and Gravity Forms work.
– Notable projects or skills: Multi-page donation forms, conditional logic for event registration, and a member portal. Jonah also says he tests every form with a screen reader and cares about accessibility.
– Ask about: Jonah wants to work on larger builds and learn more PHP, so it may be worth asking what his current PHP experience looks like and what size of projects he has handled so far.
Download: 02-job-application-summary-form.json (form export) · 02-job-application-summary-feed.json (feed settings and meta)
03. Reply draft for contact form messages
Drafts a reply to a contact form message so staff can review, edit and send it instead of starting from a blank email.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Name (Single Line Text; required)
- Email (Email; required)
- Message (Paragraph Text; required)
- Draft reply (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-03 · Reply draft for contact form messages |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Draft reply |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You draft email replies for a small web design studio. Warm, brief and specific. Never quote prices, dates or commitments that are not in the message. Sign off as "The team".
User Prompt
Draft a reply to this message from {Name:1}. Under 120 words. Answer what you can from the message itself and ask at most two questions.
{Message:3}
Sample input (invented)
- Name: Elena Brooks
- Email: elena.brooks@example.net
- Message: Hi, we run a small bakery and want customers to order birthday cakes online: pick a size and flavor, choose a pickup date, and pay a deposit. Is that something you build, and roughly how long would it take?
Tested output
- Draft reply: Subject: Re: Online cake ordering for your bakery
Hi Elena,
Thanks for getting in touch, and what a lovely idea for a bakery. Yes, an ordering flow like that is something we build: size and flavor options, a pickup date picker, and a deposit payment at checkout.
I'd rather not guess at a timeline before we know a bit more, but we can give you a realistic estimate once we've talked through the details.
Two quick questions to help us do that:
1. Do you already have a website, or would this be starting from scratch?
2. Do you have a payment provider in mind for the deposits?
Looking forward to hearing more.
Warm regards,
The team
Download: 03-contact-reply-draft-form.json (form export) · 03-contact-reply-draft-feed.json (feed settings and meta)
04. Translate any entry into English
Detects the language of a message and writes an English translation next to the original, so one team can handle messages in any language.
Plan: Pro. Writes to Single Line Text and Paragraph Text fields.
Fields
- Name (Single Line Text; required)
- Message (Paragraph Text; required)
- Detected language (Single Line Text; AI output)
- English translation (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-04 · Translate any entry into English |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Message from {Name:1}:
{Message:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| language | Detected language | The language of the message as one English word, for example Spanish. |
| english | English translation | A faithful English translation. Keep names, numbers and product names unchanged. |
Sample input (invented)
- Name: Lucía Ramírez
- Message: Hola, compré la licencia anual la semana pasada pero no recibí el correo con la clave. ¿Me la pueden reenviar? El número de pedido es 48213. Gracias.
Tested output
- Detected language: Spanish
- English translation: Hello, I bought the annual license last week but I did not receive the email with the key. Can you resend it to me? The order number is 48213. Thank you.
Download: 04-translate-to-english-form.json (form export) · 04-translate-to-english-feed.json (feed settings and meta)
05. Product description in Spanish
Writes a Spanish version of a product description sent in by a client or vendor, ready for a native speaker to review.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Product name (Single Line Text; required)
- Description in English (Paragraph Text; required)
- Description in Spanish (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-05 · Product description in Spanish |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Description in Spanish |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Translate this product description for {Product name:1} into natural Latin American Spanish. Keep the product name, measurements and numbers unchanged. Return only the translation.
{Description in English:2}
Sample input (invented)
- Product name: Trailhead Daypack 22L
- Description in English: A light 22-liter daypack with a padded laptop sleeve, two side bottle pockets and a rain cover tucked into the base. Made from recycled nylon. Weighs 680 grams.
Tested output
- Description in Spanish: Una mochila ligera de 22 litros para el día a día, con compartimento acolchado para laptop, dos bolsillos laterales para botellas y una funda impermeable guardada en la base. Fabricada con nailon reciclado. Pesa 680 gramos.
Download: 05-translate-product-description-form.json (form export) · 05-translate-product-description-feed.json (feed settings and meta)
06. Action items from meeting notes
Pulls owners, tasks and due dates out of rough notes submitted after a client call.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Meeting (Single Line Text; required)
- Notes (Paragraph Text; required)
- Action items (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-06 · Action items from meeting notes |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Action items |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Meeting: {Meeting:1}
Notes:
{Notes:2}
List every action item as "- Owner: task (due date if stated)". If no owner is named, write "Unassigned". Do not add tasks that are not in the notes.
Sample input (invented)
- Meeting: Kickoff call, Harbor Physio site
- Notes: Sam to send sitemap draft by Friday. Client (Rita) will collect staff photos. Agreed the booking form needs an insurance question. Need logo files from Rita. Launch target is March 3. Alex to set up staging this week.
Tested output
- Action items: – Sam: Send sitemap draft (due Friday)
– Rita: Collect staff photos
– Unassigned: Add an insurance question to the booking form
– Rita: Provide logo files
– Alex: Set up staging (this week)
Download: 06-meeting-action-items-form.json (form export) · 06-meeting-action-items-feed.json (feed settings and meta)
07. Public reply to a customer review
Drafts a short public reply to a review collected through a form, with the tone matched to the star rating.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Reviewer first name (Single Line Text; required)
- Rating (Drop Down; required; choices: 5, 4, 3, 2, 1)
- Review (Paragraph Text; required)
- Reply draft (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-07 · Public reply to a customer review |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Reply draft |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Write a public reply from the owner to this {Rating:2}-star review by {Reviewer first name:1}. Under 80 words. Thank them and respond to their specific points. Offer no discounts and make no promises.
{Review:3}
Sample input (invented)
- Reviewer first name: Tomasz
- Rating: 3
- Review: Food was great, especially the lamb, but we waited 40 minutes for a table even with a reservation. Staff were apologetic. Would come back on a weekday.
Tested output
- Reply draft: Hi Tomasz, thank you for your review. We're delighted the lamb stood out for you, and we appreciate your kind words about our team. We're sorry that you waited 40 minutes for a table despite having a reservation. That's not the experience we want anyone to have, and your feedback is helpful. We'd be glad to welcome you back on a weekday.
Best wishes,
The Owner
Download: 07-review-reply-draft-form.json (form export) · 07-review-reply-draft-feed.json (feed settings and meta)
08. Testimonial clean-up and headline
Turns a rambling client testimonial into a clean quote and a short headline for a case study, without changing what the client said.
Plan: Pro. Writes to Paragraph Text and Single Line Text fields.
Fields
- Client name (Single Line Text; required)
- Company (Single Line Text; required)
- Testimonial (Paragraph Text; required)
- Clean quote (Paragraph Text; AI output)
- Headline (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-08 · Testimonial clean-up and headline |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Testimonial from {Client name:1} at {Company:2}:
{Testimonial:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| quote | Clean quote | Fix grammar and remove filler. Keep the meaning and the client wording where possible. Two or three sentences. |
| headline | Headline | Under 8 words, based on what the client actually said. |
Sample input (invented)
- Client name: Grace Whitfield
- Company: Whitfield and Rowe Landscaping
- Testimonial: so honestly before this we were doing quotes by email and it was a mess, like we lost track of half of them. now the quote form goes straight into our pipeline and the team gets a text when a big one comes in. i think we answered every lead within a day last month which never happened before
Tested output
- Clean quote: Before this, we handled quotes by email and it was a mess. We lost track of half of them. Now the quote form goes straight into our pipeline, and the team gets a text when a big one comes in. I think we answered every lead within a day last month, which never happened before.
- Headline: Every lead answered within a day
Download: 08-testimonial-cleanup-form.json (form export) · 08-testimonial-cleanup-feed.json (feed settings and meta)
09. Property listing description
Writes a listing description from the facts an agent enters, so every listing starts from the same structure and sticks to those facts.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Neighborhood (Single Line Text; required)
- Bedrooms (Single Line Text; required)
- Bathrooms (Single Line Text; required)
- Square feet (Single Line Text)
- Features (Paragraph Text; required)
- Listing description (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-09 · Property listing description |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Listing description |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You write property listings. Use only the facts given. No claims about schools, safety, investment value or neighbors. Use fair housing language.
User Prompt
Write a listing description of 90 to 120 words for a home in {Neighborhood:1}: {Bedrooms:2} bedrooms, {Bathrooms:3} bathrooms, {Square feet:4} square feet.
Features: {Features:5}
Sample input (invented)
- Neighborhood: Maple Hollow
- Bedrooms: 3
- Bathrooms: 2
- Square feet: 1640
- Features: Renovated kitchen with quartz counters and a gas range, south-facing backyard with raised garden beds, new roof in 2024, attached single garage, hardwood floors upstairs, walk-in pantry
Tested output
- Listing description: Welcome to this 3-bedroom, 2-bathroom home in Maple Hollow, offering 1,640 square feet of comfortable living space. The renovated kitchen features quartz counters and a gas range, along with a convenient walk-in pantry for all your storage needs. Hardwood floors run throughout the upstairs, adding warmth and character to the living areas. Outside, the south-facing backyard includes raised garden beds, ready for your planting season. A new roof installed in 2024 adds practical appeal, and the attached single garage provides covered parking and extra storage. Schedule a showing to see how this Maple Hollow home could fit your life.
Download: 09-property-listing-description-form.json (form export) · 09-property-listing-description-feed.json (feed settings and meta)
10. SEO title and meta description
Suggests an SEO title and a meta description from a page summary sent in through a content request form.
Plan: Pro. Writes to Single Line Text fields.
Fields
- Page title (Single Line Text; required)
- Page summary (Paragraph Text; required)
- Main keyword (Single Line Text)
- SEO title (Single Line Text; AI output)
- Meta description (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-10 · SEO title and meta description |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Page: {Page title:1}
Main keyword: {Main keyword:3}
Summary: {Page summary:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| seo_title | SEO title | Under 60 characters, uses the main keyword once, no clickbait. |
| meta_description | Meta description | Between 120 and 155 characters. A plain description of what the page offers. |
Sample input (invented)
- Page title: Gravity Forms maintenance plans
- Page summary: Monthly care plans for sites that rely on Gravity Forms: add-on updates tested on staging, failed-entry monitoring, spam rule tuning, and one hour of form changes each month.
- Main keyword: Gravity Forms maintenance
Tested output
- SEO title: Gravity Forms Maintenance Plans | Monthly Care
- Meta description: Monthly Gravity Forms maintenance plans with add-on updates tested on staging, failed-entry monitoring, spam rule tuning, and one hour of form changes.
Download: 10-seo-title-meta-description-form.json (form export) · 10-seo-title-meta-description-feed.json (feed settings and meta)
11. Bug report into steps to reproduce
Restructures a free-text bug report into numbered steps to reproduce and an expected-versus-actual line, ready to paste into your issue tracker.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Reporter (Single Line Text; required)
- Page or URL (Single Line Text)
- What happened (Paragraph Text; required)
- Steps to reproduce (Paragraph Text; AI output)
- Expected and actual (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-11 · Bug report into steps to reproduce |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Bug report from {Reporter:1} about {Page or URL:2}:
{What happened:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| steps | Steps to reproduce | Numbered steps, one action per line, only what the report supports. Write "Unknown" for anything the report does not cover. |
| expected_actual | Expected and actual | Two lines: "Expected: …" and "Actual: …". |
Sample input (invented)
- Reporter: Noor Haddad
- Page or URL: /register
- What happened: When I pick the Team plan on the registration form the seat count field disappears and the total stays at 0. If I go back, pick Solo and then Team again, it works. Chrome on a Mac. Tried twice.
Tested output
- Steps to reproduce: 1. Open the /register page in Chrome on a Mac.
2. Pick the Team plan on the registration form.
3. Look at the seat count field and the total.
4. Go back and pick Solo.
5. Pick Team again.
Note: Noor tried this twice. Other details such as the Chrome version, the Mac OS version and any entries typed before choosing the plan are Unknown. - Expected and actual: Expected: When Team is picked, the seat count field stays visible and the total updates from 0.
Actual: The seat count field disappears and the total stays at 0 on the first pick of Team. If Noor goes back, picks Solo and then picks Team again, it works.
Download: 11-bug-report-repro-steps-form.json (form export) · 11-bug-report-repro-steps-feed.json (feed settings and meta)
12. Crew brief from a service request
Turns a homeowner service request into a short brief the crew can read on site, with open questions marked.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Customer name (Single Line Text; required)
- Service (Drop Down; required; choices: Plumbing, Electrical, Carpentry, Painting)
- Describe the job (Paragraph Text; required)
- Access notes (Single Line Text)
- Crew brief (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-12 · Crew brief from a service request |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Crew brief |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Write a crew brief for a {Service:2} job for {Customer name:1}. Use three lines that start with "Job:", "Likely parts or materials:" and "Questions to confirm:". Short phrases. Mark anything uncertain as "confirm on site".
Job description: {Describe the job:3}
Access: {Access notes:4}
Sample input (invented)
- Customer name: Owen Mbeki
- Service: Plumbing
- Describe the job: Kitchen sink drains really slowly and there is a gurgling noise from the dishwasher when the sink empties. It started after we replaced the garbage disposal last month.
- Access notes: Side gate code 4471, the dog is friendly
Tested output
- Crew brief: Job: Plumbing for Owen Mbeki. Kitchen sink drains very slowly. Dishwasher gurgles when sink empties. Started after garbage disposal was replaced last month. Access via side gate, code 4471. Dog is friendly.
Likely parts or materials: Drain snake or auger. Bucket and towels. Disposal drain connection and dishwasher drain hose connection (check, confirm on site). Dishwasher knockout plug in disposal inlet, possibly not removed (confirm on site). Dishwasher drain hose high loop or air gap (confirm on site). P-trap and drain clamps or gaskets (confirm on site).
Questions to confirm: Is the dishwasher hose connected to the new disposal inlet, and was the knockout plug removed? Is the sink single or double bowl? Does water back up into the other bowl? Does the disposal run normally? Who installed the disposal, and was it done by the owner or a pro? Is the clog worse when the dishwasher runs? Best time to arrive and who will be home?
Download: 12-service-request-crew-brief-form.json (form export) · 12-service-request-crew-brief-feed.json (feed settings and meta)
13. Refund request case note in a Hidden field
Writes a neutral internal case note into a Hidden field, so the customer never sees it but it appears in the entry, in notifications and in exports.
Plan: Pro. Writes to Hidden fields.
Fields
- Order number (Single Line Text; required)
- Email (Email; required)
- Reason (Drop Down; required; choices: Not as described, Arrived damaged, Changed my mind, Other)
- Details (Paragraph Text; required)
- Case note (Hidden; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-13 · Refund request case note in a Hidden field |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Case note |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Write a neutral internal case note of two sentences for a refund request on order {Order number:1}. Reason given: {Reason:3}. Say what the customer is asking for and what evidence they mention. Give no opinion on whether to approve it.
Details: {Details:4}
Sample input (invented)
- Order number: BL-20931
- Email: kai.lindqvist@example.net
- Reason: Arrived damaged
- Details: The ceramic planter arrived with a crack across the base. The box looked fine. I have photos and can send them. I would like a replacement rather than my money back if possible.
Tested output
- Case note: Order BL-20931: The customer reports that the ceramic planter arrived damaged, with a crack across the base, and says the box looked fine. They are asking for a replacement rather than a refund if possible, and they mention having photos that they can send.
Download: 13-refund-case-note-hidden-form.json (form export) · 13-refund-case-note-hidden-feed.json (feed settings and meta)
14. Theme for open-ended feedback
Labels an open-ended survey answer with a short theme, so a few hundred answers can be sorted in the entries list or an export.
Plan: Pro. Writes to Single Line Text fields.
Fields
- Customer type (Drop Down; choices: New customer, Returning customer)
- What could we do better (Paragraph Text; required)
- Theme (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-14 · Theme for open-ended feedback |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Theme |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Read this answer to "What could we do better?" and reply with a theme of one to three words, for example "Shipping speed" or "Website checkout". Reply with the theme only.
{What could we do better:2}
Sample input (invented)
- Customer type: Returning customer
- What could we do better: I love the coffee, but every time I order, the tracking link does not work for the first two days, so I never know if it shipped.
Tested output
- Theme: Tracking link reliability
Download: 14-feedback-theme-form.json (form export) · 14-feedback-theme-feed.json (feed settings and meta)
15. Discovery call questions from a project brief
Reads a project inquiry and suggests five questions for the discovery call, aimed at the gaps in the brief.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Organization (Single Line Text; required)
- Budget range (Drop Down; choices: Under $5k, $5k to $15k, $15k to $40k, Over $40k)
- Project brief (Paragraph Text; required)
- Questions for the call (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-15 · Discovery call questions from a project brief |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Questions for the call |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Suggest five questions to ask {Organization:1} on a first call about this project (budget: {Budget range:2}). Focus on gaps in the brief: goals, integrations, content, timeline and who approves. Numbered list, one line each.
{Project brief:3}
Sample input (invented)
- Organization: Cedar Lane Montessori
- Budget range: $5k to $15k
- Project brief: We need a new site with an enrollment application that parents can save and finish later, a tour booking form, and a way for staff to review applications. Our current site is on an old builder and nobody here knows how to edit it.
Tested output
- Questions for the call: 1. What are your top goals for the new site, such as more tour bookings, more completed applications, or less admin work for staff, and how will you measure success?
2. Which tools does the site need to connect with, such as your current student records system, email or text reminders, calendar for tours, or payment for application fees?
3. Who will write and supply the content (photos, program descriptions, tuition info, application questions), and what from the old site should carry over?
4. Do you have a target launch date, and is anything driving it, like the start of enrollment season?
5. Who has final approval on design and content, and how many people need to sign off before launch?
Download: 15-discovery-call-questions-form.json (form export) · 15-discovery-call-questions-feed.json (feed settings and meta)
16. Grant application abstract
Condenses the project narrative from a grant application into a 100-word abstract for the review panel packet.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Organization (Single Line Text; required)
- Project title (Single Line Text; required)
- Amount requested (Single Line Text; required)
- Project narrative (Paragraph Text; required)
- Abstract (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-16 · Grant application abstract |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Abstract |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Write an abstract of no more than 100 words for the project "{Project title:2}" by {Organization:1}, requesting {Amount requested:3}. Cover the need, what will be done, who benefits and how success is measured, using only the narrative.
{Project narrative:4}
Sample input (invented)
- Organization: Riverbend Community Garden Network
- Project title: Seed Library and Teaching Beds
- Amount requested: $12,500
- Project narrative: Our network runs six community gardens on vacant lots. We want to build a seed library in the branch library lobby with 300 varieties, and four raised teaching beds at the Elm Street garden where volunteers will run monthly workshops for families. Last year 140 families gardened with us and 60 asked for seeds and lessons. We will track seed checkouts, workshop attendance and how many families return seeds at the end of the season. Funds cover lumber, soil, seed stock, cabinets and a part-time coordinator for eight months.
Tested output
- Abstract: Abstract: Seed Library and Teaching Beds
Riverbend Community Garden Network, which runs six community gardens on vacant lots, requests $12,500. Last year 140 families gardened with us, and 60 asked for seeds and lessons. We will create a seed library of 300 varieties in the branch library lobby and build four raised teaching beds at the Elm Street garden, where volunteers will run monthly family workshops. Funds cover lumber, soil, seed stock, cabinets and a part-time coordinator for eight months. Local families will benefit. We will measure success by tracking seed checkouts, workshop attendance and the number of families who return seeds at season's end.
(Word count: 93)
Download: 16-grant-application-abstract-form.json (form export) · 16-grant-application-abstract-feed.json (feed settings and meta)
17. Welcome paragraph for new members
Writes a short, personal welcome paragraph from a membership signup, ready to drop into the welcome email with a merge tag.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- First name (Single Line Text; required)
- Membership (Drop Down; required; choices: Studio, Community, Mentor)
- What do you hope to get from joining (Paragraph Text; required)
- Welcome paragraph (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-17 · Welcome paragraph for new members |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Welcome paragraph |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Write a welcome paragraph of 50 to 70 words to {First name:1}, who just joined the {Membership:2} membership of a co-working space for freelancers. Refer to what they hope to get from it. No promises about specific events or people.
Their answer: {What do you hope to get from joining:3}
Sample input (invented)
- First name: Ines
- Membership: Community
- What do you hope to get from joining: I just went freelance after six years at an agency. I want people to have lunch with, and maybe find a developer to partner with on bigger WordPress projects.
Tested output
- Welcome paragraph: Welcome to the Community membership, Ines! Congratulations on going freelance after six years at an agency. That's a big step, and we're glad you've chosen to take it with us. You mentioned wanting people to have lunch with and a developer to partner with on bigger WordPress projects. Being around other freelancers is a great way to start on both, so say hello, get chatting, and enjoy settling in.
Download: 17-member-welcome-paragraph-form.json (form export) · 17-member-welcome-paragraph-feed.json (feed settings and meta)
18. Scope outline and open questions from a project request
Turns a website request into a draft scope outline and a list of open questions, so the estimate starts from structure instead of a wall of text.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Organization (Single Line Text; required)
- What do you need (Paragraph Text; required)
- Deadline (Single Line Text)
- Scope outline (Paragraph Text; AI output)
- Open questions (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-18 · Scope outline and open questions from a project request |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Request from {Organization:1}. Deadline mentioned: {Deadline:3}.
{What do you need:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| scope | Scope outline | Bulleted outline of the pages, forms and integrations the request names. Start each line with "- ". Nothing that is not in the request. |
| questions | Open questions | Up to five questions that must be answered before an estimate. Start each line with "- ". |
Sample input (invented)
- Organization: Northfield Youth Soccer Club
- What do you need: New website with team pages for 14 teams, a player registration form with a sibling discount and payment, volunteer sign-up for match days, and a way for coaches to post schedule changes. We currently use spreadsheets and a lot of email.
- Deadline: Before spring registration opens in February
Tested output
- Scope outline: – Client: Northfield Youth Soccer Club
– Deadline mentioned: Before spring registration opens in February
– New website replacing current spreadsheets and email
– Team pages for 14 teams
– Player registration form with a sibling discount and payment
– Volunteer sign-up form for match days
– A way for coaches to post schedule changes - Open questions: – Which payment method or provider should the registration form use, and what should the sibling discount be?
– What information should the player registration form collect from families?
– What should each team page show, and who will keep the content up to date?
– How should coaches post schedule changes, and how should families be notified of them (for example, on the site only or also by email)?
– What exact date in February does spring registration open, and do you have existing spreadsheet data that needs to be brought into the new site?
Download: 18-rfp-scope-outline-form.json (form export) · 18-rfp-scope-outline-feed.json (feed settings and meta)
19. Redact personal details before sharing
Writes a copy of a message with phone numbers, email addresses, street addresses and account numbers replaced, so it can be shared with a contractor or pasted into a ticket.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Original message (Paragraph Text; required)
- Redacted message (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-19 · Redact personal details before sharing |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Redacted message |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You redact personal data. Replace phone numbers with [PHONE], email addresses with [EMAIL], street addresses with [ADDRESS], and card, bank or account numbers with [NUMBER]. Keep everything else exactly as written. Return only the redacted text.
User Prompt
Redact this message:
{Original message:1}
Sample input (invented)
- Original message: Hi, this is Dara Quinlan. Please call me back on 555-0142 or email dara.q@example.com. The install address is 18 Larkspur Court, Fairview. My invoice was paid from the account ending 4417, but I think I was charged twice.
Tested output
- Redacted message: Hi, this is Dara Quinlan. Please call me back on [PHONE] or email [EMAIL]. The install address is [ADDRESS], Fairview. My invoice was paid from the account ending [NUMBER], but I think I was charged twice.
Download: 19-redact-personal-details-form.json (form export) · 19-redact-personal-details-feed.json (feed settings and meta)
20. Rewrite copy in a chosen tone
Rewrites a draft announcement in the tone picked from a drop down, keeping every fact, date and number the same.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Tone (Drop Down; required; choices: Friendly, Formal, Short and direct)
- Draft (Paragraph Text; required)
- Rewritten copy (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-20 · Rewrite copy in a chosen tone |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Rewritten copy |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Rewrite this draft in a {Tone:1} tone. Keep every fact, date and number unchanged. Do not add new claims. Same length or shorter.
{Draft:2}
Sample input (invented)
- Tone: Friendly
- Draft: Please be advised that the office will be closed on Monday the 14th for maintenance of the heating system. Appointments on that day have been moved to Tuesday the 15th at the same times. Contact reception with questions.
Tested output
- Rewritten copy: Just a heads-up: our office will be closed on Monday the 14th while the heating system is being maintained. Any appointments that day have moved to Tuesday the 15th at the same times. If you have questions, please reach out to reception. We're happy to help!
Download: 20-tone-rewrite-form.json (form export) · 20-tone-rewrite-feed.json (feed settings and meta)
21. Key points from workshop feedback
Summarizes one attendee feedback form into three points the instructor can act on.
Plan: Pro. Writes to Paragraph Text fields.
Fields
- Session (Drop Down; required; choices: Forms 101, Conditional logic deep dive, Payments and add-ons)
- Rating out of 5 (Single Line Text)
- What worked (Paragraph Text; required)
- What to change (Paragraph Text)
- Key points (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-21 · Key points from workshop feedback |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | Single target field |
| Target Field | Key points |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Attendee feedback for the {Session:1} session, rated {Rating out of 5:2} out of 5.
What worked: {What worked:3}
What to change: {What to change:4}
Write three short bullet points for the instructor: one strength, one change, one concrete suggestion. Start each with "- ".
Sample input (invented)
- Session: Conditional logic deep dive
- Rating out of 5: 4
- What worked: The live build of the quote calculator was very useful, and I liked getting the export file afterwards.
- What to change: It went too fast in the last 20 minutes. More time on showing and hiding sections, less on email routing.
Tested output
- Key points: – Strength: The live build of the quote calculator was very useful, and the export file afterwards was a welcome extra.
– Change: The last 20 minutes went too fast for this attendee.
– Suggestion: Spend more time on showing and hiding sections, and less on email routing.
Note: the bullets above need to start with "- " exactly, so here they are in that form:
– Strength: The live build of the quote calculator was very useful, and the export file afterwards was a welcome extra.
– Change: The last 20 minutes went too fast for this attendee.
– Suggestion: Spend more time on showing and hiding sections, and less on email routing.
Download: 21-workshop-feedback-key-points-form.json (form export) · 21-workshop-feedback-key-points-feed.json (feed settings and meta)
22. Ticket priority and department routing
Sets a Priority radio button and a Department drop down from the ticket text, so notifications and Gravity Flow steps can route on real field values.
Plan: Premium. Writes to Radio Buttons and Drop Down fields, which need Premium.
Fields
- Name (Single Line Text; required)
- Email (Email; required)
- How can we help (Paragraph Text; required)
- Priority (Radio Buttons; AI output; choices: Low, Normal, High, Urgent)
- Department (Drop Down; AI output; choices: Billing, Technical, Sales, Account)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-22 · Ticket priority and department routing |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Support request from {Name:1}:
{How can we help:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| priority | Priority | Urgent: site down, payments failing or data loss. High: a key feature broken for many users. Normal: one user blocked, or a question with a deadline. Low: how-to questions and requests. |
| department | Department | Billing for invoices, refunds and charges. Technical for errors and broken features. Sales for pricing and plan questions before purchase. Account for logins, users and license transfers. |
Sample input (invented)
- Name: Felix Andersson
- Email: felix.andersson@example.net
- How can we help: Our donation form stopped taking payments about an hour ago. Every donor gets "payment failed" and we have a fundraising email going out at 6pm today. Nothing changed on our side as far as I know.
Tested output
- Priority: Urgent
- Department: Technical
Download: 22-ticket-priority-department-form.json (form export) · 22-ticket-priority-department-feed.json (feed settings and meta)
23. Lead score from 0 to 100
Scores a project inquiry from 0 to 100 against the ideal-client rules written in the feed and stores the reason, so sales can sort entries by a Number field.
Plan: Premium. Writes to Number field, which needs Premium.
Fields
- Company (Single Line Text; required)
- Company size (Drop Down; choices: 1 to 10, 11 to 50, 51 to 200, More than 200)
- Budget (Drop Down; choices: Under $5k, $5k to $15k, $15k to $40k, Over $40k)
- Timeline (Drop Down; choices: This month, 1 to 3 months, 3 to 6 months, Just researching)
- Project details (Paragraph Text; required)
- Lead score (Number; AI output; range 0 to 100)
- Score reason (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-23 · Lead score from 0 to 100 |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Our ideal client: an organization of 11 to 200 people, a budget of $5k or more, a timeline within 3 months, and a project centered on forms, workflows or integrations.
User Prompt
Score this inquiry from {Company:1}. Size: {Company size:2}. Budget: {Budget:3}. Timeline: {Timeline:4}.
Details: {Project details:5}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| score | Lead score | Whole number from 0 to 100 measuring fit with our ideal client. |
| reason | Score reason | One or two sentences naming the facts that raised or lowered the score. |
Sample input (invented)
- Company: Lakeshore Veterinary Group
- Company size: 51 to 200
- Budget: $15k to $40k
- Timeline: 1 to 3 months
- Project details: We have four clinics and want one online intake form per clinic that feeds a single approval workflow for new client records, plus monthly reporting. Today it is all paper.
Tested output
- Lead score: 95
- Score reason: Lakeshore Veterinary Group is a strong fit: its size (51 to 200) is within our 11 to 200 range, its $15k to $40k budget is above our $5k minimum, and its 1 to 3 month timeline is within 3 months. The project is also centered on forms and workflows, with one intake form per clinic feeding a single approval workflow plus monthly reporting, replacing a paper process.
Download: 23-lead-score-form.json (form export) · 23-lead-score-feed.json (feed settings and meta)
24. Sentiment and main complaint
Tags feedback as Positive, Neutral or Negative in a Radio Buttons field and pulls out the main complaint, so a follow-up notification can target unhappy customers.
Plan: Premium. Writes to Radio Buttons field, which needs Premium.
Fields
- Name (Single Line Text)
- Feedback (Paragraph Text; required)
- Sentiment (Radio Buttons; AI output; choices: Positive, Neutral, Negative)
- Main complaint (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-24 · Sentiment and main complaint |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Customer feedback:
{Feedback:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| sentiment | Sentiment | Overall sentiment of the feedback. |
| complaint | Main complaint | The main complaint in under 12 words, or "None" if there is no complaint. |
Sample input (invented)
- Name: Harriet Osei
- Feedback: The cleaners arrived on time and the kitchen looked great, but they skipped the upstairs bathroom completely and nobody told us. We had to call twice to get someone back.
Tested output
- Sentiment: Negative
- Main complaint: Upstairs bathroom was skipped, and we had to call twice.
Download: 24-feedback-sentiment-form.json (form export) · 24-feedback-sentiment-feed.json (feed settings and meta)
25. Topic checkboxes for incoming messages
Ticks every topic a message covers in a Checkboxes field, so one message can show up in several filtered entry views.
Plan: Premium. Writes to Checkboxes field, which needs Premium.
Fields
- Email (Email; required)
- Message (Paragraph Text; required)
- Topics (Checkboxes; AI output; choices: Billing, Login and accounts, Performance, Integrations, Feature request, Bug)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-25 · Topic checkboxes for incoming messages |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Message:
{Message:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| topics | Topics | Every topic the message clearly covers. Leave out topics that are only implied. |
Sample input (invented)
- Email: ravi.chandran@example.net
- Message: Three things. The sync to our email marketing tool stopped adding new subscribers last week. Could you add a way to export entries to a spreadsheet on a schedule? And we were charged for two seats but only have one user.
Tested output
- Topics: Billing, Integrations, Feature request
Download: 25-message-topic-checkboxes-form.json (form export) · 25-message-topic-checkboxes-feed.json (feed settings and meta)
26. Event date and guest count from free text
Reads a free-text event inquiry and fills a Date field and a Number field, so inquiries can be sorted and filtered by date and size.
Plan: Premium. Writes to Date and Number fields, which need Premium.
Fields
- Name (Single Line Text; required)
- Email (Email; required)
- Tell us about your event (Paragraph Text; required)
- Event date (Date; AI output)
- Guest count (Number; AI output; range 1 to 2000)
- Event type (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-26 · Event date and guest count from free text |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Event inquiry from {Name:1}:
{Tell us about your event:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| event_date | Event date | The event date stated in the message. If only a range is given, use the first day. |
| guests | Guest count | The number of guests as a whole number. If a range is given, use the higher number. |
| event_type | Event type | The type of event in two or three words, for example "Company dinner". |
Sample input (invented)
- Name: Mei Tanaka
- Email: mei.tanaka@example.net
- Tell us about your event: We are planning a retirement party for our office manager on Saturday, June 12, 2027, in the evening. Somewhere between 60 and 75 guests, buffet style, and we would like the garden room if it is free.
Tested output
- Event date: 2027-06-12
- Guest count: 75
- Event type: Retirement party
Download: 26-event-date-guest-count-form.json (form export) · 26-event-date-guest-count-feed.json (feed settings and meta)
27. Contact details from a pasted email signature
Fills Email, Website, name and job title fields from a pasted email signature, so a quick-add form captures a contact in one paste.
Plan: Premium. Writes to Email and Website fields, which need Premium.
Fields
- Paste the email signature (Paragraph Text; required)
- Full name (Single Line Text; AI output)
- Job title (Single Line Text; AI output)
- Contact email (Email; AI output)
- Website (Website; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-27 · Contact details from a pasted email signature |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Extract the contact details from this email signature:
{Paste the email signature:1}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| full_name | Full name | Full name as written. |
| job_title | Job title | Job title as written, without the company name. |
| Contact email | Email address exactly as written. | |
| website | Website | Website as a full URL that starts with https:// |
Sample input (invented)
- Paste the email signature: Best regards,
Adaeze Nwosu
Operations Lead, Brightwater Kitchens
m: 555-0187
adaeze@brightwaterkitchens.example
www.brightwaterkitchens.example
Tested output
- Full name: Adaeze Nwosu
- Job title: Operations Lead
- Contact email: adaeze@brightwaterkitchens.example
- Website: https://www.brightwaterkitchens.example
Download: 27-signature-contact-details-form.json (form export) · 27-signature-contact-details-feed.json (feed settings and meta)
28. Skills match against listed requirements
Compares the skills an applicant lists with requirements written into the feed, sets a Yes, Partly or No radio, and lists what is missing for the human reviewer.
Plan: Premium. Writes to Radio Buttons field, which needs Premium.
Fields
- Applicant name (Single Line Text; required)
- Skills and experience (Paragraph Text; required)
- Meets requirements (Radio Buttons; AI output; choices: Yes, Partly, No)
- Missing requirements (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-28 · Skills match against listed requirements |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Requirements for the Support Specialist role: two years of customer support, fluent written English, experience with WordPress, and comfort with a ticketing tool. Compare stated skills only and do not judge the person. A human makes every decision.
User Prompt
Applicant {Applicant name:1} lists:
{Skills and experience:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| meets | Meets requirements | Yes if every requirement is clearly stated, Partly if some are, No if none are. |
| missing | Missing requirements | Requirements not clearly stated in the application, one per line starting with "- ", or "None". |
Sample input (invented)
- Applicant name: Bruno Salgado
- Skills and experience: Three years on the help desk at a regional internet provider, answering email and chat tickets in a ticketing system. Native Portuguese speaker with fluent written English. I have built two small sites for friends but have not used WordPress professionally.
Tested output
- Meets requirements: Partly
- Missing requirements: – Experience with WordPress: the entry says he built two small sites for friends but does not say they were built with WordPress, and says he has not used WordPress professionally.
Download: 28-application-skills-match-form.json (form export) · 28-application-skills-match-feed.json (feed settings and meta)
29. Language drop down and English summary
Sets a Language drop down and writes a two-sentence English summary, so conditional notifications can send each message to the right speaker.
Plan: Premium. Writes to Drop Down field, which needs Premium.
Fields
- Message (Paragraph Text; required)
- Language (Drop Down; AI output; choices: English, Spanish, French, German, Portuguese, Other)
- English summary (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-29 · Language drop down and English summary |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Message:
{Message:1}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| language | Language | The language the message is written in. Use Other for any language not listed. |
| summary | English summary | Two-sentence English summary of what the sender wants. |
Sample input (invented)
- Message: Bonjour, nous organisons un séminaire pour 40 personnes en avril et nous cherchons un formulaire d’inscription avec paiement en ligne et choix des ateliers. Pouvez-vous nous envoyer un devis ?
Tested output
- Language: French
- English summary: The sender is organizing a seminar for 40 people in April and wants a registration form with online payment and a choice of workshops. They are asking for a quote.
Download: 29-language-routing-form.json (form export) · 29-language-routing-feed.json (feed settings and meta)
30. Spam check for contact messages
Flags likely sales pitches and link offers with a Yes or No radio and a reason, so a conditional notification can skip them. Use it as a second check after your anti-spam tools, not instead of them.
Plan: Premium. Writes to Radio Buttons field, which needs Premium.
Fields
- Name (Single Line Text)
- Email (Email; required)
- Message (Paragraph Text; required)
- Likely spam (Radio Buttons; AI output; choices: Yes, No)
- Spam reason (Single Line Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-30 · Spam check for contact messages |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Contact form message from {Name:1} ({Email:2}):
{Message:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| likely_spam | Likely spam | Yes for unsolicited sales pitches, SEO or link offers, and messages unrelated to our services. No for real inquiries, even short ones. |
| reason | Spam reason | Under 12 words. |
Sample input (invented)
- Name: Kevin Marsh
- Email: growth.team@example.net
- Message: Hello webmaster, I noticed your website is not ranking on page one. Our team can get you 300 high authority backlinks in 10 days for a one-time fee. Reply YES to get a free audit.
Tested output
- Likely spam: Yes
- Spam reason: Unsolicited SEO backlink sales pitch, unrelated to our services.
Download: 30-spam-check-form.json (form export) · 30-spam-check-feed.json (feed settings and meta)
31. Care plan recommendation from a short quiz
Recommends one of three care plans in a Radio Buttons field from quiz answers, using rules written in the feed, with a reason you can show in the confirmation.
Plan: Premium. Writes to Radio Buttons field, which needs Premium.
Fields
- Number of sites (Drop Down; required; choices: 1, 2 to 5, 6 or more)
- Forms that take payments (Drop Down; required; choices: None, One or two, Many)
- Anything else we should know (Paragraph Text; required)
- Recommended plan (Radio Buttons; AI output; choices: Starter care, Growth care, Priority care)
- Why this plan (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-31 · Care plan recommendation from a short quiz |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Plans: Starter care is for one site with no payment forms. Growth care is for up to five sites or any site with payment forms. Priority care is for six or more sites, or when the client needs same-day responses.
User Prompt
Sites: {Number of sites:1}. Payment forms: {Forms that take payments:2}.
Notes: {Anything else we should know:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| plan | Recommended plan | The single plan that fits the rules. |
| why | Why this plan | One or two sentences addressed to the client that cite their answers. |
Sample input (invented)
- Number of sites: 2 to 5
- Forms that take payments: One or two
- Anything else we should know: We run event registration with deposits on one site and a newsletter on the others. Registration opens in January and we cannot afford downtime then.
Tested output
- Recommended plan: Growth care
- Why this plan: You have two to five sites and one or two payment forms, including event registration with deposits, which fits Growth care (up to five sites or any site with payment forms). You didn't ask for same-day responses or have six or more sites, so Priority care isn't required based on your entry.
Download: 31-care-plan-recommendation-form.json (form export) · 31-care-plan-recommendation-feed.json (feed settings and meta)
32. Invoice total, due date and vendor from pasted text
Fills Number, Date and text fields from invoice text pasted into an accounts payable form, so totals and due dates are sortable.
Plan: Premium. Writes to Number and Date fields, which need Premium.
Fields
- Paste invoice text (Paragraph Text; required)
- Vendor (Single Line Text; AI output)
- Invoice number (Single Line Text; AI output)
- Total due (Number; AI output)
- Due date (Date; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-32 · Invoice total, due date and vendor from pasted text |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Extract these details from the invoice text:
{Paste invoice text:1}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| vendor | Vendor | The vendor business name. |
| invoice_number | Invoice number | The invoice number exactly as written. |
| total_due | Total due | The total amount due as a number, without a currency symbol. |
| due_date | Due date | The payment due date. |
Sample input (invented)
- Paste invoice text: INVOICE
Copperline Print Studio
Invoice no. CPS-1186
Issued: 3 November 2026
Terms: Net 30
Business cards (500): 145.00
Event banners (2): 310.00
Delivery: 25.00
Total due: USD 480.00
Due date: 3 December 2026
Tested output
- Vendor: Copperline Print Studio
- Invoice number: CPS-1186
- Total due: 480.0
- Due date: 2026-12-03
Download: 32-invoice-details-form.json (form export) · 32-invoice-details-feed.json (feed settings and meta)
33. Moderation suggestion for community posts
Suggests Approve, Needs edit or Reject in a Drop Down for a post submitted through a form, with a note for the moderator, before anything goes live.
Plan: Premium. Writes to Drop Down field, which needs Premium.
Fields
- Display name (Single Line Text; required)
- Post title (Single Line Text; required)
- Post (Paragraph Text; required)
- Suggested decision (Drop Down; AI output; choices: Approve, Needs edit, Reject)
- Moderator note (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-33 · Moderation suggestion for community posts |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Community rules: posts are about home gardening, no selling, no personal attacks, and no contact details in public posts.
User Prompt
Post "{Post title:2}" by {Display name:1}:
{Post:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| decision | Suggested decision | Approve if it follows every rule, Needs edit if a small change fixes it, Reject for selling or attacks. |
| note | Moderator note | One sentence naming the rule involved, or "Follows the rules". |
Sample input (invented)
- Display name: TomatoTess
- Post title: Blossom end rot fix that worked for me
- Post: Lost half my tomatoes to blossom end rot last summer. This year I watered deeply twice a week instead of a little every day and mulched with straw, and so far there is no rot at all. Happy to answer questions, text me at 555-0119.
Tested output
- Suggested decision: Needs edit
- Moderator note: The post is on-topic gardening advice, but it breaks the rule against contact details in public posts, so please remove the phone number 555-0119.
Download: 33-community-post-moderation-form.json (form export) · 33-community-post-moderation-feed.json (feed settings and meta)
34. Skills multi select from a freelancer bio
Selects matching skills in a Multi Select field from a short bio, so directory filters work without asking people to tick a long list.
Plan: Premium. Writes to Multi Select field, which needs Premium.
Fields
- Name (Single Line Text; required)
- Short bio (Paragraph Text; required)
- Skills (Multi Select; AI output; choices: WordPress, Gravity Forms, PHP, JavaScript, Design, SEO, Copywriting, Accessibility)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-34 · Skills multi select from a freelancer bio |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
Freelancer bio for {Name:1}:
{Short bio:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| skills | Skills | Every skill the bio clearly states. |
Sample input (invented)
- Name: Leah Abernathy
- Short bio: I build WordPress sites for nonprofits, mostly custom blocks in JavaScript and PHP, and I handle complex Gravity Forms setups like multi-page applications. I also write the microcopy for forms and check everything against WCAG.
Tested output
- Skills: WordPress, Gravity Forms, PHP, JavaScript, Copywriting, Accessibility
Download: 34-freelancer-skills-form.json (form export) · 34-freelancer-skills-feed.json (feed settings and meta)
35. Rough hours estimate with assumptions
Puts a rough hours figure in a Number field with the items behind it, using rates of thumb written in the feed, so whoever writes the quote has a starting point to correct.
Plan: Premium. Writes to Number field, which needs Premium.
Fields
- Company (Single Line Text; required)
- What do you need built (Paragraph Text; required)
- Estimated hours (Number; AI output; range 1 to 500)
- Assumptions (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-35 · Rough hours estimate with assumptions |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English. Rates of thumb: a simple form 2 hours, a multi-page form with conditional logic 6 hours, a payment integration 4 hours, an approval workflow 8 hours, a custom report 6 hours, and project management at 15 percent of the total.
User Prompt
Estimate the build for {Company:1}:
{What do you need built:2}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| hours | Estimated hours | Total hours as a whole number, using the rates of thumb. |
| assumptions | Assumptions | Bulleted list of the items counted and their hours. Start each line with "- ". |
Sample input (invented)
- Company: Pinewood Dance Academy
- What do you need built: A multi-page class registration form with conditional logic for age groups, card payments for the term fee, and an approval step so the office confirms placement before the confirmation email goes out.
Tested output
- Estimated hours: 21
- Assumptions: – Multi-page registration form with conditional logic for age groups: 6 hours
– Card payment integration for the term fee: 4 hours
– Approval workflow so the office confirms placement before the confirmation email is sent: 8 hours
– Subtotal: 18 hours
– Project management at 15 percent of the subtotal: 2.7 hours, giving 20.7 hours in total, rounded up to 21 whole hours
– No custom report was requested, so none is counted
Download: 35-build-hours-estimate-form.json (form export) · 35-build-hours-estimate-feed.json (feed settings and meta)
36. NPS follow-up type and draft message
Picks a follow-up type in a Drop Down for an NPS response and drafts the message, so low scores become a call-back task and high scores get a thank-you.
Plan: Premium. Writes to Drop Down field, which needs Premium.
Fields
- Customer name (Single Line Text; required)
- Score (Drop Down; required; choices: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
- Why that score (Paragraph Text)
- Follow-up type (Drop Down; AI output; choices: Thank you, Fix request, Call back)
- Draft message (Paragraph Text; AI output)
Feed settings (Form Settings > AI Text)
| Setting | Value |
|---|---|
| Name | AI3-36 · NPS follow-up type and draft message |
| Model | Claude Sonnet 5.5 |
| Effort | Low |
| Thinking | Provider default |
| Speed | Standard |
| Max Tokens | 4096 |
| Output Mode | JSON multi-field mapping |
| Existing Values | Fill only empty targets |
| Trigger Mode | After form submission |
| Execution Mode | Synchronous |
| Conditional Logic | Off |
System Prompt
You process Gravity Forms entries for a small business. Use only facts that appear in the entry. Never invent names, prices, dates or promises. Write plain, friendly English.
User Prompt
{Customer name:1} gave a score of {Score:2} out of 10.
Reason: {Why that score:3}
Output Map
| Response name | Destination field | Output instructions |
|---|---|---|
| follow_up | Follow-up type | Thank you for 9 or 10. Fix request for 7 or 8 with a concrete issue. Call back for 0 to 6. |
| draft | Draft message | Under 70 words to the customer, matching the follow-up type. No discounts or promises. |
Sample input (invented)
- Customer name: Gideon Pratt
- Score: 6
- Why that score: The site works, but every small change takes a week and I have to chase for updates.
Tested output
- Follow-up type: Call back
- Draft message: Hi Gideon, thank you for your honest feedback. I'm sorry that small changes take a week and that you have to chase us for updates. That isn't the experience we want you to have. We would like to arrange a call to hear more about what's been happening and talk through your concerns. Please let us know a good time to reach you.
Download: 36-nps-follow-up-form.json (form export) · 36-nps-follow-up-feed.json (feed settings and meta)
37. Event banner image
Generates a wide banner for an event from its name, a style choice and a short description, with space left for the headline.
Plan: Pro. An AI Image feed after submission into a File Upload field.
Fields
- Event name (Single Line Text; required)
- Style (Drop Down; required; choices: Watercolor, Flat illustration, Photo style)
- What the event is about (Paragraph Text; required)
- Banner image (File Upload; AI output)
Feed settings (Form Settings > AI Image)
| Setting | Value |
|---|---|
| Name | AI3-37 · Event banner image |
| Model | GPT Image 2.6 Flare |
| Trigger Mode | After form submission |
| Target File Upload Field | Banner image |
| Size | 1536 x 1024 |
| Quality | Low |
| Complexity | Low |
| Output Format | JPEG |
| Content Filter | Standard (provider default) |
| Conditional Logic | Off |
Prompt
A wide banner image in {Style:2} style for an event called "{Event name:1}". Theme: {What the event is about:3}. No text, letters or logos. Leave calm empty space in the left third for a headline.
Sample input (invented)
- Event name: Riverside Spring Plant Swap
- Style: Watercolor
- What the event is about: Neighbors trade seedlings, cuttings and seeds at the riverside park pavilion on a sunny spring morning.
Tested output

Generated on November 18, 2026 by GPT Image 2.6 Flare at Quality Low. Open the image file.
Download: 37-event-banner-image-form.json (form export) · 37-event-banner-image-feed.json (feed settings and meta)
38. Product mockup image
Generates a clean studio-style product image from the product, color and material, for a catalog draft or a product request form.
Plan: Pro. An AI Image feed after submission into a File Upload field.
Fields
- Product (Single Line Text; required)
- Color (Single Line Text; required)
- Material (Single Line Text; required)
- Product image (File Upload; AI output)
Feed settings (Form Settings > AI Image)
| Setting | Value |
|---|---|
| Name | AI3-38 · Product mockup image |
| Model | GPT Image 2.6 Flare |
| Trigger Mode | After form submission |
| Target File Upload Field | Product image |
| Size | 1024 x 1024 |
| Quality | Low |
| Complexity | Low |
| Output Format | JPEG |
| Content Filter | Standard (provider default) |
| Conditional Logic | Off |
Prompt
Studio product photo of a {Product:1} in {Color:2}, made of {Material:3}, on a plain light grey background with a soft shadow, centered. No text and no brand marks.
Sample input (invented)
- Product: ceramic pour-over coffee dripper
- Color: matte sage green
- Material: stoneware
Tested output

Generated on November 18, 2026 by GPT Image 2.6 Flare at Quality Low. Open the image file.
Download: 38-product-mockup-image-form.json (form export) · 38-product-mockup-image-feed.json (feed settings and meta)
39. Featured image for a blog post submission
Generates a simple illustrated featured image from a guest post title and summary, so every submission arrives with an image to review.
Plan: Pro. An AI Image feed after submission into a File Upload field.
Fields
- Post title (Single Line Text; required)
- Post summary (Paragraph Text; required)
- Featured image (File Upload; AI output)
Feed settings (Form Settings > AI Image)
| Setting | Value |
|---|---|
| Name | AI3-39 · Featured image for a blog post submission |
| Model | GPT Image 2.6 Flare |
| Trigger Mode | After form submission |
| Target File Upload Field | Featured image |
| Size | 1536 x 1024 |
| Quality | Low |
| Complexity | Low |
| Output Format | JPEG |
| Content Filter | Standard (provider default) |
| Conditional Logic | Off |
Prompt
Flat vector illustration for a blog post titled "{Post title:1}". Summary: {Post summary:2}. Simple shapes and a limited palette of three colors. No text or letters in the image.
Sample input (invented)
- Post title: Five checks before you launch a donation form
- Post summary: A practical checklist: test payments in sandbox mode, confirm receipts, check the mobile layout, set spam protection, and decide who gets notified.
Tested output

Generated on November 18, 2026 by GPT Image 2.6 Flare at Quality Low. Open the image file.
Download: 39-blog-featured-image-form.json (form export) · 39-blog-featured-image-feed.json (feed settings and meta)
40. Illustrated listing image
For a rental or marketplace listing that has no photos yet: generates a hand-drawn illustration, clearly not a photo, so nobody mistakes it for the real property.
Plan: Pro. An AI Image feed after submission into a File Upload field.
Fields
- Property type (Single Line Text; required)
- Setting (Single Line Text; required)
- Highlights (Paragraph Text; required)
- Listing illustration (File Upload; AI output)
Feed settings (Form Settings > AI Image)
| Setting | Value |
|---|---|
| Name | AI3-40 · Illustrated listing image |
| Model | GPT Image 2.6 Flare |
| Trigger Mode | After form submission |
| Target File Upload Field | Listing illustration |
| Size | 1536 x 1024 |
| Quality | Low |
| Complexity | Low |
| Output Format | JPEG |
| Content Filter | Standard (provider default) |
| Conditional Logic | Off |
Prompt
Warm hand-drawn illustration, clearly not a photograph, of a {Property type:1} in {Setting:2}. Show: {Highlights:3}. Soft morning light, no people, no text.
Sample input (invented)
- Property type: small timber cabin
- Setting: a pine forest by a lake
- Highlights: a wraparound porch with two chairs, a stone chimney, and a canoe on the shore
Tested output

Generated on November 18, 2026 by GPT Image 2.6 Flare at Quality Low. Open the image file.
Download: 40-listing-illustration-image-form.json (form export) · 40-listing-illustration-image-feed.json (feed settings and meta)
Run these on your own sites
GravityOps AI Feed runs these feeds inside Gravity Forms with your own Anthropic and OpenAI keys. Plans, setup and docs: GravityOps AI Feed.