Register for a Partiful event

Complete the Partiful RSVP and return the event details.

RUNS INYour browser works best

SETUP7 details to add

WHAT YOU GET03 PARTS

01Event title, date, and location
02RSVP form completed
03Guest count and confirmation status

SET UP YOUR RUN

Add the details. Check the result. Run it.

No code needed.

Tell rtrvr what to use

Required details are marked. The example text shows the expected format.

Partiful event URLRequired

Your info (optional)

Provide basic info. Agent fills the rest intelligently.

RSVP response

Number of guests (+1, +2, etc.)

Handle missing info

Message to host (optional)

Auto-complete RSVP

Choose where it runs

Cloud uses a fresh managed browser. The extension uses the sites you are already signed into.

Your browser works best. Your signed-in account may return more complete results.

Choose a connected browser

Open the rtrvr extension and sign in with the same account, then choose your browser here.

Get the extension

Sign in to connect

Install the Chrome extension.
Sign in on this page and in the extension with the same account.
Choose the connected browser before starting the task.

Start this task in Free Mode in Cloud or your connected Chrome. Cookie sync, schedules, and triggers require a subscription. Compare plans →

Free usage, ads, and data terms

Free Mode includes supported AI models and Cloud browser time for tasks you start in the extension or Cloud dashboard. No AI API key or paid AI subscription is required. Sponsored cards and a daily fair-use allowance apply. Your account shows the current allowance and reset time. When you reach it, wait for the reset, use your own AI provider, or choose a paid plan. Your provider may charge for its usage.

One schedule that runs once a day or less often, in the Cloud or in your Chrome, is included, paid from the daily allowance. More schedules, faster schedules, triggers, cookie sync, API runs, rtrvr's agent over MCP, and WhatsApp tasks require a paid plan. Browser tools that let your own AI drive your Chrome over MCP are free on every plan. Data enrichment and managed proxies can use credits separately.

On the free plan, Cloud API calls made with an API key, the MCP Cloud tools (cloud_agent, cloud_scrape, and agent or scrape when they run in Cloud), and WhatsApp tasks need a paid plan, as does running rtrvr's agent in your Chrome through API or MCP. Free Mode covers the tasks you start in the extension or Cloud dashboard. On a paid plan, API, MCP, and WhatsApp runs use credits for the resources they consume.

Free Mode involves sponsored content in both the Chrome extension and Cloud, as described in the Terms and Privacy Notice.

Using your own AI provider avoids model-credit charges and the Free Mode allowance. Cloud resources and managed services may still use credits. Sponsored cards still appear on the free plan. Paid plans offer ad-free runs.

ONE MORE STEP

Add the required details to continue.

WHAT HAPPENS NEXT

From setup to finished result.

01
rtrvr opens the right sites. It uses Cloud or the signed-in browser you chose.
02
The browser does the job. You can follow the run and step in if a site asks for help.
03
You get the result. The output above is the shape to expect.

ADVANCEDRequest JSONOptional

Exact request sent to the run panel.

REQUEST.JSON

{
  "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": []
  }
}