The Details

Send your RSVPs to Zapier, Make, n8n or a Google Sheet

Every reply, sign-up and check-in on your event can reach another app the moment it happens. You paste one address into your event, and the app takes it from there: a row in a sheet, a message to your team, a contact in your CRM.

Make your RSVP formWebhooks come with the event pass.

How it works

  1. Step 1

    Get an address

    Zapier, Make, n8n and Google Apps Script all give you a webhook address that waits for data.

  2. Step 2

    Add it to your event

    On the event’s Integrations tab, paste it and tick what to send. Up to 5 addresses per event.

  3. Step 3

    Replies arrive

    Each one comes as JSON within seconds, signed with your secret. A failed one is tried again for a few hours.

Zapier

  1. Make a new Zap. For the trigger, choose Webhooks by Zapier, then the event Catch Hook.
  2. Copy the webhook URL Zapier shows you.
  3. On The Details, open your event, then the Integrations tab. Paste the URL under Add an endpoint, choose what to send, and add it.
  4. Press Send a test event, then Test trigger in Zapier. Zapier now knows the fields: household, guests, replies and answers.
  5. Add your action: a row in a sheet, a message in Slack, a contact in your CRM. Map the fields, then publish the Zap.

Make

  1. Make a new scenario. Add the Webhooks module and choose Custom webhook.
  2. Add a webhook, name it, and copy the address Make gives you.
  3. On The Details, open your event, then Integrations. Paste the address under Add an endpoint and add it.
  4. Press Run once in Make, then Send a test event on The Details. Make learns the structure from it.
  5. Add the modules that come next, map the fields, and turn the scenario on.

n8n

  1. Add a Webhook node to a new workflow. Set the HTTP method to POST.
  2. Copy the Production URL (the test URL only listens while you watch). Your n8n must be reachable over https.
  3. On The Details, open your event, then Integrations, and add the URL as an endpoint.
  4. Activate the workflow, press Send a test event, and open the execution to see the fields.
  5. To check the signature, add a Code node with the Node example from the developer docs, using the raw body.

Send replies to a Google Sheet

No Zapier needed: a short Apps Script in your sheet takes each reply and adds a row for every person on it.

  1. Make a Google Sheet. Open Extensions, then Apps Script.
  2. Replace what’s there with the script below. Change TOKEN to a long random word only you know.
  3. Deploy: New deployment, type Web app, execute as Me, access Anyone. Allow it when Google asks, then copy the web app URL.
  4. Add ?token= and your word to the end of the URL, like …/exec?token=your-word.
  5. On The Details, add that whole address as an endpoint on your event’s Integrations tab, with A first reply and A changed reply ticked. Press Send a test event: a row appears in a tab called Replies.
Apps Script
// The Details → Google Sheets. Paste into Extensions → Apps Script, set TOKEN,
// then Deploy → New deployment → Web app (Execute as: Me, Who has access: Anyone).
const TOKEN = 'change-me-to-a-long-random-word'

function doPost(e) {
  if (!e.parameter || e.parameter.token !== TOKEN) return ContentService.createTextOutput('wrong token')
  const event = JSON.parse(e.postData.contents)
  const book = SpreadsheetApp.getActiveSpreadsheet()
  const sheet = book.getSheetByName('Replies') || book.insertSheet('Replies')
  if (sheet.getLastRow() === 0) {
    sheet.appendRow(['Received', 'Type', 'Household', 'Email', 'First name', 'Last name', 'Replies', 'Answers'])
  }
  if (event.type === 'test') {
    sheet.appendRow([event.created_at, 'test', event.data.message])
    return ContentService.createTextOutput('ok')
  }
  if (event.type !== 'reply.created' && event.type !== 'reply.updated') return ContentService.createTextOutput('ignored')
  const h = event.data.household
  h.guests.forEach(function (g) {
    sheet.appendRow([
      event.created_at,
      event.type,
      h.label,
      h.email || '',
      g.first_name,
      g.last_name,
      g.replies.map(function (r) { return r.sub_event + ': ' + (r.status || 'no reply') }).join('; '),
      g.answers.map(function (a) { return a.question + ': ' + a.answer }).join('; '),
    ])
  })
  return ContentService.createTextOutput('ok')
}

Apps Script can’t read the headers a request comes with, so it can’t check our signature. The token in the address does that job: anyone without it is turned away. Keep the address to yourself, and change the token (and the endpoint) if it gets out.

Manage your event from Claude or ChatGPT

Add The Details to Claude or ChatGPT as a custom connector, sign in, and ask in your own words: who hasn’t replied yet, add a family of four, email a reminder, move the reply-by date.

We run no AI ourselves: the app you connect does the asking and works only on events with the event pass. You choose whether it may make changes, and you can disconnect it any time in your account settings. The address and every tool are in the MCP docs.

CRMs, Slack and the rest

Salesforce, HubSpot, Mailchimp, Slack and most other tools connect through Zapier or Make: catch the webhook, then add their step. For your own code there is a read-only API with keys you make in your account.

Every field, header and retry rule is in the developer docs. The form itself is free: see the RSVP form and the sign-up sheet.

Connect your RSVPs

Make your event page and form, publish it, then add a webhook from the Integrations tab once you have the event pass.

Free to make and publish, for up to 50 guests. Guests never need an account.

Questions

Is there a Zapier app for The Details?

Not a listed app. Zapier’s “Webhooks by Zapier” trigger with “Catch Hook” takes any address, and that is all The Details needs: paste the address Zapier gives you into your event’s Integrations tab and every reply arrives as a Zap trigger.

Can I send replies to Salesforce or HubSpot?

Yes, through Zapier or Make. Catch the webhook there, then add a step that creates or updates a contact in your CRM with the guest’s name and email. There is no direct CRM connection.

Do I need the event pass?

Yes. Webhooks and API keys come with the event pass, which is one payment per event. Grants work too, if we gave your event the feature.

What is sent?

What you already see on your guest list: the household’s name and email, each person’s name, their reply to each part of the event and their answers to your questions. For sign-ups, the item and who took it; for check-in, who arrived and when.

What if my Zap or scenario is off when someone replies?

We try again after 30 seconds, 2, 10 and 30 minutes, then 2 hours. If 50 deliveries in a row fail every try, we turn the endpoint off and email you. Turn it back on from the Integrations tab once it works again; failed deliveries in the log can be sent again with Resend.

How does my app know a delivery really came from The Details?

Each one is signed with your endpoint’s secret in the X-TheDetails-Signature header. Your own server can check it in a few lines; the developer docs show how in Node and Python. Checking the signature