Exact request sent to the run panel.
{
"source": "retrieve",
"template": {
"id": "universal_event_rsvp",
"slug": "universal-event-rsvp",
"name": "Universal Event RSVP",
"categoryId": "EVENT_RSVP"
},
"inputs": {
"eventUrl": "",
"userContext": "",
"ticketType": "free",
"ticketQuantity": 1,
"missingInfoStrategy": "interpret",
"maxPrice": "",
"autoComplete": true
},
"agentHint": "You are completing event registration. Adapt completely to whatever platform and UI you encounter.\n\n**TASK CONFIGURATION:**\n- Event URL: \n- User Context: \n- Ticket Preference: free\n- Ticket Quantity: 1\n- Max Price: \n- Missing Info Strategy: interpret\n- Auto-complete: true\n\n---\n\n## STEP 1: NAVIGATE & DETECT\n\n1. Go to \n2. Wait for page to load\n3. **Detect platform from what you see:**\n - Eventbrite-style page\n - Meetup event\n - Facebook Event\n - Luma event\n - Partiful event\n - Unknown/custom platform\n4. Note the platform type for appropriate handling\n\n---\n\n## STEP 2: EXTRACT EVENT INFO\n\n**Capture whatever is visible:**\n- Event name\n- Date, time, timezone\n- Location or virtual meeting info\n- Organizer/host\n- Available ticket types and prices\n- Capacity/availability\n\n---\n\n## STEP 3: TICKET/PRICE CHECK\n\n1. Identify available ticket options\n2. Match to preference: free\n3. Check prices against max: \n\n**If price exceeds max:**\n- STOP\n- Report: \"Ticket price ($X) exceeds maximum ()\"\n- Show available cheaper options if any\n\n**If free is \"free\" and only paid options:**\n- Report: \"No free tickets available. Cheapest: $X\"\n- Stop unless user provided maxPrice\n\n---\n\n## STEP 4: ANALYZE REGISTRATION\n\n**Examine the registration flow:**\n- What fields are present?\n- Which are required vs optional?\n- Any platform-specific fields?\n- Custom organizer questions?\n- Payment requirements?\n\n**DO NOT assume specific field names or locations.**\nAdapt to whatever form structure you encounter.\n\n---\n\n## STEP 5: FILL REGISTRATION\n\n**Parse user context:**\n```\n\n```\n\n**Apply strategy: interpret**\n\nFor each field you encounter:\n1. Check if data available in context\n2. If missing and required:\n - interpret: Derive intelligently (name from email, etc.)\n - ask_user: STOP and list needed fields\n - defaults: Use generic defaults or skip\n3. Fill the field\n4. Watch for validation errors\n\n**Common field mappings:**\n- Name fields: Extract from context\n- Email: Required for most - if missing, report error\n- Phone: Use if provided, skip if optional\n- Company/Organization: Use \"Independent\" if not provided\n- Custom questions: Answer contextually\n\n---\n\n## STEP 6: COMPLETE REGISTRATION\n\n### IF true === true:\n1. Fill all fields\n2. Select ticket type and quantity\n3. **Check for validation errors before submitting**\n4. If errors: Report them and stop\n5. If payment required: Report and stop (don't auto-pay)\n6. Submit registration\n7. Wait for confirmation\n8. Capture confirmation number/details\n\n### IF true === false:\n1. Prepare all values\n2. Report preview of what would be submitted\n3. DO NOT submit\n\n---\n\n## STEP 7: HANDLE ERRORS\n\n**If form validation fails:**\n- Read error messages\n- Report specific issues\n- Suggest fixes\n\n**If platform blocks or requires login:**\n- Report the requirement\n- Explain what's needed\n\n---\n\n## STEP 8: REPORT RESULTS\n\n```json\n{\n \"platform\": \"\",\n \"event\": {\n \"name\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"location\": \"\",\n \"organizer\": \"\",\n \"eventUrl\": \"\"\n },\n \"tickets\": {\n \"type\": \"\",\n \"quantity\": 1,\n \"pricePerTicket\": 0,\n \"totalPrice\": 0,\n \"confirmationNumber\": \"\"\n },\n \"registration\": {\n \"fieldsFound\": [],\n \"fieldsProvided\": {},\n \"fieldsDerived\": {},\n \"validationErrors\": []\n },\n \"status\": \"completed|preview|incomplete|exceeds_budget|payment_required|validation_error|login_required|failed\",\n \"errorMessage\": \"\"\n}\n```\n\n---\n\n## ADAPTIVE UI PRINCIPLES\n\n**This template must work on ANY event platform.**\n\n- Don't assume button text (\"Register\", \"RSVP\", \"Get Tickets\" - all valid)\n- Don't assume form layout (modal, inline, multi-page)\n- Don't assume field labels (adapt to meaning)\n- Handle unexpected prompts gracefully\n- Report what you see if stuck\n\n**If the platform is unfamiliar:**\n- Describe the UI you see\n- Make reasonable choices\n- Report uncertainty in results",
"userInput": "You are completing event registration. Adapt completely to whatever platform and UI you encounter.\n\n**TASK CONFIGURATION:**\n- Event URL: \n- User Context: \n- Ticket Preference: free\n- Ticket Quantity: 1\n- Max Price: \n- Missing Info Strategy: interpret\n- Auto-complete: true\n\n---\n\n## STEP 1: NAVIGATE & DETECT\n\n1. Go to \n2. Wait for page to load\n3. **Detect platform from what you see:**\n - Eventbrite-style page\n - Meetup event\n - Facebook Event\n - Luma event\n - Partiful event\n - Unknown/custom platform\n4. Note the platform type for appropriate handling\n\n---\n\n## STEP 2: EXTRACT EVENT INFO\n\n**Capture whatever is visible:**\n- Event name\n- Date, time, timezone\n- Location or virtual meeting info\n- Organizer/host\n- Available ticket types and prices\n- Capacity/availability\n\n---\n\n## STEP 3: TICKET/PRICE CHECK\n\n1. Identify available ticket options\n2. Match to preference: free\n3. Check prices against max: \n\n**If price exceeds max:**\n- STOP\n- Report: \"Ticket price ($X) exceeds maximum ()\"\n- Show available cheaper options if any\n\n**If free is \"free\" and only paid options:**\n- Report: \"No free tickets available. Cheapest: $X\"\n- Stop unless user provided maxPrice\n\n---\n\n## STEP 4: ANALYZE REGISTRATION\n\n**Examine the registration flow:**\n- What fields are present?\n- Which are required vs optional?\n- Any platform-specific fields?\n- Custom organizer questions?\n- Payment requirements?\n\n**DO NOT assume specific field names or locations.**\nAdapt to whatever form structure you encounter.\n\n---\n\n## STEP 5: FILL REGISTRATION\n\n**Parse user context:**\n```\n\n```\n\n**Apply strategy: interpret**\n\nFor each field you encounter:\n1. Check if data available in context\n2. If missing and required:\n - interpret: Derive intelligently (name from email, etc.)\n - ask_user: STOP and list needed fields\n - defaults: Use generic defaults or skip\n3. Fill the field\n4. Watch for validation errors\n\n**Common field mappings:**\n- Name fields: Extract from context\n- Email: Required for most - if missing, report error\n- Phone: Use if provided, skip if optional\n- Company/Organization: Use \"Independent\" if not provided\n- Custom questions: Answer contextually\n\n---\n\n## STEP 6: COMPLETE REGISTRATION\n\n### IF true === true:\n1. Fill all fields\n2. Select ticket type and quantity\n3. **Check for validation errors before submitting**\n4. If errors: Report them and stop\n5. If payment required: Report and stop (don't auto-pay)\n6. Submit registration\n7. Wait for confirmation\n8. Capture confirmation number/details\n\n### IF true === false:\n1. Prepare all values\n2. Report preview of what would be submitted\n3. DO NOT submit\n\n---\n\n## STEP 7: HANDLE ERRORS\n\n**If form validation fails:**\n- Read error messages\n- Report specific issues\n- Suggest fixes\n\n**If platform blocks or requires login:**\n- Report the requirement\n- Explain what's needed\n\n---\n\n## STEP 8: REPORT RESULTS\n\n```json\n{\n \"platform\": \"\",\n \"event\": {\n \"name\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"location\": \"\",\n \"organizer\": \"\",\n \"eventUrl\": \"\"\n },\n \"tickets\": {\n \"type\": \"\",\n \"quantity\": 1,\n \"pricePerTicket\": 0,\n \"totalPrice\": 0,\n \"confirmationNumber\": \"\"\n },\n \"registration\": {\n \"fieldsFound\": [],\n \"fieldsProvided\": {},\n \"fieldsDerived\": {},\n \"validationErrors\": []\n },\n \"status\": \"completed|preview|incomplete|exceeds_budget|payment_required|validation_error|login_required|failed\",\n \"errorMessage\": \"\"\n}\n```\n\n---\n\n## ADAPTIVE UI PRINCIPLES\n\n**This template must work on ANY event platform.**\n\n- Don't assume button text (\"Register\", \"RSVP\", \"Get Tickets\" - all valid)\n- Don't assume form layout (modal, inline, multi-page)\n- Don't assume field labels (adapt to meaning)\n- Handle unexpected prompts gracefully\n- Report what you see if stuck\n\n**If the platform is unfamiliar:**\n- Describe the UI you see\n- Make reasonable choices\n- Report uncertainty in results",
"urls": [],
"meta": {
"createdAt": "",
"userAgent": ""
},
"execution": {
"mode": "device",
"deviceIds": []
}
}
Add to Chrome