Exact request sent to the run panel.
{
"source": "retrieve",
"template": {
"id": "partiful_event_rsvp",
"slug": "partiful-rsvp",
"name": "Partiful Event RSVP",
"categoryId": "EVENT_RSVP"
},
"inputs": {
"eventUrl": "",
"userContext": "",
"rsvpResponse": "yes",
"guestCount": 0,
"missingInfoStrategy": "interpret",
"messageToHost": "",
"autoRsvp": true
},
"agentHint": "Navigate to . This is a Partiful event RSVP task.\n\n**USER CONTEXT:** \n**RSVP RESPONSE:** yes\n**GUEST COUNT:** 0\n**MISSING INFO STRATEGY:** interpret\n**MESSAGE TO HOST:** \n**AUTO-RSVP:** true\n\n**EXECUTION FLOW:**\n\n1. **EXTRACT EVENT DETAILS**\n - Event name and description\n - Date and time\n - Location (address or virtual)\n - Host information\n - RSVP deadline\n - Any special notes (bring something, theme, dress code)\n\n2. **ANALYZE RSVP FORM**\n - Required fields (usually name, phone, RSVP status)\n - Optional fields (email, dietary needs, +1 info)\n - Host questions (e.g., \"What are you bringing?\", \"Song requests?\")\n\n3. **PREPARE RSVP DATA**\n Using strategy: interpret\n \n - RSVP Status: yes\n - Guest count: 0\n - User info: \n \n **SMART HANDLING:**\n - If phone number missing and strategy is \"interpret\": Use a placeholder or mark as \"will provide\"\n - If host asks \"What are you bringing?\": \n * Check user context for mentions\n * If none, suggest something appropriate to event type (wine for dinner party, snacks for casual)\n - If +1 name requested but not provided:\n * strategy \"interpret\": Use \"Plus One\" or \"Guest\"\n * strategy \"ask_user\": Prompt for +1 name\n \n **HOST MESSAGE:**\n - If provided: \n - If not provided and strategy is \"interpret\": Generate friendly response like \"Thanks for the invite! Looking forward to it!\"\n\n4. **COMPLETE RSVP**\n - {autoRsvp ? \"Fill and submit the form\" : \"Show preview\"}\n - Handle any confirmation screens\n\n5. **POST-RSVP**\n - Note any action items (bring something, RSVP deadline for +1 names, etc.)\n\n**RETURN:**\n{\n \"event\": {\n \"name\": \"\",\n \"host\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"location\": \"\",\n \"eventUrl\": \"\"\n },\n \"rsvp\": {\n \"status\": \"yes\",\n \"guestCount\": 0,\n \"dataUsed\": {},\n \"messageToHost\": \"\"\n },\n \"status\": \"completed|preview|failed\",\n \"actionItems\": [],\n}\n\n**PARTIFUL-SPECIFIC TIPS:**\n- Partiful is casual - friendly tone is appropriate\n- Phone numbers are often required - ask user if not provided and strategy is \"ask_user\"\n- +1 info can usually be added later, so mark as \"TBD\" if needed\n- Host questions are usually optional - intelligent guesses are fine\n\nComplete the RSVP smoothly with minimal friction!",
"userInput": "Navigate to . This is a Partiful event RSVP task.\n\n**USER CONTEXT:** \n**RSVP RESPONSE:** yes\n**GUEST COUNT:** 0\n**MISSING INFO STRATEGY:** interpret\n**MESSAGE TO HOST:** \n**AUTO-RSVP:** true\n\n**EXECUTION FLOW:**\n\n1. **EXTRACT EVENT DETAILS**\n - Event name and description\n - Date and time\n - Location (address or virtual)\n - Host information\n - RSVP deadline\n - Any special notes (bring something, theme, dress code)\n\n2. **ANALYZE RSVP FORM**\n - Required fields (usually name, phone, RSVP status)\n - Optional fields (email, dietary needs, +1 info)\n - Host questions (e.g., \"What are you bringing?\", \"Song requests?\")\n\n3. **PREPARE RSVP DATA**\n Using strategy: interpret\n \n - RSVP Status: yes\n - Guest count: 0\n - User info: \n \n **SMART HANDLING:**\n - If phone number missing and strategy is \"interpret\": Use a placeholder or mark as \"will provide\"\n - If host asks \"What are you bringing?\": \n * Check user context for mentions\n * If none, suggest something appropriate to event type (wine for dinner party, snacks for casual)\n - If +1 name requested but not provided:\n * strategy \"interpret\": Use \"Plus One\" or \"Guest\"\n * strategy \"ask_user\": Prompt for +1 name\n \n **HOST MESSAGE:**\n - If provided: \n - If not provided and strategy is \"interpret\": Generate friendly response like \"Thanks for the invite! Looking forward to it!\"\n\n4. **COMPLETE RSVP**\n - {autoRsvp ? \"Fill and submit the form\" : \"Show preview\"}\n - Handle any confirmation screens\n\n5. **POST-RSVP**\n - Note any action items (bring something, RSVP deadline for +1 names, etc.)\n\n**RETURN:**\n{\n \"event\": {\n \"name\": \"\",\n \"host\": \"\",\n \"date\": \"\",\n \"time\": \"\",\n \"location\": \"\",\n \"eventUrl\": \"\"\n },\n \"rsvp\": {\n \"status\": \"yes\",\n \"guestCount\": 0,\n \"dataUsed\": {},\n \"messageToHost\": \"\"\n },\n \"status\": \"completed|preview|failed\",\n \"actionItems\": [],\n}\n\n**PARTIFUL-SPECIFIC TIPS:**\n- Partiful is casual - friendly tone is appropriate\n- Phone numbers are often required - ask user if not provided and strategy is \"ask_user\"\n- +1 info can usually be added later, so mark as \"TBD\" if needed\n- Host questions are usually optional - intelligent guesses are fine\n\nComplete the RSVP smoothly with minimal friction!",
"urls": [],
"meta": {
"createdAt": "",
"userAgent": ""
},
"execution": {
"mode": "device",
"deviceIds": []
}
}
Add to Chrome