Exact request sent to the run panel.
{
"source": "retrieve",
"template": {
"id": "luma_event_rsvp",
"slug": "luma-rsvp",
"name": "Luma Event RSVP",
"categoryId": "EVENT_RSVP"
},
"inputs": {
"eventUrl": "",
"userContext": "",
"missingInfoStrategy": "interpret",
"dietaryRestrictions": "",
"autoRsvp": true
},
"agentHint": "You are completing a Luma event RSVP. Adapt completely to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Event URL: \n- User Context: \n- Missing Info Strategy: interpret\n- Dietary Restrictions: \n- Auto-RSVP: true\n\n---\n\n## STEP 1: NAVIGATE TO EVENT\n\n1. Go to \n2. Wait for event page to fully load\n3. If event not found, past, or cancelled: Report status and stop\n\n---\n\n## STEP 2: EXTRACT EVENT INFO\n\n**Capture whatever is visible:**\n- Event name\n- Date and time (with timezone if shown)\n- Location (venue address or \"Virtual\")\n- Host/organizer name\n- Event description summary\n- RSVP deadline (if shown)\n- Capacity status (spots left, waitlist, etc.)\n\n---\n\n## STEP 3: FIND REGISTRATION\n\n1. Look for RSVP/Register/Get Tickets button or similar\n2. Click to open registration flow\n3. **Analyze the form that appears:**\n - What fields are shown?\n - Which are marked required?\n - Any custom questions from host?\n\n**Note: Luma forms vary by event - adapt to what you see.**\n\n---\n\n## STEP 4: PREPARE REGISTRATION DATA\n\n**Parse user context:**\n```\n\n```\n\n**For each form field you encounter:**\n\n### Strategy: \"interpret\"\n- Use provided context if available\n- For missing required fields, derive intelligently:\n * Name: Extract from email if available, or use \"Attendee\"\n * Email: Must have - if missing, report error\n * Company: Use \"Independent\" or derive from context\n * Role/Title: Derive from context or use \"Professional\"\n * LinkedIn: Skip if not required or provided\n * Custom questions: Answer contextually based on event type\n\n### Strategy: \"ask_user\"\n- Use provided context for available fields\n- If required fields missing, STOP and report:\n \"Missing required fields: [list]. Please provide.\"\n\n### Strategy: \"skip\"\n- Only fill with available context\n- If required fields missing, STOP:\n \"Cannot complete - missing: [list]\"\n\n**Dietary restrictions:** \n\n---\n\n## STEP 5: FILL & SUBMIT\n\n1. Fill each field with prepared data\n2. **Check for validation errors before submitting:**\n - Red highlights?\n - Error messages?\n - Required field warnings?\n3. If errors: Report them and what's needed\n\n### IF true === true AND no errors:\n4. Submit the form\n5. Wait for confirmation\n6. Capture confirmation details\n\n### IF true === false:\n4. Prepare all values for preview\n5. Report what would be submitted\n6. DO NOT submit\n\n---\n\n## STEP 6: REPORT RESULTS\n\n```json\n{\n \"event\": {\n \"name\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"timezone\": \"\",\n \"location\": \"\",\n \"host\": \"\",\n \"eventUrl\": \"\"\n },\n \"registration\": {\n \"fieldsFound\": [],\n \"fieldsProvided\": {},\n \"fieldsDerived\": {},\n \"fieldsSkipped\": [],\n \"validationErrors\": []\n },\n \"status\": \"completed|preview|incomplete|validation_error|failed\",\n \"confirmationMessage\": \"\",\n \"nextSteps\": [],\n \"errorMessage\": \"\"\n}\n```\n\n---\n\n## ADAPTIVE UI PRINCIPLES\n\n**DO NOT assume specific button names or locations.**\n- Look for registration/RSVP actions wherever they appear\n- Forms may be modal, inline, or multi-step\n- Field labels vary - match by meaning, not exact text\n- Handle dynamic form elements\n\n**If something doesn't look as expected:**\n- Describe what you see\n- Adapt your approach\n- Report if you cannot proceed",
"userInput": "You are completing a Luma event RSVP. Adapt completely to the actual UI you encounter.\n\n**TASK CONFIGURATION:**\n- Event URL: \n- User Context: \n- Missing Info Strategy: interpret\n- Dietary Restrictions: \n- Auto-RSVP: true\n\n---\n\n## STEP 1: NAVIGATE TO EVENT\n\n1. Go to \n2. Wait for event page to fully load\n3. If event not found, past, or cancelled: Report status and stop\n\n---\n\n## STEP 2: EXTRACT EVENT INFO\n\n**Capture whatever is visible:**\n- Event name\n- Date and time (with timezone if shown)\n- Location (venue address or \"Virtual\")\n- Host/organizer name\n- Event description summary\n- RSVP deadline (if shown)\n- Capacity status (spots left, waitlist, etc.)\n\n---\n\n## STEP 3: FIND REGISTRATION\n\n1. Look for RSVP/Register/Get Tickets button or similar\n2. Click to open registration flow\n3. **Analyze the form that appears:**\n - What fields are shown?\n - Which are marked required?\n - Any custom questions from host?\n\n**Note: Luma forms vary by event - adapt to what you see.**\n\n---\n\n## STEP 4: PREPARE REGISTRATION DATA\n\n**Parse user context:**\n```\n\n```\n\n**For each form field you encounter:**\n\n### Strategy: \"interpret\"\n- Use provided context if available\n- For missing required fields, derive intelligently:\n * Name: Extract from email if available, or use \"Attendee\"\n * Email: Must have - if missing, report error\n * Company: Use \"Independent\" or derive from context\n * Role/Title: Derive from context or use \"Professional\"\n * LinkedIn: Skip if not required or provided\n * Custom questions: Answer contextually based on event type\n\n### Strategy: \"ask_user\"\n- Use provided context for available fields\n- If required fields missing, STOP and report:\n \"Missing required fields: [list]. Please provide.\"\n\n### Strategy: \"skip\"\n- Only fill with available context\n- If required fields missing, STOP:\n \"Cannot complete - missing: [list]\"\n\n**Dietary restrictions:** \n\n---\n\n## STEP 5: FILL & SUBMIT\n\n1. Fill each field with prepared data\n2. **Check for validation errors before submitting:**\n - Red highlights?\n - Error messages?\n - Required field warnings?\n3. If errors: Report them and what's needed\n\n### IF true === true AND no errors:\n4. Submit the form\n5. Wait for confirmation\n6. Capture confirmation details\n\n### IF true === false:\n4. Prepare all values for preview\n5. Report what would be submitted\n6. DO NOT submit\n\n---\n\n## STEP 6: REPORT RESULTS\n\n```json\n{\n \"event\": {\n \"name\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"timezone\": \"\",\n \"location\": \"\",\n \"host\": \"\",\n \"eventUrl\": \"\"\n },\n \"registration\": {\n \"fieldsFound\": [],\n \"fieldsProvided\": {},\n \"fieldsDerived\": {},\n \"fieldsSkipped\": [],\n \"validationErrors\": []\n },\n \"status\": \"completed|preview|incomplete|validation_error|failed\",\n \"confirmationMessage\": \"\",\n \"nextSteps\": [],\n \"errorMessage\": \"\"\n}\n```\n\n---\n\n## ADAPTIVE UI PRINCIPLES\n\n**DO NOT assume specific button names or locations.**\n- Look for registration/RSVP actions wherever they appear\n- Forms may be modal, inline, or multi-step\n- Field labels vary - match by meaning, not exact text\n- Handle dynamic form elements\n\n**If something doesn't look as expected:**\n- Describe what you see\n- Adapt your approach\n- Report if you cannot proceed",
"urls": [],
"meta": {
"createdAt": "",
"userAgent": ""
},
"execution": {
"mode": "device",
"deviceIds": []
}
}
Add to Chrome